[NICE TO HAVE][FEATURE REQUEST] Option to ask Changesets actopm to update versions in the package-lock.json

[ktarmyshov]

Great tooling! Thank you for your work!

It would be nice if changeset action would provide an option if versions in package-lock.json should also be updated and commited (under the provided token). At the moment I run npm install and commit after the flow with changeset is done.

Thank you!

[mikeybinns]

As a workaround, you can add npm i to your version command, then the package-lock.json file is included in the version packages PR.

[ktarmyshov]

Hi, guys I added the workaround as you suggested.

"changeset:version": "changeset version && npm install && git add --all",

in my flow it is:
npm ci
npm run build:release
then
- id: changesets
uses: changesets/action@v1

The update to package-lock.json is only versioning:

{
"name": "@ktarmyshov/npm-typescript-template",
----- "version": "0.0.15",
++++ "version": "0.0.16",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@ktarmyshov/npm-typescript-template",
----- "version": "0.0.15",
++++ "version": "0.0.16",
"license": "MIT",
"devDependencies": {
"@changesets/cli": "^2.28.1",

Nothing else seems to be touched.

I went through the comments in the related PR - my request makes the tool non-agnostic. So in my case the version issue is sovled and can be closed.

I would suggest just to update the docs to mention about "npm install" for npm (no idea how it would be with other PMs though).

Thank you for your response,
It took me time to test the flows, but the workaround - or probably the right solution for NPM works just fine.
K