[Chore] Prep minor release notes for 0.3.0 - #234
Merged
Conversation
Author changeset notes for post-0.2.0 user/operator-facing work: task Sleep, Docker standby retention, PR review polish, security fixes, and Blaxel/Docker lifecycle hardening.
Contributor
Author
mrubens
marked this pull request as ready for review
July 12, 2026 04:39
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 12, 2026 04:39
daniel-lxs
added a commit
that referenced
this pull request
Jul 24, 2026
The routing precheck already extracts references like #234, acme/web#42, or ENG-512 into externalReference, but nothing acted on it when the message carried no pasted URL. When the precheck asks for a lookup and URL parsing finds nothing, the reference now resolves deterministically against the deployment's own configuration: repo-qualified numbers must match a configured repository, bare numbers fan out across configured repositories only when there are at most three (labeled per repo so the informed re-route can disambiguate), and Linear-style identifiers fetch directly. Bare references normalize to canonical URLs and reuse the provider registry, so fetch-attempt construction stays single-source. The model still never picks fetch targets: it proposes reference text, code validates against a closed candidate set and executes under the existing shared 8s fail-open deadline. Pasted URLs take precedence. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
daniel-lxs
added a commit
that referenced
this pull request
Jul 24, 2026
…ed repositories (#722) * [Feat] Resolve bare issue references against configured repositories The routing precheck already extracts references like #234, acme/web#42, or ENG-512 into externalReference, but nothing acted on it when the message carried no pasted URL. When the precheck asks for a lookup and URL parsing finds nothing, the reference now resolves deterministically against the deployment's own configuration: repo-qualified numbers must match a configured repository, bare numbers fan out across configured repositories only when there are at most three (labeled per repo so the informed re-route can disambiguate), and Linear-style identifiers fetch directly. Bare references normalize to canonical URLs and reuse the provider registry, so fetch-attempt construction stays single-source. The model still never picks fetch targets: it proposes reference text, code validates against a closed candidate set and executes under the existing shared 8s fail-open deadline. Pasted URLs take precedence. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * [Fix] Stop dispatching MCP fetch attempts after the lookup deadline expires A new fake-timer test for the shared 8s deadline exposed that withExternalLookupTimeout received an already-invoked promise, so an exhausted deadline still fired the next MCP call and merely ignored its result (pre-existing since #693). The helper now takes a thunk and checks the remaining budget before dispatching. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Cap the bare-number fan-out at five repositories instead of skipping it Per review: on deployments with many configured repositories, a bare issue number now fans out across the first five (environment order) rather than resolving to nothing. Non-existent issue numbers drop out at fetch time, so only real matches reach the informed re-route. Smarter candidate selection (routing memory) is a future follow-up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
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.
Related issue
N/A — requested in Slack to kick off another minor release.
Why this PR exists
What changed
Adds nine pending changesets (2 minor, 7 patch) for user/operator-facing work merged since product version
0.2.0. No product code,CHANGELOG.md, orpackage.jsonversion edits — CI will own the version bump after merge.Expected next version:
0.2.0→0.3.0(highest pending level is minor; no other changesets were pending).Minor changes (preview of the CHANGELOG section)
0disables retention). Blaxel standby retention is likewise bounded (defaults 25 / 168 hours), with env knobsDOCKER_STANDBY_MAX_*andBLAXEL_STANDBY_MAX_*documented for operators.Patch changes (preview of the CHANGELOG section)
Reviewing abc1234/Reviewed abc1234), using a linked SHA when a commit URL can be built.~/.roomote/env.sh, which holds deployment secrets such as cloud tokens) is written owner-only (0o600) with~/.roomotelocked to0o700, so other sandbox users cannot read those secrets.Covered by the notes: #219–#220, #222–#231, #233 grouped into the bullets above (Sleep + Docker/Blaxel retention as minor; review UI polish, security, resume/lifecycle as patch).
Skipped for the changelog: #218 LCP logo prioritization (pure performance polish), #221 typed runtime scalar normalization (internal retention path fix), #232 test-fixture identifier scrub.
Impact
Merging this PR does not bump the product version by itself. Once these changesets land on
develop, CI opens or refreshes the Release Roomote 0.3.0 Version PR, which is what actually updatespackage.json/CHANGELOG.mdand starts the promote path.How it was tested
package.json0.2.0, tagv0.2.0, top ofCHANGELOG.md, and version-bump commit1cd5df45ondevelopgit log 1cd5df45..origin/develop --oneline --first-parentand each PR body for user/operator impact.changeset/*.mdfiles beyond READMEcomputeNextVersion('0.2.0', ['minor', 'patch'])→0.3.0lint:fast,check-types:fast,knip) passed on this changeset-only branchChecklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changeset(this PR is the changeset authoring)