Update lockfile in changeset version script

[trivikr]

Issue

Refs:

• Update lockfile before posting changeset PR #965 (comment)
• After merging the PR, npm i is not a no-op on package-lock.json changesets/action#203 (comment)

Description

Update lockfile in changeset version script

Testing

$ npm run version
...

$ git status --porcelain
 D .changeset/mean-sheep-refuse.md
 M CHANGELOG.md
 M package-lock.json
 M package.json

$ git diff package-lock.json | head
diff --git a/package-lock.json b/package-lock.json
index abe4451..56c5632 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "aws-sdk-js-codemod",
-  "version": "2.4.2",
+  "version": "2.4.3",
   "lockfileVersion": 3,

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d6c5b8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[trivikr]

The package-lock.json was updated

> changeset version && npm i --package-lock-only
🦋  All files have been updated. Review them and commit at your leisure
up to date, audited 368 packages in 753ms
52 packages are looking for funding
  run `npm fund` for details
found 0 vulnerabilities
/usr/bin/git status --porcelain
 D .changeset/mean-sheep-refuse.md
 M CHANGELOG.md
 M package-lock.json
 M package.json
/usr/bin/git add .
/usr/bin/git commit -m Version Packages

https://github.com/aws/aws-sdk-js-codemod/actions/runs/11678017014/job/32516865225

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.