π·π»ββοΈ GHA release workflow#510
Merged
phatblat merged 81 commits intoreleases/release-1.8.7from Mar 31, 2024
Merged
Conversation
| fatal: Not a valid object name HEAD | MAS_VERSION: 0.0.0
f6278b0 to
30ba6ad
Compare
1597789 to
b696f52
Compare
b696f52 to
ebfd624
Compare
GHA jobs use -f so pinned version of tools are installed, if necessary. New bootstrap-update make target upgrades tools
formerly debug-event
Actually uploading to a release now
Member
Author
|
@rgoldberg I think this new release workflow is finally ready. I'll need to test it on the release branch so you'll probably see a number of test releases soon. |
Merged
Closed
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.
π New
releaseGHA WorkflowThis workflow is triggered based on the publishing of a GitHub Release. The process to kick it off will be as follows:
v1.2.3(with an optional-prerelease.4suffix).releaseworkflow will run.The release progress can be monitored by navigating to the "Actions" tab at the top of the page. If there are problems building the artifacts or publishing to Homebrew core, they will need to be addressed in a PR and a new release. The reason for this is the workflow definition will be taken from the state at the tag for the given release. Deleting and recreating tags or releases is not recommended as people may have already started using
masfrom that version.Jobs in
releaseworkflowstart- SetsDRY_RUNandMAS_VERSIONvariables based on contextpkg-installer- Builds and uploadsmas.pkghomebrew-core- Updates the mas formula in thehomebrew/coretaphomebrew-tap- Waits forhomebrew-coreto succeed and updates themas-cli/homebrew-taptapMore details of each jobbelow.
pkg-installer
Runs the
packagescript to build the macOS installer package file and uploads it to the GitHub release. This file is for those that want to manually install without using Homebrew.homebrew-core
Runs the
brew_core_updatescript using thebrew bump-formula-prcommand. It also creates a new PR with the changes to the homebrew package formulae to updatemain.homebrew-tap
Runs the
brew_tap_updatescript to buildmasbottles and upload them to the GitHub release for mas-cli/homebrew-tap:Uploaded Artifacts
This job will upload artifacts such as the following to the GitHub Release: