Change publish-docs workflow to use Node 20 instead of 22 due to the temporary npm issue #1424
Conversation
This file contains 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
…temporary npm issue
sequba
added a commit
that referenced
this pull request
Jul 18, 2024
* Change publish-docs workflow to use Node 20 instead of 22 due to the temporary npm issue (#1424) * Set NODE_OPTIONS=--openssl-legacy-provider for the typedoc command
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.
Context
The
npm cicommand is failing on Node 22 even though yesterday it worked correctly (see the GH actions execution history). Because of that, thepublish-docsworkflow cannot deploy the new version of the docs. I'm downgrading this workflow to use Node 20 temporarily.