packaging: use PNPM for publishing, with correct tags #363
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
fixes: #362 extracts the following tags: * rc * next * alpha * beta also enables NPM provenance when publishing
✅ Deploy Preview for oasisprotocol-sapphire-paratime canceled.
|
CedarMist
added
javascript
lukaw3d
reviewed
Aug 26, 2024
aefhm
approved these changes
Aug 26, 2024
CedarMist
added a commit
that referenced
this pull request
Aug 27, 2024
re: #362 re: #363 for the following packages: * oasisprotocol/sapphire-paratime * oasisprotocol/sapphire-ethers-v6 * oasisprotocol/sapphire-hardhat * oasisprotocol/sapphire-viem-v2 * oasisprotocol/sapphire-wagmi-v2 They will be released under the `next` tag, to test updated publish.yaml workflow after publishing the bundlephobia links in the main README.md should work It should also be possible to install the packages & resolve their dependencies.
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.
fixes: #362
includes: #358
extracts the following tags:
also enables NPM provenance when publishing
We can change the dist-tag for the
latesttag: https://stackoverflow.com/questions/67813980/how-to-point-latest-dist-tag-to-a-previous-version-in-npmAnd release new versions under the appropriate
alphaorbetatags. Maybe as @matevz recommended we should just usenext?