Publishing patches to older component versions

[alexkilgour]

Sometimes we will need to fix a bug in an older version of a component. How do we do that?

1. cd into project
2. checkout point-in-history-where-patch-needed
3. create branch for the version you are patching e.g. 2.5.0 would be version2.5
4. make changes, and increment version
5. DO NOT MERGE back to master
6. Manually publish to NPM npm publish --tag version2.5

As long as you supply a --tag <tagname> argument to npm publish, the latest tag will not be updated, and people using npm install <package> or npm install <package>@latest will still get the latest version.

Note that the tagname has to share a namespace with version numbers, so it's best to choose a tagname that doesn't look like a semver version; avoid '1.0.6' or 'v1.0.6'.

sources and examples

• https://stackoverflow.com/questions/24691314/npm-publish-patch-for-earlier-major-version
• https://www.npmjs.com/package/globby?activeTab=versions
• https://github.com/sindresorhus/globby/commits/version11

[sturobson]

There has been no update on this issue for 30 days. It is now marked as "stale". If you think this issue is still relevant and needs attention then reply with an update. If there is no update in 14 days, this issue will be closed.