style: fix pre-existing Biome lint errors (main CI red) - #327
Merged
Conversation
added 2 commits
July 30, 2026 14:22
main CI was red on 16 Biome errors (7 formatting + 9 organizeImports) across aep/core/compliance/mcp-posture/react. Applied `biome check --write` (import ordering + formatting only). The 4 remaining noNonNullAssertion findings are warnings (non-blocking) and left as-is. No logic or public-API change, so no release is warranted — hence [skip changeset]. Verified: bun run lint exits 0; affected packages build clean.
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.
main CI has been failing on the Lint (Biome) step (last several runs red) on pre-existing errors unrelated to any single feature branch.
biome checkreported 16 errors across@wasmagent/aep,core,compliance,mcp-posture,react:Applied
biome check --write(import ordering + whitespace only — no logic or public-API change). The 4 remainingnoNonNullAssertionfindings are warnings (non-blocking) and left untouched.[skip changeset]: pure formatting/import-order, so no package release is warranted; the changeset-required check honours the bypass. Verified locally:bun run lintexits 0 and the affected packages build clean.Unblocks main and the provable-chain gate PR (#326).