chore(main): release 1.7.0

[chrischall]

🤖 I have created a release beep boop

1.7.0 (2026-07-29)

Features

• graphql: route declared GraphQL ops through the tab's own Apollo client (#178) (0c3fdf4)

Bug Fixes

• extension-chrome: build content scripts as classic IIFE so Chrome injects them (#175) (f4a3728)
• graphql: address all four tracked nits from PR #178's auto-review (#180) (9d88ac9)

---

This PR was generated with Release Please. See documentation.

[claude]

Claude finished @chrischall's task in 39s —— View job

---

Reviewing PR #177

• Read CLAUDE.md conventions
• Read PR diff
• Review version bumps / cross-package deps
• Post findings

This is the automated release-please version-bump PR (1.6.2 → 1.7.0) — purely mechanical, no hand-written code changes. Verified against CLAUDE.md's "Versioning + releases" section: lockstep version bumps across all workspaces, caret ranges preserved for cross-package @fetchproxy/* deps, extra-files targets (extension-chrome/manifest.json) updated, version.ts marker comment intact, package-lock.json and CHANGELOG.md consistent with the bump. No issues found.

Full review posted as a PR comment.

Verdict: pass

[claude]

Automated release-please version-bump PR — mechanical changes only (manifest, CHANGELOG, package.json versions across all workspaces, lockfile, extra-files like extension-chrome/manifest.json and cli/src/version.ts). All workspace versions are in lockstep at 1.7.0 and cross-package deps use caret ranges (^1.7.0), consistent with CLAUDE.md's versioning conventions. No hand-written logic to review.

No issues found.

Verdict: pass

[github-actions]

✅ Auto-review verdict: pass — Automated release-please version-bump PR (1.6.2 → 1.7.0) is mechanical and correct — all workspace versions bumped in lockstep, cross-package caret ranges preserved, extra-files targets and CHANGELOG updated consistently. No issues found.

[claude]

Review: release-please PR #177 (1.6.2 → 1.7.0)

This is the automated release-please version-bump PR — no hand-written code changes, only mechanical version propagation.

Checked against the conventions in CLAUDE.md ("Versioning + releases"):

• All workspace package.json versions bumped in lockstep to 1.7.0 ✓
• Cross-package @fetchproxy/* deps stay on caret ranges (^1.7.0), not pinned literals — consistent with "Don't add direct dependencies between workspaces using literal versions" ✓
• .release-please-manifest.json, root package.json, and packages/extension-chrome/manifest.json (the documented extra-files target) all updated together ✓
• packages/cli/src/version.ts keeps its x-release-please-version marker comment intact ✓
• package-lock.json regenerated consistently with the same version bumps ✓
• CHANGELOG.md entry matches the PR body summary (features/fixes with correct issue/commit links) ✓

No correctness, security, or convention issues found. Nothing to flag.

Verdict: pass

View job run

[chrischall]

🤖 Created releases:

• v1.7.0

🌻