diff --git a/.changepacks/changepack_log_gCxOcoaFIRE_FxBPz_F-O.json b/.changepacks/changepack_log_gCxOcoaFIRE_FxBPz_F-O.json
new file mode 100644
index 00000000..8bece1bf
--- /dev/null
+++ b/.changepacks/changepack_log_gCxOcoaFIRE_FxBPz_F-O.json
@@ -0,0 +1 @@
+{"changes":{"crates/vespertide-cli/Cargo.toml":"Minor","crates/vespertide-config/Cargo.toml":"Minor","crates/vespertide-core/Cargo.toml":"Minor","crates/vespertide-exporter/Cargo.toml":"Minor","crates/vespertide-loader/Cargo.toml":"Minor","crates/vespertide-lsp/Cargo.toml":"Minor","crates/vespertide-macro/Cargo.toml":"Minor","crates/vespertide-naming/Cargo.toml":"Minor","crates/vespertide-planner/Cargo.toml":"Minor","crates/vespertide-query/Cargo.toml":"Minor","crates/vespertide/Cargo.toml":"Minor"},"note":"align every published crate on one Minor bump so the workspace resolves. The 0.2.1 -> 0.3.0 release mixed Minor and Patch levels across crates, so vespertide/loader/macro/lsp landed on 0.2.2 while core/query/planner/cli/config/exporter/naming landed on 0.3.0, and the root [workspace.dependencies] pins stayed at =0.2.1. cargo then failed with: failed to select a version for the requirement vespertide-core = =0.2.1, candidate versions found which didn't match: 0.3.0. Bumping every crate at the same level keeps the pins and the crate versions in lockstep.","date":"2026-08-20T12:18:27.2498058Z"}
\ No newline at end of file