Repository navigation
Maintain Python LSP integrations and refresh the November playground - #64
Merged
Merged
Conversation
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.
Pyrefly 1.4 inserted semantic-token modifiers, causing existing string highlights to decode incorrectly. Update the fallback, append three canonical modifiers without shifting existing editor indices, and require Pyrefly 1.4.0. Refresh Python dependencies, regenerate Pyright configuration types, and expose current Pyrefly/ty configuration options.
Refresh the playground to Pyrefly 1.4.0 and ty 0.0.95 WASM with verified archive hashes. Update DOMPurify to 3.4.17 (resolving alerts #35–37), Vite and the LSP packages; align JSON-RPC on 10.0.0.
Validation: 251 tests passed with one existing ty hover xfail; Microsoft Pyright separately 35 passed; zero type errors; Ruff and wheel/sdist builds passed. Both token regressions failed before the fix. Generated files reproduced byte-for-byte. Both WASM tests and Chromium production/concurrency checks passed, including hover, diagnostics, edits and repeated backend switches. npm audit reports zero vulnerabilities.
Maintenance evidence: docs/internal/MAINTENANCE_2026-11-02.md. Planned release: 0.26.0 through the existing publish workflow after CI passes.