@taraxvoid/voidflow 0.11.0-next → 0.11.0

package/README.md

@@ -204,14 +204,14 @@ remotes:
     configs:
       - lefthook/site.yml
 
-# Site-specific differences override the remote by name, e.g. skip tests that
-# need a built dist/ before commit:
-pre-commit:
-  commands:
-    unit:
-      run: bun run test:unit -- --exclude 'test/build.test.ts'
 ```
 
+Lefthook merges `lefthook.yml`, then remotes, then `lefthook-local.yml`, so a
+site's own `lefthook.yml` can add commands (for example image compression) but
+cannot override ones defined here. Differences go through `package.json`
+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 `"prepare": "lefthook install"` so `bun install` wires the hooks. `ref`
 cannot be a commit SHA; pin a release tag.
@@ -287,7 +287,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` (`vX.Y.Z-next[.N]` on `next`),
+Merging it bumps `package.json` (and [`CHANGELOG.md`](CHANGELOG.md) on stable), tags `vX.Y.Z`,
 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.11.0-next",
+    "version": "0.11.0",
     "description": "Shared workflows, actions and tooling for @taraxvoid sites",
     "license": "MIT",
     "keywords": [