Skip to content

chore: update typescript-go submodule#873

Merged
graphite-app[bot] merged 1 commit into
mainfrom
camc314/update-typescript-go-20260406
Apr 6, 2026
Merged

chore: update typescript-go submodule#873
graphite-app[bot] merged 1 commit into
mainfrom
camc314/update-typescript-go-20260406

Conversation

@camc314

@camc314 camc314 commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • update the typescript-go submodule from 025d5aa3913ad54c5eae6be37677d3b85f783fd9 to c0703e66b68b826eedadce353d63fe9f4ea21fb6
  • refresh the local patches/*.patch series against the new upstream base
  • regenerate shims and update find_tsconfig for the NewConfigFileRegistryBuilder signature change

Verification

  • go test ./internal/... against the refreshed patched submodule state
  • CI workflows apply patches/*.patch before build/test via .github/actions/setup

Copilot AI review requested due to automatic review settings April 6, 2026 10:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the typescript-go submodule baseline and refreshes this repo’s shim/patch integration to match upstream API and type surface changes.

Changes:

  • Regenerates/updates shim exports to match upstream symbol/type changes (project, compiler, lsproto).
  • Updates find_tsconfig to use the new NewConfigFileRegistryBuilder signature (adds snapshotID argument).
  • Refreshes the patches/*.patch series metadata against the new upstream base.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.

Show a summary per file
File Description
shim/project/shim.go Adjusts shimmed project APIs/types for upstream signature/generic changes.
shim/lsp/lsproto/shim.go Updates LSP protocol shim surface (drops notebook-related items, adds missing semantic tokens method constant, updates type aliases).
shim/compiler/shim.go Exposes newly available upstream compiler type via shim.
internal/utils/find_tsconfig.go Adapts resolver construction to the updated NewConfigFileRegistryBuilder signature.
patches/0001-Adapt-project-service-for-single-run-mode.patch Refreshes patch header to new upstream base commit.
patches/0002-patch-expose-more-functions-via-the-shim-with-type-f.patch Refreshes patch header to new upstream base commit.
patches/0003-fix-early-return-from-invalid-tsconfig-for-better-er.patch Refreshes patch header to new upstream base commit.
patches/0004-fix-collections-avoid-internal-json-import-in-ordere.patch Refreshes patch header to new upstream base commit.
patches/0005-perf-vfs-cache-ReadFile-results-in-cachedvfs.patch Refreshes patch header to new upstream base commit.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@camc314 camc314 added the 0-merge label Apr 6, 2026

camc314 commented Apr 6, 2026

Copy link
Copy Markdown
Contributor Author

Merge activity

## Summary
- update the `typescript-go` submodule from `025d5aa3913ad54c5eae6be37677d3b85f783fd9` to `c0703e66b68b826eedadce353d63fe9f4ea21fb6`
- refresh the local `patches/*.patch` series against the new upstream base
- regenerate shims and update `find_tsconfig` for the `NewConfigFileRegistryBuilder` signature change

## Verification
- `go test ./internal/...` against the refreshed patched submodule state
- CI workflows apply `patches/*.patch` before build/test via `.github/actions/setup`
@graphite-app graphite-app Bot force-pushed the camc314/update-typescript-go-20260406 branch from 68d3e21 to 588ec3c Compare April 6, 2026 10:35
@graphite-app graphite-app Bot merged commit 588ec3c into main Apr 6, 2026
8 checks passed
@graphite-app graphite-app Bot removed the 0-merge label Apr 6, 2026
@graphite-app graphite-app Bot deleted the camc314/update-typescript-go-20260406 branch April 6, 2026 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants