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
sequba
added a commit
that referenced
this pull request
Nov 6, 2024
* Merge hotfix to develop (#1431) Change publish-docs workflow to use Node 20 instead of 22 due to the temporary npm issue * Merge hotfix to develop (#1432) * 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 * Merge hotfix to develop (#1433) * Change publish-docs workflow to use Node 20 instead of 22 due to the temporary npm issue (#1424) * Hotfix: Set NODE_OPTIONS=--openssl-legacy-provider for the typedoc command (#1425) Set NODE_OPTIONS=--openssl-legacy-provider for the typedoc command * Revert the publish-docs workflow to Node 16 * Add build-docs workflow (#1434) * Add build-docs workflow * Add environment variables necessary to build the docs with Node 20 * Use Node 20 in all the build/test workflows (#1435) * Remove license comments from the UMD build (#1437) * Install terser plugin explicite to enable extensive customization * Remove license comment from the UMD builds using string-replace-loader webpack plugin * Test for the redundant license comments in the UMD build inside the verify:umd script * Update build badge in readme to show the build workflow status instead of test (#1443) * Update build badge to show the build workflow status instead of test * Native demos in the docs (#1447) * Add markdown-it plugins * Make HTML+CSS preview work * Make some of the buttons work * Add edit-in-stackblitz button * Make the entire runtime of the demo work (including js) * Add real HF demo. * Make HyperFormula import work in runtime of the docs examples * Add script code-examples-generator * Style stackblitz button * Style demo internal buttons * Remove unused glue-code * Remove not needed vuepress plugins * Fix linter error * Reformat demo/example1.ts file * Add advanced-usage demo * Change the framework demos in the docs to use Codesandbox iframe instead of Stackblitz * Add basic-operations demo * Add basic-usage demo * Add batch-operations demo * Add demo clipboard-operations * Changed the custom-functions demo to use Codesandbox instead of Stackblitz * Add date-time demo * Add demo i18n * Add localizing-functions guide * Add named-expressions demo * Add sorting-data demo * Add undo-redo demo * Fix lint errors * Disable linter for the docs examples * Tweak the styling of demo example * Fix row and column counting in the docs examples * Adjust css of basic-usage demo * Adjust style of advanced-usage demo * Fix styles for basic-operations demo * Fix styles for batch-operations demo * Fix styles for sorting demo * Fix height of the table cell in the demos * Adjust text decoration of the summary row in the i18n demo * Fix styles for basic-operations demo * Adjust styles for the inputs * Disable logging HF version to console in the native examples embedded in the docs * Update styles for the open-in-stackblitz button * Fix broken favicon link * Fix examples.js script to handle newline characters in both unix and windows styles * Reduce space between buttons and table in the undo-redo demo * Fix style for checkbox in the batch-operations demo
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.