Use latest npm-publish action #774
Merged
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 fixes an issue in v1 where the action was overriding the `.npmrc` file which was causing subsequent calls to `npm` or `yarn` to have a malformed `.npmrc`. This was fixed in v2.
- Node 16 EOL on 2023/10/16 - EdgeDB v1 still works, but we will no longer test it
Fix for the issue with older versions of EdgeDB went out in 4.0.2 which is the latest stable CLI
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 fixes an issue in v1 where the action was overriding the
.npmrcfile which was causing subsequent calls tonpmoryarnto have a malformed.npmrc. This was fixed in v2. We are pinning the action to version v3.0.1 which is the latest version as of today.The other notable change here:
https://github.com/JS-DevTools/npm-publish/tree/v3.0.1#v2-output-changes