Repository navigation
Merge upstream main (ca6e09c3e1) - #107
Merged
chrisohearn merged 179 commits intoNov 13, 2026
Merged
Conversation
…us (pingdotgg#23141) Co-authored-by: Julius Marminge <julius0216@outlook.com>
…#29452) Co-authored-by: Julius Marminge <julius0216@outlook.com>
…ingdotgg#33782) Co-authored-by: Julius Marminge <julius0216@outlook.com>
…p tabs (pingdotgg#32854) Co-authored-by: Julius Marminge <julius0216@outlook.com>
…ex at the window edges (pingdotgg#35877) Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…e Welcome page counts (pingdotgg#36242)
… follower hits a defect (pingdotgg#32331)
…tale native subagent (pingdotgg#32307)
…cher reads a large file (pingdotgg#36273)
… into sync/upstream-20261113-2019
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Owner
Author
|
Daily upstream sync: merges Format, lint, typecheck, server tests, the container release build with its smoke test, and the service preflight against the live database passed. Prepared release candidate 🤖 Generated with Claude Code |
chrisohearn
merged commit Nov 13, 2026
8cea406
into
integration/mcp-events-20261109
19 checks passed
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.
Merge 175 upstream commits through
ca6e09c3e1191c8d46a9b97dd658ccb65dde8fcbintointegration/mcp-events-20261109. Candidatebfca0440cdca187f063193f0735ea7f330755c25includes fresh integration56e297dccc5bc07cce51e273c35c933e50ecfb4c, including PRs #88 and #103, without extending the upstream cutoff.Preserve the fork's MCP/events, rollovers and standing instructions, approval access, scheduled model selection, failover, snooze, Codex database isolation, and desktop shutdown handling. Adapt upstream async workspace search and watcher notifications to the fork's separate finder process, retaining both sides' regression coverage. Fork migration files and registry match integration; upstream migration files match the cutoff. Fork migrations stay in
t3_fork_migrations. Regenerate integration CI and remeasure the MCP tool-list budget at 58,304 bytes.Fix two failures found by the integrated gate: supply the event-revision method in the new MCP activity-read fixture, and read the installer's exported
SHELLrather than Bash's implicit default. Both failures reproduced before the fixes; both affected suites pass afterward (17 tests, one platform skip).Validation:
c24b6d71e1ec6c49f9f94453cf7c210706d12979passedvp run check:changed origin/integration/mcp-events-20261109 --concurrency 1on Node 26.12.1: all 41 affected package typechecks, 378 test files / 8,836 tests (7 skipped), format, lint, both knip passes, generated GraphQL, and 90 React compiler checks. The subsequent integration merge changes only three guard files; its exact delta passedvp run check:changed c24b6d71e1ec6c49f9f94453cf7c210706d12979 --concurrency 1and all 34 isolated guard checks. Application/test sources remain identical to the broad passing tree. One prior Vitest startup attempt segfaulted (systemd PID 1340681, no stored core); the unchanged retry passed. No native-crash cause or fix is claimed.All 19 hosted checks and the hosted code/security reviews completed on
bfca0440cdca187f063193f0735ea7f330755c25; there were no review threads or outstanding findings. The mandatoryt3-sync-upstreamwrapper exited 0 after format/lint/typechecks, 8,417 passing server tests (5 skipped), the container build and runtime smoke test, and ready read-only live-database preflights for launcher protocols 3 and 4.Merged at 2026-11-13T21:26:50Z as
8cea4063e46c6c6bc1f6688455c324b155f10765. v0.1.10-preview.20261113.5 was published at 21:28:20Z. Candidate, merge and release tag share treed94a8b437ecfae11a802e66b0b8178003bddb229. The Linux archive andSHA256SUMSare present; the archive digest matches checksum36079008fec8823aa7f337fb7f6a1f1604375d6773bb1acf98e83688c2a0c1c8.Deployment remains pending: a normal
t3-service-updatedeferred for one running thread.0.1.10-preview.20261113.4still serves under the healthy trusted guard; the existing update timer owns deployment. No forced update was used. Paid model evals have not been run.Closes #105.
Prepared by GPT-6.1 Sol through the Codex harness in T3 Code.