Repository navigation
feat(release): publish husky-aware Git hooks in v6.3.0 - #214
Merged
Merged
Conversation
Release highlights: - keep the index fresh in repositories that manage Git hooks with husky: `rgr hooks install` now adds the refresh to the `.husky/<hook>` scripts husky runs - tell agents in other projects exactly which folders a knowledge base serves when `mcpAllowedRoots` refuses them Release details: - **Git hooks:** husky 9 (`.husky/_` shims) and husky 8 (`.husky` with `_/husky.sh`) are recognized; the Ragmir block goes into the tracked `.husky/<hook>` scripts instead of shims husky regenerates, reports carry `manager`, and the CLI asks to commit the changed scripts; other tracked hooks folders still need `--force` - **MCP:** the `mcpAllowedRoots` refusal names the resolved folders instead of raw configuration values such as `.` - **Documentation:** both READMEs follow the conventions most successful open-source READMEs share, with a three-line quick start at the top, a community section, and downloads and stars badges; the CLI reference covers husky Verification: - pass pnpm validate with 542 Core tests and 24 landing tests plus coverage, API, CLI and MCP smoke, builds, packaging, license policy and release smoke checks - pass Quality gate, Linux x64, macOS ARM64 and Windows x64 portability, Commitlint and CodeQL analysis on the feature pull request - install the hooks through husky 9 in a real product monorepo, and refuse an unrelated workspace on a real umbrella knowledge base configured with `mcpAllowedRoots`
|
🎉 This PR is included in version 6.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
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.
Release highlights:
rgr hooks installnowadds the refresh to the
.husky/<hook>scripts husky runsmcpAllowedRootsrefuses themRelease details:
.husky/_shims) and husky 8 (.huskywith_/husky.sh) arerecognized; the Ragmir block goes into the tracked
.husky/<hook>scripts instead of shims huskyregenerates, reports carry
manager, and the CLI asks to commit the changed scripts; othertracked hooks folders still need
--forcemcpAllowedRootsrefusal names the resolved folders instead of raw configurationvalues such as
.share, with a three-line quick start at the top, a community section, and downloads and stars
badges; the CLI reference covers husky
Verification:
smoke, builds, packaging, license policy and release smoke checks
analysis on the feature pull request
on a real umbrella knowledge base configured with
mcpAllowedRoots