Release process tweaks#3389
Merged
Merged
Conversation
Member
novemberborn
commented
Jun 8, 2025
novemberborn
commented
- Verify release commit is in the main branch
- Improve CI status check
- Execute package.json check within jq
- Perform package.json check first
- Update instructions
Typically the tag is pushed first, CI runs, clearing the way for 'main' to be pushed. However we must not release until this is done.
Execute logic within jq; look for any passing workflow and fail if there are none.
No need for Bash, jq can handle this.
It's the most important check, are we publishing what we think we're publishing.
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
1 participant
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.