chore(browser): Bump extension version to 1.0.2

[yamadashy]

Bumps the browser extension version for the store release containing #1779 (support for GitHub's new repository header).

Checklist

• Run npm run test
• Run npm run lint

🤖 Generated with Claude Code

[github-actions]

⚡ Performance Benchmark

Latest commit:	104afc0 chore(browser): Bump extension version to 1.0.2
Status:	⚡ Benchmark in progress...

Workflow run

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: d8d97372-585f-4498-8cc0-e735cb2488db

📥 Commits

Reviewing files that changed from the base of the PR and between 06cfb7a and 104afc0.

📒 Files selected for processing (1)

• browser/wxt.config.ts

---

📝 Walkthrough

Walkthrough

The browser extension manifest version is updated from 1.0.1 to 1.0.2.

Changes

Browser manifest

Layer / File(s)	Summary
Update manifest version browser/wxt.config.ts	The manifest version changes from 1.0.1 to 1.0.2.

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

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the browser extension version bump to 1.0.2.
Description check	✅ Passed	The description summarizes the version bump, states its release purpose, and confirms that tests and linting were run.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/browser-version-1.0.2

---

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.}

[claude]

Review

LGTM — nothing blocking. This is a clean, correct patch bump. ✅

The version lands exactly where it should: browser/wxt.config.ts:8 is the only place the extension version exists in the repo (browser/package.json is private: true with no version field, so WXT reads it solely from the config). A repo-wide search for 1.0.1 outside lockfiles returns nothing, so there is no second source of truth to drift.

I also confirmed the base commit 06cfb7a is precisely the merge of #1779, so the bump is correctly gated on the fix it claims to ship.

Details

Verified

• Version format — 1.0.2 is 3 dot-separated integers within 0–65535, valid for Chrome, Edge, and AMO. browser_specific_settings.gecko (wxt.config.ts:37-42) has no separate version field, so nothing else needs touching. Patch level is right for a bugfix-only release.
• Release process — .github/workflows/ci-browser.yml runs lint + test only; npm-publish.yml targets the root npm package and never touches browser/. The store upload is manual (zip:chrome / zip:firefox / zip:edge), so this bump is the prerequisite, not a trigger. CONTRIBUTING.md:107-109 documents no changelog or tag step for the extension, so a bare bump is the whole obligation — nothing omitted.
• Tests — no test asserts the manifest version, so nothing breaks. The behavior being released (fix(browser): Support GitHub's new repository header for the Repomix button #1779) is well covered: browser/tests/repomix-integration.test.ts has four cases over findNavigationContainer() (legacy selector, new data-testid selector, precedence when both present, null when neither).
• Security — no attack-surface change. Manifest stays minimal: permissions: ['scripting'], host_permissions: ['https://github.com/*'], icons-only web_accessible_resources, no CSP override. fix(browser): Support GitHub's new repository header for the Repomix button #1779 adds a read-only querySelector and nothing else.

Out of scope for this PR, but worth a follow-up around the store release

1. MutationObservers can accumulate across service-worker wakes. browser/entrypoints/background.ts:47-55 re-injects the content script into every open GitHub tab on each MV3 service-worker wake, and initRepomixIntegration() (content.ts:139) has no re-entry guard — so each injection calls observePageChanges() again and attaches another observer to the same page. The button-exists check at content.ts:83 prevents duplicate buttons, but not duplicate observers. allFrames: true (content.ts:151) multiplies this across sub-frames.

Cheap mitigation:

function initRepomixIntegration(): void {
  // Guard against re-injection from the background service worker (MV3 wakes
  // re-run the content script, which would attach a second observer).
  if ((window as { __repomixInitialized?: boolean }).__repomixInitialized) return;
  (window as { __repomixInitialized?: boolean }).__repomixInitialized = true;
  // ...
}

Separately, the observer at content.ts:124-131 is undebounced on document.body with subtree: true. On pages where the nav container never appears (issues, settings, PR file views), every mutation batch on a DOM-churny site pays a querySelector + regex indefinitely. A short debounce or requestIdleCallback would help.

2. Stale docs under browser/. Not caused by this PR, but they point readers at the wrong place for exactly this kind of change:

• browser/CLAUDE.md:11-24 documents an app/ layout with a checked-in app/manifest.json — that tree no longer exists (it is entrypoints/, public/, utils/, and a generated manifest). Anyone following it would look for the version in the wrong file.
• browser/README.md:23 says "Node.js 22 or higher" while browser/package.json declares "engines": { "node": ">=24.0.1" }.
• browser/README.md:35-53 uses npm run dev chrome / npm run build chrome, but the actual scripts are dev, dev:firefox, build:chrome, build:firefox, build:edge. wxt treats the trailing word as a positional root dir, so the documented commands do not select a browser (and there is no dev:chrome / dev:edge script at all).

---

Note on bot comments: CodeRabbit reviewed and approved this PR with no inline comments, so there was nothing to triage. I could not run gh api .../pulls/1780/comments directly (blocked by the permission system), so this is based on the review status and walkthrough visible via gh pr view --comments.