[exKAZUu]

Why

On darwin-arm64, bunx code-gauge@latest installs code-gauge 4.2.2 but fails because its native addon is missing. Both packages are published correctly. The seven-day release-age policy exempts the main package but blocks its exact-version optional platform dependency, which Bun silently omits. Recently published Exercode companion packages and better-auth-email-otp-reliable are also missing from the exclusions.

Customer Summary

New releases of the affected WillBooster packages can be installed once the updated policy is applied. code-gauge can obtain its matching native addon without a local Rust build.

Technical Summary

Add ten exact package names to packages/wbfy/configs/releaseAgeGate.json, the shared source for repository and global package-manager exclusions: all seven code-gauge platform packages, @exercode/problem-utils-browser, @exercode/problem-utils-llm, and better-auth-email-otp-reliable. @exercode/problem-utils is already registered. Keep the seven-day policy for other packages. No code-gauge repository changes are needed.

Testing

bun run verify-full passed (install, cleanup, typecheck, and all tests). The focused global-release-age and bunfig tests also passed after the additional OSS exclusions (8 tests).

On darwin-arm64 with Bun 1.4.0, a fresh installation of code-gauge 4.2.2 with only the main package exempt reproduced the missing-addon failure. Adding the platform exemption installed three packages instead of two and measured sample.js successfully with install scripts disabled. Using the shared policy, an isolated global config and empty bunx/cache directories also produced one file, one function, NCSS 5, and no errors. Verified the additional OSS package names against their GitHub manifests and npm publications. Other platform binaries were not executed locally. No constant-list regression test was added.

Notes

Distribute the updated policy through wbfy to affected machines and repositories. Existing lockfiles or bunx installations that already omit the addon may need a fresh installation after the policy update.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 updates the release age gate configuration to ensure that critical native addons and specific OSS dependencies are not blocked by the seven-day release policy. By explicitly adding these packages to the exclusion list, the change resolves installation failures where optional platform-specific dependencies were being silently omitted, ensuring proper functionality for tools like code-gauge.

Highlights

• Release Age Gate Policy Update: Updated the release age gate configuration to exempt specific native addons and recent OSS packages from the seven-day restriction.
• Package Exclusions: Added ten new packages to the exclusion list, including all seven platform-specific variants of code-gauge, two Exercode utilities, and better-auth-email-otp-reliable.

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 Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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 was closed, the addon missed, / We added names unto the list. / Now packages flow, the build is sound, / And native code is finally found.

Footnotes

1. Review the Generative AI Prohibited Use Policy, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates packages/wbfy/configs/releaseAgeGate.json to exclude several new packages, including browser/LLM problem utilities and platform-specific code-gauge packages. The review feedback points out that including the Windows-specific package code-gauge-win32-x64-msvc violates the repository style guide, which requires dropping Windows support and ensuring compatibility only with macOS and Linux.