@oakoss/oakum 0.9.2 → 0.9.3

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## 0.9.3 (2026-11-06)
+
+### Changed
+
+Reading intent from commits, oakum lists the paths of every commit it attributes by path with one `git` child, instead of two per commit, lists each commit range once per run where `check` listed the range since the base twice, finds the default base once where `status` found it twice, and `check`'s coverage look reads every bump file `HEAD` carries with one `git` child instead of one per file.
+
+An `extra-files` write that meets a duplicated key or a path that is not an object now words the error as every other JSON edit does: "has duplicate keys" where it said "is duplicated", and "is not an object" where it said "is not an object or array".
+
+`release` reads the workspace, the install pin and the reachable tags once per run instead of once per step, takes an existing tag's commit from that tag listing rather than asking git per tag, and checks an ordinary tag name itself rather than running `git check-ref-format` for each, so it spawns fewer `cargo`, `pnpm` and `git` children.
+
+### Fixed
+
+A Cargo member that declares a path dependency under the deprecated `[dev_dependencies]` or `[build_dependencies]` spelling, which Cargo still reads, failed workspace discovery with "missing from manifest", and `version` could not rewrite it. Both spellings are now read.
+
+A workflow that installs oakum with an inexact version flag, such as `cargo install oakum --version=latest` or `cargo binstall oakum --version latest`, was reported as installing oakum without a version. It now names the spec, `latest`, as not an exact version. The outcome was already unverified; only the message changes.
+
+A workflow that pins oakum to a spec spelled `unversioned`, `unparseable-yaml` or `with-not-object`, such as `npm i -g @oakoss/oakum@unparseable-yaml`, was reported as the wrong problem by every command that reads the pin: not valid YAML, an install without a version, or a `with` that is not a mapping. It now says the spec is not an exact version. The outcome was already unverified; only the message changes.
+
+A bump file named like the consume marker's staging copy, such as `.version.oakum-consume.1.2.0.oakum-write.4.md`, made an interrupted consume whose writes had landed read as a rollback, so `version` advised reverting writes that had landed correctly.
+
+When `version` rolls back and cannot move consumed bump files back, the advice to move them back names every one, where it stopped at five and said the rest were named in a list that also stopped at five. It now prints last, after any directories the rollback could not check, so it stays on screen.
+
+`_schema.json` now says what `tag-format` defaults to when unset: `v{{ version }}` while one package is tag-managed, `{{ package }}/v{{ version }}` when several are. `oakum upgrade` rewrites the file.
+
 ## 0.9.2 (2026-11-05)
 
 ### Fixed
@@ -527,4 +551,4 @@ Release workflow checks out the homebrew tap in a subdirectory so the composite
 
 Self-host release CI uploads cargo-dist artifacts into the GitHub Release oakum already created, instead of calling create again.
 
-Generated by oakum 0.9.1.
+Generated by oakum 0.9.2.

package/README.md

@@ -18,7 +18,7 @@ Oakum derives which is which — from the binary targets Cargo resolves for a pa
 
 ## Design rules
 
-**Config expresses preference; facts are derived.** What depends on what, what is publishable, what needs a bump, and which artifact ships are all read from the repository on every run. Templates, titles, the tag format oakum writes, and commit messages are yours, because they describe output rather than the repository, so they cannot go stale. One key is neither: `resolves-dependencies-at`, which states when your package manager fixes a dependency — a fact about the ecosystem that oakum cannot read from your repository. `init` and `upgrade` will write `_schema.json` next to `_config.toml` and a `#:schema ./_schema.json` line; that directive is taplo's, not part of TOML, so editor support varies.
+**Config expresses preference; facts are derived.** What depends on what, what is publishable, what needs a bump, and which artifact ships are all read from the repository on every run. Templates, titles, the tag format oakum writes, and commit messages are yours, because they describe output rather than the repository, so they cannot go stale. One key is neither: `resolves-dependencies-at`, set per package under `[packages.<name>]`, which states when your package manager fixes a dependency — a fact about the ecosystem that oakum cannot read from your repository. `init` and `upgrade` will write `_schema.json` next to `_config.toml` and a `#:schema ./_schema.json` line; that directive is taplo's, not part of TOML, so editor support varies. Every key, with its type and any default, is in the [configuration reference](docs/guide/configuration.md).
 
 **Every command writes only the files it owns.** Oakum does not install git hooks, touch git config, edit `AGENTS.md`, write CI workflows, or create commits you did not ask for. `version` owns the manifests it bumps, the lockfile entries those bumps invalidate, and declared `extra-files`. A Cargo version bump invalidates `Cargo.lock`, and a rewritten workspace range invalidates its `pnpm-lock.yaml` entry, so leaving either stale would break the next `--locked` build or frozen install. Nothing beyond that is written. `check` is pure: it reports drift and names the fix, never applies it.
 

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@oakoss/oakum",
-      "version": "0.9.2"
+      "version": "0.9.3"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.9.2"
+  "version": "0.9.3"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/oakoss/oakum/releases/download/v0.9.2"
+    "https://github.com/oakoss/oakum/releases/download/v0.9.3"
   ],
   "author": "Jace Babin",
   "bin": {
@@ -105,7 +105,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.9.2",
+  "version": "0.9.3",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"