feat: exempt every current @willbooster-private package from the release-age gate - #1197
Conversation
…ase-age gate bun, npm, and Yarn match minimum-release-age excludes by exact name (no @scope/* patterns), so newly published packages in our own scope — most recently @willbooster-private/review-booster-cli — were blocked for the full gate period even though the scope resolves only from our own registry. Add the missing scope packages and document that each new @willbooster-private package must be added on first publish. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue where internal CLI tools were being blocked by the release-age gate. Since package managers do not support wildcard scope exclusions, the missing packages were explicitly added to the configuration, and the operational documentation was updated to ensure future packages are registered correctly. Highlights
New Features🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. The gate is set to keep us safe, But internal tools began to chafe. With wildcards gone and names to list, No private package shall be missed. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds three new private packages (@willbooster-private/agent-workflows, @willbooster-private/code-analyzer, and @willbooster-private/review-booster-cli) to the release age gate exclusion list in releaseAgeGate.json. Additionally, it updates the documentation in bunfig.ts to clarify that package managers match exclude entries by exact name rather than scope patterns, requiring manual additions for new packages. There are no review comments, and I have no feedback to provide.
…ent packages Enumerate the packages actually published under the organization's registries — the @willbooster-private Verdaccio scope, the @WillBooster and @exercode npm scopes — and add the missing ones. Personal packages stay out of the list. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
…auto-install too These unscoped packages are also maintained by the organization's members and used by its repositories. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
1 participant
Why
bunx @willbooster-private/review-booster-cli@latest loginfails with:Every version of the CLI is newer than the 7-day gate, and the package is missing from
minimumReleaseAgeExcludes.A scope-wide
@willbooster-private/*exclude would be the ideal fix, but bun, npm, and Yarn all match minimum-release-age excludes by exact name — no@scope/*patterns (verified empirically with bun 1.3.14; only pnpm supports globs, cf. oven-sh/bun#22679). So the scope has to be materialized into literal names.What
configs/releaseAgeGate.jsonwith the organization's currently published packages, enumerated from the registries:@willbooster-private(own Verdaccio): addagent-workflows,code-analyzer,review-booster-cli.@willbooster(npmjs org): addbiome-config, theeslint-config-*packages,renovate-config,tree-measurer.configs/releaseAgeGate.jsonwhen it is first published (per the repo's "prefer an operational rule over code" principle, instead of adding registry-querying sync machinery).Verification
bun verifypasses.configs/applyReleaseAgeGate.sh,bunx @willbooster-private/review-booster-cli@latest --helpresolves and runs.