Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[217] Updates to wasm-tool's release process #2025

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

alexcrichton
Copy link
Member

Backport of #2021 to assist patch releases.

* Enable releases to happen on `release-*` branches, not just `main`
* PRs to bump versions from `release-*` branches now have the correct
  base branch.
* Logic for publication was moved from `.github/workflows/publish.yml`
  to `.github/actions/publish-release` to be able to share logic with
  `main.yml`. This is because releases from `main` always have the merge
  queue first, hence the `publish.yml` workflow, but releases from a
  `release-*` branch don't have a merge queue meaning it has to run at
  the end of normal CI.
* Some various conditions were tweaked for various conditions to assist
  with external testing of the release workflow, e.g. dropinng
  requirements for repos to be in the `bytecodealliance` organization.
* The `main.yml` CI now runs for all pushes to `release-*` branches,
  enabling artifacts being built for publication.
@alexcrichton alexcrichton enabled auto-merge (squash) February 5, 2025 16:40
@alexcrichton alexcrichton merged commit 1d650f1 into bytecodealliance:release-217 Feb 5, 2025
31 checks passed
@alexcrichton alexcrichton deleted the cifix-217 branch February 5, 2025 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant