This repository was archived by the owner on Oct 31, 2026. It is now read-only.
Repository navigation
Conversation
Applied @willbooster/wbfy v21.0.2.
exKAZUu
changed the title
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
Apply the repository conventions supplied by
@willbooster/wbfyv21.0.2.Requirements
wbfybranch and push fixes normally, without force pushing.Customer Summary
Refresh repository configuration and development tooling. Parser code is unchanged.
Technical Summary
Update
@willbooster/wbto 23.0.0 and its lockfile entry, refresh the wbfy badge and generated code-gauge guidance, and extend Bun's release-age exclusions for the Windows code-gauge package.Testing
All five review sessions completed without findings. All PR checks passed, including macOS and Linux platform tests, Rust tests, both fuzz jobs, and semantic PR validation. The readiness check returned
PASSon6aaded5f68030a0d8708e2be36185a4b3eb98f07. No local tests were run; no repository fixes were needed.