Skip to content

chore(dev): bump biome config schema to 2.5.4 - #302

Merged
fro-bot merged 3 commits into
mainfrom
fix/biome-schema-2.5.4
Jul 30, 2026
Merged

chore(dev): bump biome config schema to 2.5.4#302
fro-bot merged 3 commits into
mainfrom
fix/biome-schema-2.5.4

Conversation

@fro-bot

@fro-bot fro-bot commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

Aligns biome.json \ (2.5.32.5.4) with the installed @biomejs/biome@2.5.4 CLI. PR #300 bumped the CLI to 2.5.4 but the \ was left at 2.5.3, leaving one lingering lint info on main:

biome.json:1  Expected: 2.5.4  Found: 2.5.3

Generated via bun run biome migrate --write. Biome-only config migration; no source or behavior changes.

Verification

Check Result
bun install ✅ clean
bun run lint ✅ clean (no infos)
bun run typecheck ✅ clean
bun run build ✅ clean

Changeset

None — dev-tooling config fix; no user-visible changes.

@fro-bot
fro-bot force-pushed the fix/biome-schema-2.5.4 branch 2 times, most recently from a775373 to 7d10e99 Compare July 22, 2026 16:34
@fro-bot

fro-bot commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator Author

Autoheal: schema bump refreshed to 2.5.5

@biomejs/biome is now at 2.5.5 (this branch had targeted 2.5.4, which left a schema version does not match the CLI version 2.5.5 lint info on local runs). This PR was also BEHIND main.

Actions taken:

  • Merged main into fix/biome-schema-2.5.4 (resolved cleanly).
  • Bumped biome.json `` to https://biomejs.dev/schemas/2.5.5/schema.json.
  • Verified bun run lint (no info), bun run typecheck (clean).
  • Committed chore(dev): bump biome config schema to 2.5.5 and pushed.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

@fro-bot

fro-bot commented Jul 25, 2026

Copy link
Copy Markdown
Collaborator Author

Daily autoheal rebase: this branch had fallen BEHIND main after #319/#320 landed. Merged current origin/main into the branch (clean — biome.json keeps the 2.5.5 schema target), verified bun run lint and bun run typecheck clean, and pushed the merge commit (39404b6..e28c095). PR is now MERGEABLE and current with main.

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

@fro-bot

fro-bot commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator Author

Fro Bot Autoheal · 2026-07-27

PR was BEHIND main after recent dep PRs landed (#319, #320, #321, #322). Merged origin/main into fix/biome-schema-2.5.4 (clean merge; biome.json schema target stays at 2.5.5 per the prior branch commit 39404b6).

Verified on the refreshed branch:

  • bun run lint — clean (no infos; resolves the lingering 2.5.3 schema vs CLI 2.5.5 info on main).
  • bun run typecheck — clean.
  • bun run build — clean.

PR is now current with main and MERGEABLE. Ready to merge.

Run Summary — Schedule autoheal · Repo: marcusrbrown/opencode-copilot-delegate · Run ID: 30290410559 · Ref: refs/heads/main · Actor: marcusrbrown · Cache: hit

Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.

fro-bot added 2 commits July 28, 2026 17:28
Aligns biome.json $schema with the installed @biomejs/biome@2.5.4 CLI
(to clear the lingering "Expected: 2.5.4, Found: 2.5.3" lint info on main
after PR #300 bumped the CLI). Biome-only config fix; no user-visible
changes; no changeset needed.
@fro-bot
fro-bot force-pushed the fix/biome-schema-2.5.4 branch from 609904d to 51491f2 Compare July 28, 2026 17:29
@fro-bot
fro-bot enabled auto-merge (squash) July 30, 2026 17:29
@fro-bot
fro-bot merged commit 58e037e into main Jul 30, 2026
3 checks passed
@fro-bot
fro-bot deleted the fix/biome-schema-2.5.4 branch July 30, 2026 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant