Implements the release workflow #263
Merged
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
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.
This workflow creates and updates a git tag named "latest". When a new tag with the name matching "Ubuntu*" is pushed to the repository, the "latest" tag is updated to the same commit as the newly pushed tag and a new GitHub Release is created as draft, pointing to the "latest" tag.
The commits added between the previous "latest" and the current one are listed in an automatically generated changelog.
Besides the source code, the latest PDB archives generated by the previous runs of the "build-wsl" workflow are uploaded as release assets.
One human being must then edit the draft release to:
It's important to make sure that the tag points to the exact same commit that generated the last app submited to the store.
The "Ubuntu*" naming convention was chosen to preserve compatibility with the current practice of naming the releases per the latest app version published. For instance, the last release is named Ubuntu22.04LTS/2204.0.10 because it the latest Ubuntu 22.04 LTS app was released at that commit and the store app version is 2204.0.10 (22.04, minor version number 0 build 10).
That way, whenever we need to refer to a specific version of an app for crash analysis we can always refer to its release in GitHub to fetch the appropriate PDB files.