chore: back-merge v0.11.0 into next - #112
Merged
Merged
Conversation
Found while rolling v0.10.0 into queeromaha: a site's own `lefthook.yml` cannot override a command defined by the remote. Lefthook merges `lefthook.yml`, then remotes, then `lefthook-local.yml`, so the remote's `unit` command won and ran tests that need a built `dist/` (`lefthook dump` showed the remote's `run`). The README I wrote said local config overrides by name; that was wrong. Fix: the shared `unit` step runs `test:unit:precommit` if the site's `package.json` defines it, otherwise `test:unit` as before. Sites that exclude dist-dependent tests pre-commit (queeromaha, soundry, synthomaha) define that script. README corrected: a site `lefthook.yml` can add commands (e.g. synthomaha's image compression), not override. Verified in throwaway repos consuming this branch as the remote: with the script defined the pre-commit runs it, without it falls back to `test:unit`. Added a unit test for the fallback text. Needs a patch release (0.10.1) before the sites can pin it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
`minimumReleaseAgeExcludes` sat below the `[install.security]` header in `bunfig.toml`, so TOML scoped it to that table instead of `[install]` and the exclusions never applied. Found because the same layout (from the bunfig baseline PRs) made `bun add @taraxvoid/voidflow@0.10.0` fail in queeromaha with `blocked by minimum-release-age`, and Netlify's install failed identically; moving the key under `[install]` made it resolve. Moves the key up (and keeps a blank line before `[install.security]`). Other repos from the baseline PRs likely share the layout. 🤖 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](v0.10.0...v0.11.0) (2026-10-02) ### Features * branch-based release channels (next prerelease, maintenance branches, floating v0) ([#105](#105)) ([978f1db](978f1db)) ### Bug Fixes * **lefthook:** pre-commit unit step honors test:unit:precommit ([#110](#110)) ([0be17d7](0be17d7)) * scope minimumReleaseAgeExcludes under [install] ([#111](#111)) ([9869f82](9869f82)) --- 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>
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.
Brings the v0.11.0 version bump and changelog from main into next. Merge with a merge commit, not a squash, so the branches share history.