dependabot/npm_and_yarn/main/eslint-10.4.0
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: Updating your published package version number |
| 3 | --- |
| 4 | |
| 5 | When you make significant changes to a published package, we recommend updating the version number to communicate the extent of the changes to others who rely on your code. |
| 6 | |
| 7 | <Note> |
| 8 | |
| 9 | **Note:** If you have linked a git repository to a package, updating the package version number will also add a tag with the updated release number to the linked git repository. |
| 10 | |
| 11 | </Note> |
| 12 | |
| 13 | 1. To change the version number in `package.json`, on the command line, in the package root directory, run the following command, replacing `<update_type>` with one of the [semantic versioning][semver] release types (patch, major, or minor): |
| 14 | |
| 15 | ``` |
| 16 | npm version <update_type> |
| 17 | ``` |
| 18 | |
| 19 | 2. Run `npm publish`. |
| 20 | |
| 21 | 3. Go to your package page (`https://npmjs.com/package/<package>`) to check that the package version has been updated. |
| 22 | |
| 23 | For more information on `npm version`, see the [CLI documentation][cli-version]. |
| 24 | |
| 25 | [semver]: about-semantic-versioning |
| 26 | [cli-version]: /cli/version |