Repository navigation
chore(release): prepare 0.4.7 and remote runtime v26 - #833
Merged
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to This release-preparation change updates version numbers, the remote bridge version, and release notes. No actionable merge-blocking risk is evident. Publish remote-v26 before the app release, as planned. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| 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 1… |
| 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. |
| Title check | |
The title clearly identifies the release preparation and the remote runtime version update. It is concise and directly matches the changes. |
| Description check | |
The description includes the required Change and Validation sections, explains the release behavior, lists validation results, and documents the known unit test failure. The additional Release section… |
✨ 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.
Comment @coderabbitai help to get the list of available commands.
devswha
added a commit
that referenced
this pull request
Oct 11, 2026
## Change The usage meters' pace (#513: the mark of an even pace on each bar, the rate under it, "Runs out in …" and the chip's red hairline for a low share) becomes a setting, **Settings → Subscription usage → Show pace**, off by default. With it off the meters read as they did before #513; with it on, as #513 made them. #513 is not released yet, so nobody loses anything: this decides how it first ships. - `usagePace` in `src/lib/settings.ts` (default `false`), read by `UsageMeters` in the three places the pace showed: the chip's hairline, the popover's rows, and the strip's label. - The row sits under **Limit shown**, shown only while **Show plan limits** is on, with Korean, Japanese, Chinese and Turkish text. - No changelog change here: the release PR (#833) words #513's entry with the setting. ## Validation - `bun run typecheck`: pass. `settings.test.ts`, `i18n.test.ts`, `usage.test.ts`: 85 pass. - `scripts/usage-regression.ts` (run through its exported check against a real server and Chrome): pass. New: with plan limits on and the pace not chosen, the strip's label has no "Runs out", no chip is `is-fast`, and the popover has no mark or rate; turning **Show pace** on brings them, and the existing pace checks run from there. - `scripts/settings-pages-demo-regression.ts`: 13 PASS (the Subscription usage page with its new row fits 390px and 320px phones in en, ko, ja and zh). ## Release Client-side only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Release 0.4.7, from main at 80ca9bb (47 PRs since v0.4.6).
package.jsonandherdr-plugin.toml: 0.4.7.[Unreleased]becomes[0.4.7] - 2026-10-12, with the compare links.release-summaries.json: 0.4.7 in en/ko/ja/zh/tr (6 new, 6 improved, 5 fixed). The Turkish lines are not checked by a native speaker.REMOTE_BUNDLE_VERSION25 -> 26. Since v0.4.5's runtime the bridge gained Hermes transcripts (feat(chat): support hermes agent transcripts #604), conversation pushes (perf(chat): read the conversation when its transcript changes, not every 2 s #689) and Grok/Antigravity activity (fix(chat): show native Grok and Antigravity activity #816), soremote-v26is published before the app release.Not in this release: #606.
Validation
bun scripts/release-notes.ts 0.4.7renders the summaries and the full changelog (235 lines).bun run typecheckandbun run build: pass.TMPDIR=/tmp bun run test:unit: one failure,server/voice.test.ts("audio.webm" vs "clip.webm"), which fails the same way on unmodifiedmainon this Mac (Bun 1.4.0); CI runs Bun 1.4.2.Release
After this merges and its CI on
mainpasses: pushremote-v26, wait for its release, then run the Release workflow with0.4.7.