Skip to content

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

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

avcopan wants to merge 2 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 2 commits November 11, 2026 16:42
Both are set to 2026.2.4, the last released version of mess-static, so
that the next release bumps them together. The name and version of
mess-static are held in its recipe only, which the rattler-build
backend reads them from.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
tbump bumps the version of both packages in one step and starts the
release with a tag (see RELEASING.md). 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. A release environment holds the tooling, without building
MESS.

The build workflow becomes reusable, for the release workflow to call,
and no longer uploads mess-static to anaconda.org.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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