Skip to content

Rework release workflow#2212

Open
Mirko-von-Leipzig wants to merge 1 commit into
nextfrom
mirko/release-flow
Open

Rework release workflow#2212
Mirko-von-Leipzig wants to merge 1 commit into
nextfrom
mirko/release-flow

Conversation

@Mirko-von-Leipzig
Copy link
Copy Markdown
Collaborator

@Mirko-von-Leipzig Mirko-von-Leipzig commented Jun 6, 2026

The PR re-implements the current release workflow.

The new workflow is triggered by a release tag push. It first does a dry run of all release artifacts before creating and publishing the github release.

  • Debian package are still built post release since these are slated for removal and I don't want to fiddle with that.
  • Docker images are built as part of dryrun and then published.
  • Crates are dryrun but then are published post release.
    • These are finicky and I didn't want them to hold up the release. We care more about the docker images.

I've improved the crates publishing to be able to rerun in in case it partially failed the previous run. This happened a bunch recently due to crates.io timing out. cargo publish fails if the crates already exist so this works around that by first checking which already exist.

Part of the dryrun will also be generating changelog stuff but that can be done separately depending on our approach.

@Mirko-von-Leipzig Mirko-von-Leipzig added the no changelog This PR does not require an entry in the `CHANGELOG.md` file label Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no changelog This PR does not require an entry in the `CHANGELOG.md` file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant