Repository navigation
Publish the engine to crates.io on release - #197
Merged
Merged
Conversation
The job runs in the crates-io environment, which holds the token, accepts only main and waits for a reviewer. It packages first so a broken package fails before anything is uploaded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The release event checks out its tag, which the crates-io environment now accepts alongside main. A version already on crates.io is skipped, so a rerun or a release after a manual publish of the same version succeeds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Publish engine becomes reusable, like the chart release: the release workflow calls it with its tagged commit once the binaries build, and it still runs by hand from main. The token stays an environment secret, which a called job reads through its own environment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishes
submilli-engineto crates.io as part of a runtime release, and adds a manual workflow for publishing it by hand.Publish engineis reusable, likechart-release.yml. The release workflow calls it with the release's tagged commit once the binaries build, since a published crate version cannot be replaced. Started by hand, it publishes frommain.crates-ioenvironment: it holdsCARGO_REGISTRY_TOKEN, acceptsmainandv*tags, and waits for a reviewer.cargo publish --dry-runfirst, so a package that does not build from its packaged files fails before upload.Depends on #196, which renames the crate to
submilli-engine; running it before that merges fails at the package step. The token can be replaced by crates.io trusted publishing after the first version exists.🤖 Generated with Claude Code