Skip to content

chore(main): release 1.9.0 - #189

Merged
chrischall merged 2 commits into
mainfrom
release-please--branches--main--components--fetchproxy
Aug 2, 2026
Merged

chore(main): release 1.9.0#189
chrischall merged 2 commits into
mainfrom
release-please--branches--main--components--fetchproxy

Conversation

@chrischall

@chrischall chrischall commented Aug 2, 2026

Copy link
Copy Markdown
Owner

🤖 I have created a release beep boop

1.9.0 (2026-08-02)

Features

  • bootstrap: add createSessionLifter for renewable session lifts (#191) (b2c7049)

Bug Fixes

  • cli: catch every gate-#2 scope rejection, not just three (#187) (b2ecced), closes #185

This PR was generated with Release Please. See documentation.

@chrischall chrischall changed the title chore(main): release 1.8.1 chore(main): release 1.9.0 Aug 2, 2026
@chrischall
chrischall force-pushed the release-please--branches--main--components--fetchproxy branch from 6e04d04 to 0481380 Compare August 2, 2026 17:59
@chrischall chrischall added the release-ready Run CI + review on a release PR — the ship signal label Aug 2, 2026
@github-actions github-actions Bot added the auto-review Trigger Claude + Copilot review on this PR label Aug 2, 2026
@claude

claude Bot commented Aug 2, 2026

Copy link
Copy Markdown

Automated release-please PR: version bump 1.8.0 → 1.9.0 across the root package.json, all workspace package.json files, .release-please-manifest.json, CHANGELOG.md, packages/extension-chrome/manifest.json, packages/cli/src/version.ts, and package-lock.json, plus a bot commit syncing the inter-package @fetchproxy/* caret ranges to ^1.9.0.

Checked:

  • All workspace versions bumped consistently and in lockstep (matches the documented single-version convention).
  • Cross-package deps kept as caret ranges (^1.9.0), not literals, per the "always caret" rule in CLAUDE.md.
  • extension-chrome/manifest.json version bumped alongside the rest, matching the documented extra-files propagation.
  • No hand-edits to version fields outside what release-please/the sync bot generated — no manual version drift.
  • No source/logic changes in this diff, so no new test coverage is needed.

No issues found.

Verdict: pass

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

✅ Auto-review verdict: pass — Automated release-please PR bumping all workspace versions from 1.8.0 to 1.9.0 in lockstep, with cross-package caret ranges synced correctly; no source changes and no issues found.

@chrischall chrischall added the ready-to-merge Owner has reviewed; arm auto-merge to land when CI is green label Aug 2, 2026
@chrischall
chrischall enabled auto-merge (squash) August 2, 2026 18:20
@chrischall
chrischall merged commit c1053c9 into main Aug 2, 2026
16 checks passed
@chrischall
chrischall deleted the release-please--branches--main--components--fetchproxy branch August 2, 2026 18:20
@chrischall

Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-review Trigger Claude + Copilot review on this PR autorelease: tagged ready-to-merge Owner has reviewed; arm auto-merge to land when CI is green release-ready Run CI + review on a release PR — the ship signal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auto-review follow-ups for PR #184: feat(bootstrap,cli): surface partial lifts and clarify bridge errors

1 participant