Repository navigation
Update package metadata and lock file for 1.4.2 binary package hashes - #1481
Merged
Merged
Conversation
frankslin
force-pushed
the
chore/lock-files-1.4.2-32589112455
branch
from
August 22, 2026 18:03
19c3578 to
af823ad
Compare
Regenerated to include @opencc/opencc-win32-x64, which the automated run
had missed: npm answered that one publish with HTTP 202 ("your package is
being processed") and the package only became resolvable 3m08s later,
while the lock file job started 7s after the publish. npm silently omits
an unresolvable optional dependency, so the generated lock carried only
the four other platforms.
Verified that the recorded integrity matches the tarball the release
workflow packed and that `npm ci --omit=optional` no longer reports the
lock as out of sync.
frankslin
force-pushed
the
chore/lock-files-1.4.2-32589112455
branch
from
August 22, 2026 18:04
af823ad to
b78f297
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.
Updates package metadata and
package-lock.jsonwith integrity hashes for the newly published binary packages.Next steps: merge this PR, then create the release tag pointing to the merge commit and publish the GitHub Release. The
release: publishedevent will trigger the main package publishing workflow.