Skip to content

Implement release workflow for mess and mess-static - #90

Closed
avcopan wants to merge 7 commits into
masterfrom
release-process
Closed

avcopan wants to merge 7 commits into
masterfrom
release-process

Conversation

@avcopan

@avcopan avcopan commented Nov 11, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

avcopan and others added 7 commits November 11, 2026 16:30
The rattler-build backend reads them from recipe.yaml, so they need not
be repeated in static/pixi.toml.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Both are set to 2026.2.4, the last released version of mess-static, so
that the next release bumps them together.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A release environment holds the tooling, without building MESS. tbump
bumps the version of both packages in one step.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Releases publish the packages instead (see release.yml). Tag pushes no
longer start this workflow by themselves.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A version tag on master builds and tests both environments, publishes
mess and mess-static to the automech channel on prefix.dev with Trusted
Publishing, and makes a GitHub release with the packages and a tarball
of the static executables.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@avcopan avcopan closed this Nov 11, 2026
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