@taraxvoid/voidflow 0.12.1 → 0.13.0-next

package/README.md

@@ -222,17 +222,8 @@ scripts: define `test:unit:precommit` (for example excluding tests that need a
 built `dist/`) and the pre-commit unit step runs it instead of `test:unit`.
 
 Install the binary through mise (`lefthook = "<version>"` in `mise.toml`) and
-set the `prepare` script so `bun install` wires the hooks, but make it tolerate a
-missing binary:
-
-```json
-"prepare": "lefthook install || echo 'lefthook not installed (run mise install); git hooks skipped'"
-```
-
-A bare `lefthook install` fails the whole install step (exit 127) on any runner
-without the `lefthook` binary, which includes GitHub-hosted and self-hosted CI
-images, and CI never runs git hooks anyway. `ref` cannot be a commit SHA; pin a
-release tag.
+set `"prepare": "lefthook install"` so `bun install` wires the hooks. `ref`
+cannot be a commit SHA; pin a release tag.
 
 ## Branch rulesets as code
 
@@ -305,7 +296,7 @@ Semver, released with [release-please](https://github.com/googleapis/release-ple
 | maintenance | `release/N.x` | `0.9.4` | `release-N.x` |
 
 release-please keeps a standing release PR open on each channel's branch, updated as commits land.
-Merging it bumps `package.json` (and [`CHANGELOG.md`](CHANGELOG.md) on stable), tags `vX.Y.Z`,
+Merging it bumps `package.json` (and [`CHANGELOG.md`](CHANGELOG.md) on stable), tags `vX.Y.Z` (`vX.Y.Z-next[.N]` on `next`),
 creates the GitHub release and publishes to npm and JSR under the channel's dist-tag. The PR is
 opened with the org's release-bot GitHub App token (`RELEASE_BOT_CLIENT_ID` /
 `RELEASE_BOT_APP_PRIVATE_KEY`) so CI runs on it.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@taraxvoid/voidflow",
-    "version": "0.12.1",
+    "version": "0.13.0-next",
     "description": "Shared workflows, actions and tooling for @taraxvoid sites",
     "license": "MIT",
     "keywords": [