chore: release v0.2.0

[nh13]

🤖 New release

• ref-solver: 0.1.0 -> 0.2.0 (⚠ API breaking changes)

⚠ ref-solver breaking changes

--- failure enum_marked_non_exhaustive: enum marked #[non_exhaustive] ---

Description:
A public enum has been marked #[non_exhaustive]. Pattern-matching on it outside of its crate must now include a wildcard pattern like `_`, or it will fail to compile.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#attr-adding-non-exhaustive
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/enum_marked_non_exhaustive.ron

Failed in:
  enum BuilderError in /tmp/.tmpOFnEhr/ref-solver/src/catalog/builder.rs:19
  enum CatalogCommands in /tmp/.tmpOFnEhr/ref-solver/src/cli/catalog.rs:28

--- failure enum_struct_variant_field_added: pub enum struct variant field added ---

Description:
An enum's exhaustive struct variant has a new field, which has to be included when constructing or matching on this variant.
        ref: https://doc.rust-lang.org/reference/attributes/type_system.html#the-non_exhaustive-attribute
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/enum_struct_variant_field_added.ron

Failed in:
  field species of variant CatalogCommands::Build in /tmp/.tmpOFnEhr/ref-solver/src/cli/catalog.rs:189

--- failure struct_marked_non_exhaustive: struct marked #[non_exhaustive] ---

Description:
A public struct has been marked #[non_exhaustive], which will prevent it from being constructed using a struct literal outside of its crate. It previously had no private fields, so a struct literal could be used to construct it outside its crate.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#attr-adding-non-exhaustive
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/struct_marked_non_exhaustive.ron

Failed in:
  struct KnownReference in /tmp/.tmpOFnEhr/ref-solver/src/core/reference.rs:11
  struct KnownReference in /tmp/.tmpOFnEhr/ref-solver/src/core/reference.rs:11
  struct Contig in /tmp/.tmpOFnEhr/ref-solver/src/core/contig.rs:45
  struct Contig in /tmp/.tmpOFnEhr/ref-solver/src/core/contig.rs:45
  struct ContigMetadata in /tmp/.tmpOFnEhr/ref-solver/src/catalog/builder.rs:106
  struct QueryHeader in /tmp/.tmpOFnEhr/ref-solver/src/core/header.rs:20
  struct QueryHeader in /tmp/.tmpOFnEhr/ref-solver/src/core/header.rs:20

Changelog

0.2.0 - 2026-03-17

Added

• add pre-commit hook for format and lint checks (#7)
• display sha512t24u digests in web UI contig details
• rebuild catalog with sha512t24u digests
• add sha512t24u (GA4GH refget) digest computation

Fixed

• clarify web UI title to specify human genomes (#5)

Other

• add #[non_exhaustive] to public structs and enums (#8)
• Add Zenodo DOI badge to README (#4)
• Add bioconda badge to README (#3)
• release v0.1.0 (#1)

---

This PR was generated with release-plz.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change bumps the package version from 0.1.0 to 0.2.0 in Cargo.toml and adds a corresponding Unreleased 0.2.0 section to CHANGELOG.md. The changelog documents additions including pre-commit hooks, sha512t24u digest support in the web UI and catalog rebuild, and digest computation. It also notes a web UI title clarification and marks public structs and enums with non_exhaustive attributes.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change—a version release bump from 0.1.0 to 0.2.0.
Description check	✅ Passed	The description provides relevant context about the release, including version bump, API-breaking changes, and a detailed changelog.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-plz-2026-02-13T19-39-26Z

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

CHANGELOG.md (1)

14-28: Normalize bullet capitalization for readability.

Lines 14–28 mix add/Add. Use one style across the section for cleaner changelog scanning.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 14 - 28, The changelog bullets in the given
section mix lowercase and capitalized leading verbs (e.g., "add pre-commit
hook..." vs "Add Zenodo DOI badge..."); normalize them to a single style—prefer
starting each bullet with a capitalized first word. Update the entries that
begin with lowercase "add", "rebuild", "display", etc. (including "add
pre-commit hook for format and lint checks", "display sha512t24u digests in web
UI contig details", "rebuild catalog with sha512t24u digests", "add sha512t24u
(GA4GH refget) digest computation", "add #[non_exhaustive] to public structs and
enums") to match the capitalized form used by "Add Zenodo DOI badge..." and "Add
bioconda badge..." so all bullets in this section consistently start with a
capital letter.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@CHANGELOG.md`:
- Around line 14-28: The changelog bullets in the given section mix lowercase
and capitalized leading verbs (e.g., "add pre-commit hook..." vs "Add Zenodo DOI
badge..."); normalize them to a single style—prefer starting each bullet with a
capitalized first word. Update the entries that begin with lowercase "add",
"rebuild", "display", etc. (including "add pre-commit hook for format and lint
checks", "display sha512t24u digests in web UI contig details", "rebuild catalog
with sha512t24u digests", "add sha512t24u (GA4GH refget) digest computation",
"add #[non_exhaustive] to public structs and enums") to match the capitalized
form used by "Add Zenodo DOI badge..." and "Add bioconda badge..." so all
bullets in this section consistently start with a capital letter.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 89a6c89c-745d-4906-b0b1-a2b30bc31cca

📥 Commits

Reviewing files that changed from the base of the PR and between ae0d1c1 and 2db1700.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md
• Cargo.toml