add npm package information to release checklist#312
Merged
Conversation
Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com>
pgherveou
reviewed
May 8, 2025
RELEASE.md
Outdated
|
|
||
| # `resolc` NPM package release | ||
|
|
||
| Will happen automatically. After the GH release process described above was successfull, ensure that the newly created release is marked as the latest release. |
Contributor
There was a problem hiding this comment.
ensure that the newly created release is marked as the latest release.
this should not matter anymore, the package will b e published with the tag version
Member
Author
There was a problem hiding this comment.
Right, I will remove it, thanks
pgherveou
approved these changes
May 8, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.