chore(ci): sync package-lock after release 0.5.3#44
Closed
akirilyuk wants to merge 1 commit into
Closed
Conversation
akirilyuk
force-pushed
the
chore/post-release-package-lock-0.5.3
branch
from
c2f86a8 to
e133f21
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated follow-up to tag
release/0.5.3after npm publish.@node-webrtc-rust/*versions aligned to0.5.3package-lock.jsonoptional platform binding entries refreshed from the npm registryMerge promptly so
mainstays green fornpm ci(seevalidate-package-lockCI job).Opened manually because the release workflow could not create a PR with
GITHUB_TOKEN(org Actions policy). Future releases: enable Allow GitHub Actions to create pull requests or add repo secretREPO_SYNC_PAT— seescripts/RELEASE.md.