Repository navigation
fix(release): backport ten user-reported fixes to 0.12.0 line - #31968
Conversation
…e a slow fetch as 409 (#30258) The dashboard Update handler fetched the tracked remote under a 30s deadline, half the 60s the fast-forward that follows it gets, and reported a timeout as HTTP 500. A reachable-but-slow fetch (a large pack over a thin link) was killed and surfaced as a server error. Raise the fetch deadline to 60s to match the fast-forward's own bound, and answer a genuine overrun with 409 (retryable) like the adjacent non-zero-rc refusal, with a clear reason. The fetch still runs and the failure stays surfaced; code git_fetch_failed is unchanged so the UI keeps showing the reason. Closes #30191 Co-authored-by: kirocrew-agent <agent@kirocrew.local> (cherry picked from commit 8b96d2a)
A mid-wave digest is composed when its chunk fires, with the number of members running at that moment, and can then wait in a busy parent's queue while those members finish. The parent read "1 still running" for a member that had already ended. Each mid-wave digest now dates its counts in a sentence right after the header; the header line, which a channel parent's meta-less rows are parsed by, the spawn guidance and the card meta are unchanged. Closes #15220 (cherry picked from commit a68f38e)
…0498) Back or Forward onto the history entry of a session this tab saw closed rewrote the entry to the session on screen and said nothing, so the enabled arrow looked dead. The chat page's history reader now raises the pane notice with a new `closed` kind ("That session was closed. Find its transcript in Older Sessions.") on both of those repairs, and clears it when the next step lands on a live session. Builds on #14765 by @tmack8001. Closes #14762 (cherry picked from commit 91c35d3)
aws-cli v1 is a Python program. The Polly consent probe (through cloud.aws.run_aws) and Polly synthesis handed it the gateway's PYTHONPATH/PYTHONHOME, so on such a host the voice list worked while consent and synthesis failed. Both children now get their environment through sandbox.without_python_env, as the voice catalogue already does; run_aws keeps aws_spawn_env's widened PATH. Builds on #14207 by @leonlaiyc. Co-authored-by: Leon <leon.lai.yc@gmail.com> (cherry picked from commit b1f4c11)
An existing path whose name carries non-ASCII punctuation or a symbol (the middle dot in a transliterated name, an ideographic comma, a fullwidth plus or bracket) failed the path-shape pre-filter, so the stat probe never ran and the chip stayed plain inline code. The shape now admits every non-ASCII punctuation mark and symbol inside a segment, on both the POSIX and the drive-rooted shape, and lets a closing bracket of any script end a path. The ASCII exclusions that keep a command or URL from classifying are unchanged, and a trailing sentence mark such as an ideographic full stop still cannot end one. Closes #16890 (cherry picked from commit a0a2930)
…30611) The EC2 bootstrap fetched kiro-cli from desktop-release.q.us-east-1.amazonaws.com, a name inside the private DNS zone an Amazon Q interface VPC endpoint creates. In a VPC carrying that endpoint the lookup returned NXDOMAIN and every launch failed. The bootstrap now fetches the musl zip of the packaging/kiro-cli-version release from prod.download.cli.kiro.dev, the host the official installer uses, and checks it against its packaging/kiro-cli-sha256 line before unzipping. The DNS preflight checks the new host, and its error no longer blames an AWS endpoint. (cherry picked from commit 3ae48d9)
…30458) When an app's setup.onInstall script exits non-zero during a registry install or update, the output that says why lived only in the install response. Once that response was gone, all that remained was a generic "install script failed (exit N)" event. The install now also writes that output tail to the gateway log as one warning line: redacted off the event loop through the context-aware log redactor, then cut to a fixed size, and quoted so a newline in the output cannot start a new log line. Closes #11078 (cherry picked from commit 1e51712)
…0948) A Side Chat cancel hands the question back to the composer when its answer lands. If a socket re-read dropped the card first, the text waits in a record that is capped at 50 cards and replaced on every close, so more than 50 dropped cards, or a second conversation opened and closed before the answer, threw the question away. The tab now marks each cancel it sends as waiting until the answer settles, and the record keeps a waiting card's text through the cap and through later closes. (cherry picked from commit d583482)
…1151) A gateway that cannot list deployments at all (native Windows) answers GET /api/deploy/list with HTTP 200 and its reason in `error`. The Deploy page never read that field, so it showed "No deployments yet" and a hint to wait a couple of minutes, hiding the reason the gateway sent. The page now shows that reason through the Deployments section's existing error notice and skips the empty state and the tag-delay hint while it is set, as the Publish panel already does. Closes #27882 (cherry picked from commit d565591)
UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)UX-level review of UX-Verdict: PASS cannot evaluate: missing screenshots of the closed-session notice and the deployment-list reason. The PR attaches no image, so the blind read did not run. Evidence gaps
Notes
[UX-REVIEWED] 76d5fbf Description read[DESCRIPTION-READ] dcbf9deb3c5f7da224a0ac79006ee4103ca179d5c798bc8ea655c8a0eb72ddf9 That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS No design-level concerns: these are unchanged cherry-picks of fixes already merged on Notes
[DESIGN-REVIEWED] 76d5fbf Description read[DESCRIPTION-READ] cfc39afc2acac162d3dd4c31ff8728f87fb9763a75b0220cc1f9beeb3387f950 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing blocks: each of the ten picks is a fix already on Notes
What this change shipsInventory (10 items) — 10 justifiedIntent: ship ten user-reported fixes that already merged on
[FIRST-PRINCIPLES-REVIEWED] 76d5fbf Description read[DESCRIPTION-READ] 1609730dca4661ea72bcab19439bb26c19400821ef358a74c5a91fa0cdee8039 That sha256 names the PR description this verdict read. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: Bring ten small fixes for user-reported issues that merged on
mainafterv0.12.0ontorelease/0.12.0, one commit per fix, so the 0.12.1 patch ships them and each one can be reverted alone.Why it matters
package.jsonis not at the app root installs no npm dependencies.Not a goal
main; nothing is changed only here.CHANGELOG.mdchange. Cuttingv0.12.1-rc.Nand the bare tag follow docs/build/release.md and stay with the maintainers.credential_processsetting.What changed (motivation → approach → change)
Each main squash commit was cherry-picked with
-xontorelease/0.12.0@c8dedc263a, in merge order, one commit each, keeping its original author.8b96d2ad93ad8e4b5d55a68f38ec154847d2f1d591c35d326e864a5e179db1f4c11d33536be9d1bca0a29308f24ef4f3e79c3ae48d99c851fbbe8de2package.jsonlives087043e1f858f4ee94081e51712ee83e580a3721d583482fe7b20f91075ed565591d0276d5fbf314No hunk was resolved by hand. Every pick's added and removed lines are identical to its main commit. #30551 uses
sandbox_spawn.without_python_env, which already exists on this branch; it does not change the sandbox.builder-security checked: no pick changes a bind, a listener, an auth check, an ingress rule or a storage grant. #30258's handler change raises the pre-apply fetch timeout from 30 s to 60 s and answers a timeout with 409 instead of 500. #30611 is a supply-chain change in the tightening direction: the EC2 bootstrap now fetches the pinned kiro-cli 2.27.1 from
prod.download.cli.kiro.devinstead oflatestfromdesktop-release.q.us-east-1.amazonaws.com, and verifies it withsha256sum -cagainst two checksums it adds topackaging/kiro-cli-sha256. 2.27.1 is the version this branch already pins inpackaging/kiro-cli-version.Backwards compatibility
Compatible: each change is the one already merged on
main, and each PR's own compatibility note applies unchanged. A client that read #30258's timeout as a 500 now gets a 409 with a retry hint.Removes nothing: no pick hides, deletes or renames anything 0.12.0 accepts.
Tests
Proof: not provable -- other: a backport of main commits whose proofs ran on their own PRs
release/*, so the related set was run here: every touched test file plus every test file that imports a touched module, 182 files, one pytest process per batch of 20,-n 0. 11622 passed, none failed.src/i18n/*.test.ts*catalog test, 62 files, 1421 passed.Manual verification
N/A - every pick was verified on its own main PR. The 0.12.1 RC soak is the end-to-end check.
Screenshots / video
Why no screenshot: each frontend change here is applied from
mainunchanged; its look is reviewed on its own PR, not here.Related Issues
Backport to the 0.12 line for 0.12.1 of #30258, #30500, #30498, #30551, #30566, #30611, #30460, #30458, #30948 and #31151. Source issues: #30191, #15220, #14762, #16629, #16890, #7822, #10583, #11078, #25813, #27882.
Sibling sweep
Siblings: none -- each source PR carried its own sibling sweep; this PR only carries those fixes.
Pattern harvest
Not generalizable: this PR only carries fixes already on
main. Each source PR has its own harvest.Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.