Temporarily revert publish to using node 16.x to fix broken publish #1520
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
This is more of a case of quickly dropping down to an older version of `npm` so that it will fix the publish action. Ideally we want to move to a supported version of node and address the issue that comes with that version of npm to perform a publish. It could be 1. move to an older version of npm (ie that one that comes with node 16), but this is not ideal 2. move to a newer version of npm as it may be an issue with the version that came with node 18, but this isn't likely 3. look at the npm publish command to see what needs to be done to make it work. Signed-off-by: Dave Kelsey <d_kelsey@uk.ibm.com>
aklenik
approved these changes
Mar 25, 2024
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.
This is more of a case of quickly dropping down to an older version of
npmso that it will fix the publish action.Ideally we want to move to a supported version of node and address the issue that comes with that version of npm to perform a publish. It could be