@oakoss/oakum 0.9.0 → 0.9.2

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## 0.9.2 (2026-11-05)
+
+### Fixed
+
+`oakum init --interactive` and `oakum migrate` decide the printed workflow's install steps from what they read before the prompt. A `package.json` replaced (by a directory, a FIFO, or a symlink loop) while the prompt waited no longer turns an npm workspace's workflow into the Cargo one. A pnpm version that cannot be read for the workflow is now reported before the prompt and before any GitHub lookup.
+
+The `.changeset/README.md` that `init` and `migrate` write no longer says every changed package needs a bump file under `check --strict`: with conventional commits on, a package whose branch commits all release nothing is covered without one, and the README links the coverage guide. It no longer calls naming a dependent in a bump file a bug: a dependent releases without being named, and naming it gives it more than the cascade, such as a binary at `minor` for a library feature its users see. The stale advice about knope reading `.changeset/` is gone.
+
+When `oakum version` replaced a symlinked file with a regular file (a link into `.git`, one it could not follow, or one another write of the run shares) and the run then rolled back, the original text came back as a regular file and nothing said the link was gone. The rollback report now names that file and the link it was, so it can be recreated.
+
+The workflow `init` and `migrate` print skips `oakum check --strict` on the version pull request only when its author and the event sender are `github-actions[bot]`, the account behind the workflow's `secrets.GITHUB_TOKEN`, instead of any bot. Another bot with write access, such as Renovate or a second App, no longer skips the coverage gate by pushing to `oakum/version-packages`. A workflow that opens the version pull request with an App token names the App's `<slug>[bot]` login there; `ci version-pr` says so on stderr when the pull request's author is another bot. Workflows already pasted are unchanged.
+
+## 0.9.1 (2026-11-03)
+
+### Fixed
+
+A release `release` creates no longer takes GitHub's Latest from another package or from a newer version: it takes Latest only when no release holds it, or the holder is an earlier version of the same package, and never as a prerelease. In a multi-package repository, a library release, or a hand-made tag `release` resumes, used to become Latest by GitHub's default, breaking `releases/latest/download/…` URLs such as a binary's installer. When Latest stays elsewhere, `release` says so on stderr with the `gh release edit` command that moves it. When the current holder cannot be read, the release is still created, without taking Latest, and `release` says that too.
+
 ## 0.9.0 (2026-11-02)
 
 ### Added
@@ -509,4 +527,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.8.3.
+Generated by oakum 0.9.1.

package/npm-shrinkwrap.json

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

package/package.json

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