@oakoss/oakum 0.3.1 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,25 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.3.2 (2026-09-17)
4
+
5
+ ### Fixed
6
+
7
+ The version pull request is titled `chore(release): version packages`, the same sentence as the version commit. Where a repository takes its squash subject from the pull request title (`squash_merge_commit_title = PR_TITLE`), the old default — `Version Packages` — landed on the default branch instead, and a conventional-commit gate reading there refused the one commit oakum generates; the conventional message it wrote never appeared. GitHub's own default, `COMMIT_OR_PR_TITLE`, takes the subject from the single commit, so a repository left at that setting never saw this, and neither did one merging or rebasing, where the version commit lands carrying its own message. The two defaults sat four lines apart in the same file and disagreed either way. Set `title` in `.changeset/_config.toml` to keep the old string; its schema description now says what it falls back to and that a configured `commit-message` does not move it.
8
+
9
+ `check` names a package that changed outside `HEAD` — staged, edited or untracked — instead of passing over it. The coverage look reads commits while intent is read from the working tree, so a change that is not yet a commit was in neither half, and `--strict` exited 0 on a tree it refuses one commit later. The scope report now names both ends of the diff (`<base>...HEAD`) rather than reading as a comparison against the tree in front of you.
10
+
11
+ What that look could not read is said too: a working tree `git status` cannot walk, or can walk only in part, is reported rather than passed over in silence. Both are advisory, like the rest of this half — they name what went unread without changing any exit outcome. `release` reports them on the same terms.
12
+
13
+ `ci pr-status` says why it posted nothing on each of its three non-posting paths: an empty plan, the version pull request, and `pr-status = "none"`. Only the fork and token failures announced themselves before, so an empty plan and a swallowed failure looked alike from the workflow's side. A leftover plan comment this run's token could not remove is named as well, rather than leaving a line about what was not written to imply nothing was left behind.
14
+
15
+ Every git child now runs under `LC_ALL=C`, so the diagnostics oakum quotes back to you are in one language whatever the surrounding locale.
16
+
17
+ `check` names a package whose coverage a pull request will not receive. Changed packages are read from commits while intent is read from the working tree, so a bump file that is not committed — or one that is committed and has since been edited to name another package — covered a change that was committed, and `--strict` exited 0 while the ref you were about to push exited 1, with nothing said. The mirror of the change named outside `HEAD`, which this release also carries: there the change is invisible, here the coverage is.
18
+
19
+ The question is asked of `HEAD` itself, reading the intent its tree carries rather than guessing from which files are staged. That is what catches the ordinary flow: commit a bump file, touch a second package later, add a line to the file you already have. It costs nothing where there is no intent on disk to rest on, and nothing at all under `conventional-commits`, where both halves already read commits.
20
+
21
+ Advisory, like the rest of that half: it names what a pull request will not get without changing any exit outcome. An uncommitted bump file is the normal state seconds after `oakum add`, so refusing would fire on nearly every local loop.
22
+
3
23
  ## 0.3.1 (2026-09-16)
4
24
 
5
25
  ### Changed
@@ -200,4 +220,4 @@ Release workflow checks out the homebrew tap in a subdirectory so the composite
200
220
 
201
221
  Self-host release CI uploads cargo-dist artifacts into the GitHub Release oakum already created, instead of calling create again.
202
222
 
203
- Generated by oakum 0.3.0.
223
+ Generated by oakum 0.3.1.
@@ -19,7 +19,7 @@
19
19
  "hasInstallScript": true,
20
20
  "license": "MIT",
21
21
  "name": "@oakoss/oakum",
22
- "version": "0.3.1"
22
+ "version": "0.3.2"
23
23
  },
24
24
  "node_modules/detect-libc": {
25
25
  "engines": {
@@ -48,5 +48,5 @@
48
48
  }
49
49
  },
50
50
  "requires": true,
51
- "version": "0.3.1"
51
+ "version": "0.3.2"
52
52
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "artifactDownloadUrls": [
3
- "https://github.com/oakoss/oakum/releases/download/v0.3.1"
3
+ "https://github.com/oakoss/oakum/releases/download/v0.3.2"
4
4
  ],
5
5
  "author": "Jace Babin",
6
6
  "bin": {
@@ -105,7 +105,7 @@
105
105
  "zipExt": ".tar.xz"
106
106
  }
107
107
  },
108
- "version": "0.3.1",
108
+ "version": "0.3.2",
109
109
  "volta": {
110
110
  "node": "18.14.1",
111
111
  "npm": "9.5.0"