Repository navigation
chore(sync): merge upstream dev through v2.0.32 - #453
Merged
Merged
Conversation
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.
Issue for this PR
N/A — upstream sync into
integration-v2.Type of change
What does this PR do?
Brings Shuvcode from upstream V2
2.0.30tov2.0.32plus currentdev, at60a5a6ca7c. The source rangee25b7abf89..60a5a6ca7ccontains 78 upstream commits. The latest V2 tag isv2.0.32(843a6c514e);devincludes 45 commits beyond their shared release point. Both refs were rechecked before pushing.2.0.32-shuv.1. Preserves package/bin identity, ports, ShuvTunnel patches, npm updates, fork CI/publishing, and thenightowldefault.packages/scriptto upstream's TypeScript 7 dependency. Reconciles the durable subagent-event and theme expectations, and removes an auto-merged duplicate import. Client/OpenAPI generation was run from source.The fork's previous upstream commit
4267960a5aand current upstream counterparte25b7abf89have the identical tree1840f1a052d65bffe784c2a3b0a6b74f8ea60a97. An ancestry-only merge connects that already integrated snapshot without changing files; the next commit is the regular two-parent merge ofdev. This avoids replaying old source changes. Reviewed the 344-file local diff andgit show --remerge-diff 2a3d757c80.How did you verify your code works?
6c248f7cc7: the killed child remains a zombie under container PID 1, sokill(pid, 0)never reports it gone.6c248f7cc7. These fixtures were left unchanged; the compiled-service smoke passes.https://pkg.pr.new/@solidjs/start@dfb2020dependency returning 404. Console/stats are outside fork CI. Live provider requests, browser e2e, and ShuvTunnel bridge access were not exercised.Screenshots / recordings
Upstream UI changes are covered by the existing TUI and app suites above; no recording captured.
Checklist
Pre-sync fork branch inventory (117 unmerged refs)
Refreshed every fork branch with
git fetch --prune origin '+refs/heads/*:refs/remotes/origin/*'. The localworkbranch matchesorigin/integration-v2at6c248f7cc7; it has no unmerged local work. Reviewed unique commit/file changes and PR states. No missing fix needs reconciliation.Already landed by an equivalent merge or squash:
cursor/ab-check-git-ad5dcursor/antigravity-quota-errors-c5e1cursor/cli-test-env-a867cursor/client-test-contract-de6dcursor/core-test-node-a8d0cursor/dependency-inspection-a7f4cursor/host-deploy-channel-5f72cursor/jj-pr-review-149dcursor/large-pr-diff-87a3cursor/legacy-health-probe-5e6acursor/live-service-binary-8c38cursor/persist-session-log-5c6bcursor/pre-sync-checklist-b97ecursor/remote-port-probes-4afecursor/standalone-global-flag-1969cursor/tui-probe-404-7466cursor/whitespace-check-docs-bdcafleet-hygienefm/sc-361-jj-channelfm/sc-362-agent-modelfm/sc-363-prompt-keysfm/sc-373-jevfm/sc-ci-reenablefm/sc-cursor-378fm/sc-e2e-timelinefm/sc-folderswitch-quarantinefm/sc-i407-toolcall-recoveryfm/sc-i411-watcher-flakefm/sc-i412-run-admissionfm/sc-i438-tab-popoversc-cursor-377sc-permission-fixesPreserved unmerged:
native-supervisoris closed PR #440, outside this sync. Closed proposalscursor/ci-integration-v2-61f7(#415) andcursor/stdin-epipe-listener-968d(#425) were superseded by #420/#441, as recorded in #447. All three branches remain unchanged.Obsolete legacy/V1 or pre-rewrite work: the prior decisions in #447/#450 still apply. Recent tips on eleven legacy branches only update
flake.lock; they add no missing V2 fix. Each of these 82 refs is preserved:191-merge197-consolidate-ask-tool-implementations73-fix-branding-update-message73-fix-branding-upgradeadd-model-favoritesadd-pr-4515config-hot-reloadcopilot/install-bun-version-1-3-3copilot/resolve-upstream-sync-conflictcopilot/sub-pr-105copilot/sub-pr-27copilot/sub-pr-325copilot/sub-pr-97dev-prfeat-v186feat/codex-multi-accountfeat/image-preview-tabsfeat/reconnectfeat/save-favorite-models-desktopfeat/skills-registryfeat/tui-variant-cycle-tooltipfix-prefillfix-tui-img-attachmentsfix/directory-handling-combinedfix/file-viewer-add-img-supportfix/file-viewer-blank-contentfix/mobile-timeline-railfix/root-file-viewintegrationintegration-backup-20260915intergation-streamlinemerge-PRsmerge-v1.0.153merge-v1.1.39mobile-pairingmodel-diag-cleanupopencode/happy-mountainopencode/issue102-20251210030021opencode/issue113-20251211062235opencode/issue114-20251211062613opencode/issue117-20251211083034opencode/issue120-20251211165001opencode/issue126-20251211201237opencode/issue144-20251219021522opencode/issue146-20251219134518opencode/issue151-20251220031612opencode/issue152-20251220033120opencode/issue155-20251220035024opencode/issue157-20251220040932opencode/issue159-20251220111304opencode/issue161-20251220123030opencode/issue167-20251220154038opencode/issue169-20251220160245opencode/issue176-20251221020906opencode/issue178-20251221030922opencode/issue67-20251201020527opencode/issue68-20251201093246opencode/issue70-20251201190836opencode/issue74-20251202181455opencode/issue77-20251202201913opencode/issue78-20251203114126opencode/issue80-20251204034025opencode/issue83-20251204041504opencode/issue86-20251204220607opencode/issue89-20251205204907opencode/issue99-20251209180809plugin-slash-commandsprompt-shuvcodereply-routing-recoveryrevert-pr-4773-subagent-restrictionssewer56-subagent-restrictshuvbotta/anthropic-claude-codeshuvbotta/codemode-fixesshuvcode-devshuvcode-dev-backup-v1.0.223sidebar-fixsync-latest-v2sync-v2-aug13sync-v2-sepsync/upstream-v1.1.20tui-variant-cycle-tooltipv1.1.1.1-integration-testReview follow-up and final validation
Fix commits: 165a69d and eb0fa10.
Release execution
Merged as
d9a29db3fa3d86e81e1d9b016d5488f0afcace33. The normal release workflow for2.0.32-shuv.1/latestis running on that exact commit: https://github.com/shuv1337/shuvcode/actions/runs/39203496138 . Publication and artifact verification are still pending.