Repository navigation
ci(release): unblock the npm publish - #81
Merged
Merged
Conversation
node-gyp on the windows-11-arm image fails to find Visual Studio (ERR_CHILD_PROCESS_STDIO_MAXBUFFER), which cancelled the node build matrix and skipped the npm publish for 4.2.0 and 4.2.1. Windows on ARM installs build from source instead.
A workflow_dispatch input reruns only the npm publish from release.yml, so the trusted publisher still matches, to recover a release whose npm step failed.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
The npm publish has been skipped since 4.2.0: the windows-11-arm job of the node prebuild matrix fails because node-gyp cannot locate Visual Studio on that image (
ERR_CHILD_PROCESS_STDIO_MAXBUFFERin its finder), which cancels the other builds and skips the publish job. crates.io and PyPI received 4.2.1; npm is still at 4.1.0.workflow_dispatchinput that reruns only the npm publish of the current version from the same workflow file, so the npm trusted publisher still matches.