crates.io publishing mechanics for v0.2.0 (issue #63)#64
Merged
Conversation
Set up a repeatable NW-only publish path that works around the git `wfa2lib-rs` dependency (which crates.io rejects), and prepare the 0.2.0 release. - Cargo.toml: bump to 0.2.0; expand `exclude` to drop dev/, examples/, notes/, data/, tmp/, and CI/infra files from the crate (116 -> 68 files, ~7 MB of PacBio concordance FASTQs removed; 1.1 MiB compressed). Add a `[lints.rust]` check-cfg declaration so the `#[cfg(feature = "wfa")]` code does not emit `unexpected_cfgs` warnings when built without the feature (e.g. the published crate / `cargo install`). - scripts/publish-crate.sh: strips the WFA git dependency + `wfa` feature from the manifest, runs `cargo publish` (passing through args like --dry-run), and restores the manifest via an EXIT trap. Verified with --dry-run. - justfile/Makefile: add a `publish-crate` recipe/target (kept in sync). - concordance.yml: build with `--features wfa` so its `ALIGN_BACKEND=wfa2` steps exercise the real backend instead of the NW-only stub (regression from the feature-gating in the previous commit). - CHANGELOG.md: new, with a curated 0.2.0 section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
13 tasks
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.
Sets up a repeatable NW-only publish path that works around the git
wfa2lib-rsdependency (which crates.io rejects), prepares the 0.2.0 release, and repairs a CI regression from the earlier WFA feature-gating.What's here
scripts/publish-crate.sh— strips the WFA git dependency +wfafeature from the manifest, runscargo publish(passing through args like--dry-run), then restores the manifest via an EXIT trap. The published crate is Needleman-Wunsch only; WFA stays a source-checkout developer build. Verified end-to-end with--dry-run.justfile/Makefile— apublish-craterecipe/target (kept in sync per the CI check).Cargo.tomlexcludeto dropdev/,examples/,notes/,data/,tmp/, and CI/infra files → 116 → 68 files, ~7 MB of PacBio concordance FASTQs removed (1.1 MiB compressed).[lints.rust]check-cfg declaration so the#[cfg(feature = \"wfa\")]code doesn't emitunexpected_cfgswarnings when built without the feature (e.g.cargo install dada2-rs)..github/workflows/concordance.yml— build with--features wfaso itsALIGN_BACKEND=wfa2steps exercise the real backend instead of the NW-only stub. This repairs a live break: the WFA feature-gating already merged tomain, but without this the concordance workflow builds NW-only and then selectswfa2, hitting the stub panic.CHANGELOG.md— new, with a curated 0.2.0 section.Remaining (not in this PR — needs your crates.io credentials)
cargo loginwith a crates.io token.v0.2.0+ push (also triggersrelease.ymlfor the GitHub Release binaries).just publish-crate(no--dry-run) to upload.Refs #63.
🤖 Generated with Claude Code