Publish as barbacane-libinjection + release workflow - #5
Merged
Merged
Conversation
The crate names libinjectionrs and libinjection are already taken on crates.io (by the upstream original and an FFI-bindings crate), so this fork publishes under barbacane-libinjection. The library target keeps the name libinjectionrs, and internal path deps use `package = "barbacane-libinjection"`, so no source using `libinjectionrs::` changes. Add .github/workflows/release.yml: on a version tag it checks the tag matches Cargo.toml and runs `cargo publish`, using a CARGO_REGISTRY_TOKEN secret (org-level, or set on this repo).
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.
Prepares the fork for crates.io.
libinjectionrs(upstream) andlibinjection(an FFI-bindings crate) are both taken, so this publishes under
barbacane-libinjection.barbacane-libinjection; the library target keeps thename
libinjectionrs([lib] name), and internal path deps usepackage = "barbacane-libinjection", so no code usinglibinjectionrs::changes.
cargo publish --dry-runpackages and verifies cleanly.repositorypoints at the fork; description notes it is the differential-tested port.
release.yml: on av*tag it checks the tag matchesCargo.tomlandruns
cargo publish, usingCARGO_REGISTRY_TOKEN.Requires
CARGO_REGISTRY_TOKENto be available to this repo (org-levelsecret, or added here) before tagging. Publishing is the first step of the
sequence; parapet (
barbacane-waf) follows once this crate is on crates.io.