GitHub Actions workflows: releases, MacOS, Windows #2880
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
at this point we are not trying to have different release flavors
the Windows release task does not checkout the F* repository with the git command, but rather with the GitHub REST API, so we need to get the commit hash from outside
|
This PR successfully created https://github.com/FStarLang/FStar/releases/tag/v2023.04.08 |
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 PR:
The task of advancing the version number and refreshing hints is still done by running the current CI workflow with the "Refresh hints and advance version number" box checked.
The workflows created by this PR are still meant be triggered manually through the Actions tab. They have not been scheduled yet.
Thus, here are the steps to produce a F* release:
masterbranch, this build will create a pull request with refreshed hints and the new version number, since that branch is protected. (For any branches other thanmasterand_release, the build directly pushed on the branch and does not advance the version number.)