fix: Allow $TURBO_EXTENDS$ in LSP diagnostics#12770
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
$TURBO_EXTENDS$ in LSP diagnostics
anthonyshew
pushed a commit
that referenced
this pull request
May 9, 2026
## Release v2.9.11 > [!CAUTION] > Versioned docs aliasing FAILED. [View logs](https://github.com/vercel/turborepo/actions/runs/25582894003) ### Changes - release(turborepo): 2.9.10 (#12745) (`4b3e7cc`) - ci: Publish VS Code extension on release (#12747) (`1293d22`) - fix: Start daemon for VSCode Extension from the extension itself (#12749) (`07a56d3`) - release(turborepo): 2.9.11-canary.1 (#12748) (`0532c83`) - fix: Include file URIs in LSP lifecycle logs (#12751) (`e64060f`) - fix: Handle JSON decoration visitor depth (#12752) (`5e9cee5`) - fix: Resolve relative `turbo path` in VS Code extension (#12753) (`ca09ff1`) - fix: Preserve Bun nested dependencies during prune (#12754) (`84a161f`) - fix: Prefer installed Turbo for LSP (#12755) (`e8e4df4`) - release(turborepo): 2.9.11-canary.2 (#12750) (`4084382`) - ci: Parallelize LSP release publishing (#12758) (`25aba68`) - fix: Reduce VS Code extension startup popups (#12759) (`3c9ab14`) - fix: Support `turbo.jsonc` in VS Code extension (#12760) (`3b3776b`) - fix: Remove VS Code task key gradient (#12761) (`00c43d4`) - release(turborepo): 2.9.11-canary.3 (#12756) (`bdeb64a`) - chore: Release v2.9.11-canary.4 (#12762) (`20fa5c8`) - ci: Stop VS Code publish from blocking release PR (#12763) (`8a0bd8b`) - release(turborepo): 2.9.11-canary.5 (#12764) (`bfffbaa`) - fix: Publish VS Code extension from release tag (#12765) (`2db74b4`) - fix: Support shimmed VS Code LSP probes (#12767) (`e7c4575`) - release(turborepo): 2.9.11-canary.6 (#12766) (`5a4310d`) - release(turborepo): 2.9.11-canary.7 (#12768) (`87d468b`) - fix: Allow TURBO_EXTENDS in LSP diagnostics (#12770) (`a968db7`) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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
1 participant
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.
Summary
$TURBO_EXTENDS$package-configuration sentinel.$syntax covered by the existing diagnostic.Tests
cargo fmt --checkcargo test -p turborepo-lsppnpm exec lint-staged,turbo run format check:toml,cargo fmt --check,cargo lint,cargo check --workspaceCloses #12769