chore: remove xtask and changelog

Signed-off-by: Andrew Lilley Brinker <[email protected]>

Author: alilleybrinker

Cargo.toml

@@ -2,7 +2,7 @@
 # Overall workspace configuration.
 [workspace]
 
-members = ["omnibor", "omnibor-cli", "xtask"]
+members = ["omnibor", "omnibor-cli"]
 resolver = "2"
 
 # Shared settings across packages in the workspace.

README.md

@@ -46,9 +46,8 @@ Analysis."][cisa_report]
 
 | Crate Name    | Type                                                      | Purpose                                   | Links                                                                                                           |
 |:--------------|:----------------------------------------------------------|:------------------------------------------|:----------------------------------------------------------------------------------------------------------------|
-| `omnibor`     | ![Library](https://img.shields.io/badge/Library-darkblue) | OmniBOR Identifiers and Manifests         | [README][omnibor_r] · [Changelog][omnibor_c] · [API Docs][omnibor_d] · [Crate][omnibor_cr] |
-| `omnibor-cli` | ![Binary](https://img.shields.io/badge/Binary-darkgreen)  | CLI for OmniBOR Identifiers and Manifests | [README][omnibor_cli_r] · [Changelog][omnibor_cli_c] · [Crate][omnibor_cli_cr]                    |
-| `xtask`       | ![Binary](https://img.shields.io/badge/Binary-darkgreen)  | OmniBOR Rust Workspace Automation         | [README][xtask_r]                                                                                               |
+| `omnibor`     | ![Library](https://img.shields.io/badge/Library-darkblue) | OmniBOR Identifiers and Manifests         | [README][omnibor_r] · [API Docs][omnibor_d] · [Crate][omnibor_cr] |
+| `omnibor-cli` | ![Binary](https://img.shields.io/badge/Binary-darkgreen)  | CLI for OmniBOR Identifiers and Manifests | [README][omnibor_cli_r] · [Crate][omnibor_cli_cr]                    |
 
 ## Contributing
 
@@ -104,10 +103,8 @@ license text in the [`LICENSE`][license] file.
 [omnibor]: https://omnibor.io
 [omnibor_cr]: https://crates.io/crates/omnibor
 [omnibor_r]: https://github.com/omnibor/omnibor-rs/blob/main/omnibor/README.md
-[omnibor_c]: https://github.com/omnibor/omnibor-rs/blob/main/omnibor/CHANGELOG.md
 [omnibor_d]: https://docs.rs/crate/omnibor/latest
 [omnibor_cli_r]: https://github.com/omnibor/omnibor-rs/blob/main/omnibor-cli/README.md
-[omnibor_cli_c]: https://github.com/omnibor/omnibor-rs/blob/main/omnibor-cli/CHANGELOG.md
 [omnibor_cli_cr]: https://crates.io/crates/omnibor-cli
 [omnibor_spec]: https://github.com/omnibor/spec
 [purl]: https://github.com/package-url/purl-spec

omnibor-cli/CHANGELOG.md

@@ -103,15 +103,7 @@ It is currently pre-`1.0`, which for us means we do not generally aim for
 stability of the APIs exposed, as we are still iterating and designing what
 we consider to be an ideal API for future stabilization.
 
-That said, we do not break stability in point releases.
-
-New version inferences are supported by the use of conventional commits which
-mark the introduction of new features or fixing of bugs. When new releases of
-`omnibor` are made, `git-cliff` checks our requested version bump against its
-determination of the correct version bump based on the `CHANGELOG.md`, and
-produces a release error if it believes we're requesting to bump the wrong
-version. This helps defend against accidentally-incorrect version bumps which
-would violate semantic versioning.
+That said, we do not break stability in patch releases.
 
 ### Minimum Supported Rust Version (MSRV)