How to re-publish a plugin with the same version

Tips & tricks
1

Leaving this here as a tip for others. If you are hitting version issues when doing ipm publish v0.1.2 (or something similar) this may help.

Possible issue:

% ipm publish v0.1.1                    
(node:92339) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Preparing and tagging a new version ✗
npm ERR! Version not changed, might want --allow-same-version

npm ERR! A complete log of this run can be found in:
npm ERR!     ~/.npm/_logs/2020-12-23T22_13_52_594Z-debug.log

You have to set that as an npm config, not an ipm config.

npm config set allow-same-version true

Also, if you are using an SSH target locally (instead of HTTPS), because of two factor authentication or otherwise, make sure that the repository property in package.json is also an SSH target.

1 Like
2

I even didn’t know that!

1 Like
3

Also, ipm publish with a specific tag expects -t:

ipm publish -t v0.1.9
1 Like
4

It is useful just to update the README.
Here is how to update the README without bumping up the version number (e.g., v1.2.0):

git tag -d v1.2.0          # remove the current tag
git tag v1.2.0             # add the same tag to the HEAD
git push origin --mirror   # sync tags
ipm publish -t v1.2.0 --allow-same-version