Repository navigation
chore: promote the package version during release - #67
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🚀 Salesforce CI⏭️ Deployment cancelledAn earlier step failed (scratch org creation or Dev Hub authorization), so nothing was deployed. Check the workflow logs. 📦 Workflow run, logs and artifacts 🤖 Automated comment by Salesforce CI |
This branch was successfully deployed
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
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.
Summary
release.shasks to promote the new package version right after the install check passes, then promotes it.y, or a failed promotion, stops the release before the alias, install page or release notes are touched, and prints the command to finish by hand.Why
Versions 2.7.0, 2.8.0 and 3.0.0 shipped without being promoted, so production orgs could not install them. They have been promoted by hand. This makes promotion part of every release.
Test plan
sffory,Y,n, empty and failed-promotion answersbash -n scripts/release.sh