Fix automated release - #73
Merged
Merged
Conversation
LucDeCaf
approved these changes
Jul 9, 2026
LucDeCaf
left a comment
LucDeCaf
left a comment
There was a problem hiding this comment.
Weird that latest npm and latest node don't work together by default. Oh well.
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.
Apologies for the PR spam. Installing the latest version of
npmis broken because half of npm itself is a CommonJS build while some of its dependencies have started being ESM only (failed release run).I'm sure they'll fix that eventually, for now we'll just use the npm version included in Node. Because we've upgraded to Node 26, we no longer need to install npm manually, the default version is recent enough to support OIDC publishing.
I have tested this with a dev release, it seems like this finally gets things working.