Repository navigation
Bump to 1.39.0 - #68
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
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.
Releases vscode 1.39.0. #67 carries a FunctionElement rename into the System Composer interface dictionary's catalog in both editors, and pins data-explorer-core v1.39.0. The CHANGELOG entry is dated 2026-10-16.
Setup: origin/main = d0141e3 (asserted). npm ci rc 0; the installed data-explorer-core is 1.39.0, and the locked sha 8e334082 matches core tag v1.39.0 (annotated tag a4ed17ae).
npm run verify rc 0: typecheck and build passed; vitest had 169/169 test files and 3264/3264 tests passing; check:leak passed 3 of 3 checks (5 needles, 646 lockfile resolutions, 4 local-only paths).
npm run test:integration rc 0 (Exit code 0): 191 passing, 1 pending, 0 failing. The pending test is test-integration/suite/cutPasteUndo.test.ts:114, 'a same-document move applies as ONE WorkspaceEdit and a single undo restores the original'. It is skipped on purpose with this.skip(). Its suiteSetup canary (hostUndoWorks) found that this local headless VS Code test host does not apply
undoto an editor: a plaintext canary edit survived undo. The run printed '[cutPasteUndo] SKIPPING the undo assertion ... The contract still runs on CI.' This is a limit of the local host, not a regression.