[JosunLP]

Summary

• @bquery/bquery goes from ^1.16.0 to ^1.18.0, with a matching bun.lock update. bun also dropped two unused entries (has-flag, supports-color). The lockfile is accepted with --frozen-lockfile by bun 1.4.2 and by bun 1.3.14, the version CI pins.
• A CHANGELOG.md entry is added under [Unreleased]. The extension stays at version 1.0.0.
• No code changes were needed.

Bridge protocol

• Between 1.16.0 and the 1.18.0 release commit, src/devtools only changed a doc comment.
• BRIDGE_PROTOCOL_VERSION is still 1, and the capabilities and messages are the same.
• The README's minimum for inspected apps (@bquery/bquery ≥ 1.15.0) therefore stays.
• Live check: the extension's BridgeClient was run against createBridgeServer() from the installed 1.18.0. The handshake connected with all 5 capabilities. ping, getSnapshot, getTimeline and getComponentTree all answered.

Impact of 1.18

The extension only uses $, signal/effect/computed, safeHtml and the devtools types. These 1.18 changes therefore do not affect it:

• component morphing, since it defines no components;
• the testing event flags, since it does not use @bquery/bquery/testing;
• the HTTP retry defaults.

Validation

• bun run type-check, lint:check, format:check: all pass.
• bun run test: 190 pass, 0 fail.
• deploy-v3 and deploy-v2, each followed by verifyBuild and package: both pass. The Chromium MV3 and Firefox MV2 zips build.
• bun run test:e2e: 16/16 on the MV3 build. Locally this ran against Chromium 1194, because the sandbox lacks Playwright's headless shell. CI installs the matching browser.

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated the integration’s underlying build while keeping its existing communication protocol unchanged.
  • Apps using the integration continue to be supported when they meet the existing minimum version requirement.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7806d0e2-631f-4364-b71c-df8b1b35078f

📥 Commits

Reviewing files that changed from the base of the PR and between 0732c55 and 630ec1c.

⛔ Files ignored due to path filters: 1

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing: 2

• CHANGELOG.md
• package.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The extension updates @bquery/bquery from ^1.16.0 to ^1.18.0. The changelog records the update and states that the bridge protocol remains v1 and inspected apps still require version 1.15.0 or later.

Changes: Dependency update

Layer / File(s)	Summary
Update dependency and changelog package.json, CHANGELOG.md	The dependency range changes from ^1.16.0 to ^1.18.0. The changelog documents the update and states that the bridge protocol and inspected-app minimum version remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

• bQuery/devtools-extension#1: Introduces the protocol v1 client and its integration with @bquery/bquery, which this PR updates.

Merge Risk: ⚪ Minimal · up to 630ec

The dependency refresh is mergeable with no unresolved review findings.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating the @bquery/bquery dependency to 1.18.0.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}