Publish the way nago-wss does - #30
Merged
Merged
Conversation
cargo read-manifest for the version and cargo info for whether crates.io has it, instead of a hand-rolled crates.io API query. Same house scheme: bumping the version in a PR is the release; a merge without a bump publishes nothing.
pathscale
force-pushed
the
ci/auto-version-bump
branch
from
September 24, 2026 05:22
d9e1161 to
f548bf8
Compare
pathscale
changed the title
added 3 commits
September 24, 2026 12:26
The audit reads Cargo.lock, which is no longer tracked, so it failed on master since that change.
It spent three minutes installing cargo-audit on every push and PR. Tests, clippy and fmt stay automatic.
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
1 participant
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.
Replaces the publish.yml from #29 with nago-wss's, for both crates:
cargo read-manifestfor the version andcargo info --registry crates-iofor whether it's released, instead of a curl query against the crates.io API. endpoint-gen-macros goes first, since endpoint-gen depends on it by version. It runs on a change to either Cargo.toml, and onworkflow_dispatch.The house scheme is unchanged: bump the version in the PR and the merge publishes; a merge without a bump publishes nothing.
The auto-bump workflow that was first on this PR is gone. No other repo has one, so it was invented.
Checked locally: both manifests read, and
cargo inforeports endpoint-gen 1.14.0 and endpoint-gen-macros 1.3.4 as already on crates.io.