@oakoss/oakum 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.1.4 (2026-09-02)
+
+### Fixed
+
+The bump-file README that oakum init and migrate write documents all add flags, --empty/--none, oakum status for the release plan, and that check is unverified until an install pin exists. oakum check --explain is not a CLI flag. The README compiles into the oakum crate so a published package includes it.
+
+Windows builds compile again: same_identity converts cap-std mtime with into_std before comparing to std.
+
+## 0.1.3 (2026-09-02)
+
+### Fixed
+
+Commands now refuse if the repository root is replaced while they run, instead of reading one tree and writing another.
+
 ## 0.1.2 (2026-09-01)
 
 ### Fixed
@@ -14,4 +28,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.1.1.
+Generated by oakum 0.1.3.

package/README.md

@@ -4,7 +4,9 @@ A release tool that derives dependent version bumps from the dependency graph, a
 
 Oakum is the tarred fiber driven into the seams between a ship's planks to keep the hull watertight. This tool exists because releases leak: in one repository, eight fixes were versioned, tagged, and reported as published while never reaching a single user, and every check passed.
 
-**Status: pre-release. Nothing here is stable, and no release has been cut.**
+[![crates.io](https://img.shields.io/crates/v/oakum)](https://crates.io/crates/oakum) [![npm](https://img.shields.io/npm/v/@oakoss/oakum)](https://www.npmjs.com/package/@oakoss/oakum)
+
+**Status:** Published on crates.io, [Homebrew](https://github.com/oakoss/homebrew-tap), and npm (`@oakoss/oakum`); see [releases](https://github.com/oakoss/oakum/releases). Zero-major versioning below 1.0.0 ([ADR-0022](docs/decisions/0022-zero-major-versioning.md)) — APIs and defaults can still change; pin `tool-version` in `.changeset/_config.toml`.
 
 ## What it does that other tools don't
 
@@ -24,7 +26,7 @@ Oakum derives which is which — from the binary targets Cargo resolves for a pa
 
 ## Install
 
-Once the first release lands, three channels, one cargo-dist build behind all of them, so the versions cannot diverge ([ADR-0021](docs/decisions/0021-distribute-through-three-channels.md)):
+Three install channels, one cargo-dist build behind all of them, so the versions cannot diverge ([ADR-0021](docs/decisions/0021-distribute-through-three-channels.md)):
 
 - `cargo install oakum` — builds from crates.io
 - `brew install oakoss/tap/oakum`

package/npm-shrinkwrap.json

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

package/package.json

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