Skip to content

chore(ci): sync package-lock after release 0.9.25 - #308

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/post-release-package-lock-0.9.25
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
chore/post-release-package-lock-0.9.25

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Automated follow-up to tag release/0.9.25 after npm publish.

  • Workspace @node-webrtc-rust/* versions aligned to 0.9.25
  • package-lock.json optional platform binding entries refreshed from the npm registry

CI is dispatched on this branch and auto-merge (squash) is enabled; it merges once the required checks pass (see scripts/RELEASE.md).

Re-run locally if needed:

bash scripts/ci/post-release-sync-main-package-lock.sh 0.9.25

@akirilyuk

Copy link
Copy Markdown
Owner

Superseded by #311 (package-lock sync for 0.9.26, which includes this release). Merging this older sync now would roll package-lock.json back. Closed while unsticking the release lockfile PRs; see #311.

@akirilyuk akirilyuk closed this Oct 6, 2026
auto-merge was automatically disabled October 6, 2026 03:06

Pull request was closed

@akirilyuk
akirilyuk deleted the chore/post-release-package-lock-0.9.25 branch October 6, 2026 03:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant