@oakoss/oakum 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.10.1 (2026-11-12)
+
+### Fixed
+
+A version-managed package that two dependencies cascade into now releases when one of them is excluded from versioning and the other is not. `status`, `version` and `check --explain` dropped it whenever the walk reached it first through the excluded one, since the plan was filtered by the single dependency each package was attributed to. Packages that are not version-managed are now left out while the plan is composed, so nothing cascades through them, and `check --explain` no longer prints `skip (dropped: first reached through a package the plan dropped)`.
+
+`oakum migrate` skips a hook git would not run because the current user may not execute it, as git does. A hook whose only execute bits belong to other users made `migrate` exit 2 reporting it unreadable (`Permission denied`) at mode `0001`, or list it as a gate at mode `0645`, though git ignores it.
+
+The workflow `init`, `migrate`, and `oakum workflow` print gives the release job `actions: read` beside `contents: write`, and, under `--app`, mints its token with `permission-actions: read`. `release` reads the commit's workflow runs to confirm a tag-listening workflow ran, before the first tag as well as after each, and a private repository refuses that read to a token without Actions read: with a tag-listening workflow there, the printed release job failed with exit 1 before writing any tag. A refused read now exits 2 (unverified) and names the permission, and the `--token` next step says the secret needs Actions read on a private repository.
+
+`release` reads a tag that differs from the version only in build metadata as that version's tag, as `check` does: a `tag-format` that adds build metadata (`v{{ version }}+ci`) releases where `release` refused it as rendering a different version.
+
+`oakum upgrade` refreshes `.changeset/README.md` when it is the text an earlier oakum release wrote, so a corrected README reaches repositories that already had one, and `init` and `migrate` replace such a README where they kept it before. `check` notes one, naming `oakum upgrade`, without changing its exit code. A README of your own is left alone, and one oakum cannot read never stops `upgrade`; one that is not UTF-8 no longer stops `init` or `migrate`.
+
 ## 0.10.0 (2026-11-11)
 
 ### Added
@@ -581,4 +595,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.3.
+Generated by oakum 0.10.0.

package/npm-shrinkwrap.json

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

package/package.json

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