fix: replace mikeal/merge-release with direct npm publish, update actions to v5#448
Merged
daniloab merged 10 commits intoSurnet:masterfrom Apr 10, 2026
Merged
fix: replace mikeal/merge-release with direct npm publish, update actions to v5#448daniloab merged 10 commits intoSurnet:masterfrom
daniloab merged 10 commits intoSurnet:masterfrom
Conversation
daniloab
approved these changes
Apr 10, 2026
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
2 participants
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.
mikeal/merge-release@masteraction with a direct npm publish workflowactions/checkoutandactions/setup-nodefrom v4 to v5 for Node.js 24 supporturl.parse()deprecation warning in stderrExplanation
mikeal/merge-releaseruns in a Docker container that fails withfatal: not in a git directorydue to git safe directory restrictions in newer environments. The action is also unmaintained.The CLI snapshot test was breaking on Node 22/24 because the deprecation warning was being written to stderr alongside the expected output.