Skip to content

[216] Updates to wasm-tool's release process#2023

Merged
alexcrichton merged 1 commit intobytecodealliance:release-216from
alexcrichton:cifix-216
Feb 5, 2025
Merged

[216] Updates to wasm-tool's release process#2023
alexcrichton merged 1 commit intobytecodealliance:release-216from
alexcrichton:cifix-216

Conversation

@alexcrichton
Copy link
Copy Markdown
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:17
@alexcrichton alexcrichton merged commit 25a4975 into bytecodealliance:release-216 Feb 5, 2025
@alexcrichton alexcrichton deleted the cifix-216 branch February 5, 2025 16:18
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