Repository navigation
Publish as barbacane-waf + depend on barbacane-libinjection from crates.io - #8
Merged
Merged
Conversation
…s.io The crate name parapet is taken on crates.io, so this engine publishes as barbacane-waf. The library target keeps the name parapet (via [lib] name), and parapet-conformance depends with `package = "barbacane-waf"`, so code using `parapet::` is unchanged. Repoint the libinjection dependency from the git pin to the crates.io release (barbacane-libinjection 0.1.1), set the crate version to 0.1.0 (from 0.0.0), and add a release workflow that publishes on a version tag using CARGO_REGISTRY_TOKEN.
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 engine for crates.io.
parapetis taken, so it publishes asbarbacane-waf.barbacane-waf; the library target keeps the nameparapet([lib] name), andparapet-conformancedepends withpackage = "barbacane-waf", so no code usingparapet::changes.barbacane-libinjection = "0.1.1"(now published).0.1.0(from0.0.0).release.yml: on av*tag it checks the tag matches the crate versionand runs
cargo publish, usingCARGO_REGISTRY_TOKEN(org secret).cargo publish --dry-runpackages and verifies cleanly; the 244 lib tests passagainst the crates.io libinjection. Tagging
v0.1.0after merge publishes it.