Repository navigation
Conversation
0.10.0 shipped on the pre-channel workflow, so the back-merge job never ran and next-manifest.json still said 0.9.0. Without this the first prerelease would be computed from 0.9.0. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
chore: sync next with main and start it at 0.10.0
First feature PR through the next channel: a one-line README correction (prereleases tag vX.Y.Z-next[.N]). Merging it should make release-please open a prerelease PR on next. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
🤖 I have created a release *beep* *boop* --- ## [0.11.0-next](v0.10.0...v0.11.0-next) (2026-10-02) ### Features * branch-based release channels (next prerelease, maintenance branches, floating v0) ([#105](#105)) ([978f1db](978f1db)) ### Bug Fixes * **docs:** prerelease tags carry the -next suffix ([#109](#109)) ([1c74e3a](1c74e3a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
chore: back-merge v0.11.0 into next
chore: back-merge v0.11.1 into next
Brings the v0.12.0 version bump and changelog from main into next. Merge with a merge commit, not a squash, so the branches share history. --------- Co-authored-by: Tara X V01D <1711810+taraxvoid@users.noreply.github.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [0.13.0-next](v0.12.0...v0.13.0-next) (2026-10-06) ### Features * add conventional-commits release method ([#27](#27)) ([3cd5a86](3cd5a86)) * branch-based release channels (next prerelease, maintenance branches, floating v0) ([#105](#105)) ([978f1db](978f1db)) * **branch-env-map:** single-environment mode (main to prod, PRs to preview) ([#91](#91)) ([bc50b96](bc50b96)) * **justfile:** add lint-only validation target ([b0fbc23](b0fbc23)) * manage branch rulesets as code ([#98](#98)) ([8f9c64b](8f9c64b)) * **npm:** also publish unscoped voidflow mirror ([#69](#69)) ([8cebb32](8cebb32)) * **npm:** publish @taraxvoid/voidflow via trusted publishing ([#67](#67)) ([46b8ebd](46b8ebd)), closes [#65](#65) * **playwright:** add shared definePreviewConfig helper ([#64](#64)) ([#66](#66)) ([4901738](4901738)) * **release:** migrate to release-please ([#71](#71)) ([ecf3961](ecf3961)) * **resolve-env:** add reusable workflow to expose deploy env as a job output ([413cab4](413cab4)) * shared lefthook config for the site stack ([#103](#103)) ([98ea3cd](98ea3cd)) * shared Renovate preset ([#104](#104)) ([649d2b8](649d2b8)) * ship check-licenses as a package bin ([#97](#97)) ([4041a59](4041a59)) * **site-ci.yml:** add GITLEAKS\_LICENSE secret since organizations require it ([5000ccc](5000ccc)) * **site-ci.yml:** add optional GITLEAKS_LICENSE secret for gitleaks Organization plan ([4504d72](4504d72)) * **site-ci.yml:** add support for Playwright installation without OS-level browser dependencies on self-hosted runners ([8fcac78](8fcac78)) * **site-ci:** package-manager, e2e-extra-paths, build-env inputs; skip missing scripts ([#90](#90)) ([cd10551](cd10551)) * **site-ci:** single-environment input for main-only sites ([#102](#102)) ([7be76fd](7be76fd)) * support JSR as npm alternative ([#78](#78)) ([75b68ce](75b68ce)) * **unlighthouse:** add shared Unlighthouse CI runner ([#63](#63)) ([b8a2798](b8a2798)) ### Bug Fixes * also run validate on pushes ([#48](#48)) ([50ede94](50ede94)) * **ci.yml:** disable uv dependency cache since repo has no lockfile/requirements to key it on ([#37](#37)) ([82f81a4](82f81a4)) * **ci:** make npm publish steps idempotent ([#87](#87)) ([5ad4f10](5ad4f10)) * **ci:** resolve e2e base branch on push events ([#96](#96)) ([28e1465](28e1465)) * **cloudflare-deploy:** sanitize deployment-url output for multi-custom-domain deploys ([#49](#49)) ([d4a1eee](d4a1eee)) * **cloudflare-deploy:** warn when --config bypasses the build's deploy redirect ([#85](#85)) ([9b09c1c](9b09c1c)) * **docs:** prerelease tags carry the -next suffix ([#109](#109)) ([1c74e3a](1c74e3a)) * improve Playwright cache invalidation ([#22](#22)) ([f8d863b](f8d863b)) * invalidate py cache ([b5106e4](b5106e4)) * just use github actions a la site-ci.yml instead of using just validate ([de40c3b](de40c3b)) * just use github actions a la site-ci.yml instead of using just validate ([#68](#68)) ([2c90d50](2c90d50)) * **lefthook:** pre-commit unit step honors test:unit:precommit ([#110](#110)) ([0be17d7](0be17d7)) * move JSR publish above NPM to fix issue when npm dirties the tree ([6560f87](6560f87)) * **release.yml:** pass GH_TOKEN through to just validate ([#28](#28)) ([fb573d7](fb573d7)) * **release.yml:** pin --tag-pattern for the auto-bump path ([#38](#38)) ([1ea0abb](1ea0abb)) * **release:** publish to npm with NPM_TOKEN until npm accepts immutable OIDC subjects ([#76](#76)) ([87a407b](87a407b)) * **release:** split into PR-then-tag flow, main is PR-only ([#30](#30)) ([dea2940](dea2940)) * **resolve-env:** use local action path to satisfy zizmor's unpinned-uses policy ([a3c210b](a3c210b)) * scope minimumReleaseAgeExcludes under [install] ([#111](#111)) ([9869f82](9869f82)) * **site-ci:** scan secrets with OSS gitleaks binary ([#95](#95)) ([1fb27ea](1fb27ea)) * **tag-release.yml:** tolerate squash-merge's " (#NN)" suffix ([#33](#33)) ([665b9f3](665b9f3)) * **tag-release:** handle merge-commit release messages ([fb8e067](fb8e067)) * **tag-release:** handle merge-commit release messages ([ba6a6c9](ba6a6c9)) * **unlighthouse:** launch Chrome with --no-sandbox in CI ([#114](#114)) ([67daebb](67daebb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
Brings the v0.12.1 version bump and changelog from main into next. Merge with a merge commit, not a squash, so the branches share history. --------- Co-authored-by: Tara X V01D <1711810+taraxvoid@users.noreply.github.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
#135) Lets a site narrow what the pre-commit typecheck runs, the same way `test:unit:precommit` already narrows the unit step. If a site defines a `check:precommit` script, the hook runs that; otherwise it runs `check` as before. CI keeps calling the full `check`. Purely additive: no site defines `check:precommit` today, so nothing changes until one opts in. First user: ravenflight/rvnflt (pnpm workspace). Its pre-commit typecheck currently runs every package on every commit. With this change it can run only the changed packages and their dependents via `pnpm --filter '...[HEAD]'`. ## Changes - `lefthook/site.yml`: the `typecheck` step prefers `check:precommit` when it's defined. - `README.md`: documents the override, plus the two usual recipes: - bun: `bun test --changed`. Checked locally on bun 1.4.2: it ran 1 of 9 test files with only `site.yml` and its test changed, and it counts staged changes too. - pnpm: `--filter '...[HEAD]'`, with two caveats: fall back to a full run when a root-level file changes, and exclude the root with `--filter '!{.}'`. - `test/lefthook-site.test.ts`: a test for the new branch. ## Test plan - [x] `bun test test/lefthook-site.test.ts`: 7 pass, including `lefthook validate` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
🤖 I have created a release *beep* *boop* --- ## [0.13.0-next.1](v0.13.0-next...v0.13.0-next.1) (2026-10-12) ### Features * **lefthook:** honor check:precommit in the pre-commit typecheck step ([#135](#135)) ([faa203d](faa203d)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
Manual main to next back-merge for v0.12.2 + v0.12.3. Both automated
back-merges (runs 38204136468, 38204886503) stopped on a conflict in
`lefthook/site.yml`.
- `lefthook/site.yml`, `test/lefthook-site.test.ts`: next's side. next
already had main's `{pm}` template change (#119, from the v0.12.0
back-merge), so the main side only added a duplicate `templates:` block.
next also has #135's `check:precommit` step.
- `package.json`, `jsr.json`: keep `0.13.0-next.1`; main's new
`license-checker-rseidelsohn` dependency comes through.
- `CHANGELOG.md`, `.release-please/main-manifest.json`: main's side.
- `.release-please/next-manifest.json` left at `0.13.0-next.1` (newer
than 0.12.3).
`bun test`: 117 pass.
**Merge with a merge commit, not squash.**
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
Back-merges the v0.12.4 release from \`main\` into \`next\`. Conflict resolutions: - \`.release-please/main-manifest.json\`, \`CHANGELOG.md\`: take main (0.12.4 entry) - \`package.json\`, \`jsr.json\`: keep next's \`0.13.0-next.1\` version; main's \`peerDependenciesMeta\` (optional \`@playwright/test\`) merges in - \`lefthook/site.yml\`, \`test/lefthook-site.test.ts\`: keep next's \`check:precommit\` typecheck step and test; dropped a duplicated \`templates:\` block the merge produced - \`bun.lock\`: refreshed for the optional peer \`bun test\`: 117 pass, 0 fail. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> Co-authored-by: ravenflight-releases[bot] <330165707+ravenflight-releases[bot]@users.noreply.github.com>
#145 and #148 were squash-merged, so main's commits never became ancestors of next and the promotion PR (#143) kept conflicting. This is a true merge of origin/main into next. It also removes the duplicate `templates:` block in lefthook/site.yml and the duplicate `parallel: true` README paragraph that #148's squash introduced. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore: back-merge v0.12.4 into next (real merge)
taraxvoid
enabled auto-merge
October 12, 2026 05:16
taraxvoid
added a commit
that referenced
this pull request
Oct 12, 2026
release-please proposed 0.12.5 for the promotion of next (#143) because it walks main by commit date and stops at the v0.12.4 release commit. #135 (`feat(lefthook)`) is dated before v0.12.4, so it was never counted. This documents that in RELEASING.md, and this PR's squash commit carries the footer that makes the stable release 0.13.0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Release-As: 0.13.0 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commits promoted from next:
Merge with a merge commit so each Conventional Commit reaches release-please.