Open
Conversation
Contributor
Author
|
Thank you, @mangs . The corresponding story has been paused for other priorities. I'll continue testing here when it is unpaused. |
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.
Changes:
Context:
The current build process with OIDC fails.
It turns out there is an undocumented behaviour for
npm publishandactions/setup-nodewhich requires node version 22 or newer (cf. #21 (comment)).Since the package JSON only requires
"node": ">=16.13.0", I suggest trying this update.Note that the latest version in the change log and
pacakge.jsonis already2.1.2but because the last build failed the published version to the registry is still2.1.1.Alternatively, we have to roll back to the old publishing process without OIDC and manually rotate the secret.