chore(vscode): release 1.6.2#209
Merged
hugocorreia90 merged 1 commit intomainfrom Apr 21, 2026
Merged
Conversation
Tracks engine 1.12.0 (Arc 1 wave 2 + cleanup cascade). Regenerated TypeScript bindings + project schema; no feature changes to the extension itself. - #202 CostOutput + PerModelCostHistorical TypeScript - #203 OptimizeRecommendation cost fields - #206 MaterializationOutput.started_at Full notes in editors/vscode/CHANGELOG.md.
5 tasks
hugocorreia90
added a commit
that referenced
this pull request
Apr 21, 2026
…conds (#210) Engine release 1.12.0 landed a new `StateConfig.transfer_timeout_seconds` field on main, but the vscode schema mirror + TypeScript interface stayed on the pre-1.12.0 shape. Root cause: `just codegen-vscode` fails silently when `editors/vscode/node_modules` is missing (it just errors out of the npm-driven step), so whoever ran the engine-release PR's codegen only got the engine-side schemas regenerated, not the vscode copy. Also syncs `editors/vscode/package-lock.json` to the 1.6.2 version bumped in the package.json by PR #209 — npm install surfaced the drift. No feature change. Unblocks `codegen-drift.yml` on main.
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
Coordinated release cut: vscode-v1.6.2. Tracks engine-v1.12.0 (Arc 1 wave 2 + cleanup cascade). Regenerated TypeScript bindings +
rocky-project.schema.json; no feature changes to the extension itself.What's in this release
Regenerated bindings
CostOutput+PerModelCostHistoricalTypeScript interfaces (newrocky costcommand, feat(engine): Trust-system Arc 2 wave 2 — rocky cost <run_id|latest> #202)OptimizeRecommendationcost fields (feat(engine): Trust-system Arc 1 wave 2 — persist RunRecord on rocky run #203)MaterializationOutput.started_at: string(real per-model wall-clock, feat(engine): stamp real per-model started_at on MaterializationOutput #206)Project schema
schemas/rocky-project.schema.jsonre-exported from the engine's autogenerated source so IDE validation stays in lockstep with 1.12.0.Pre-flight
npm installcleannpm run compileclean[Unreleased]→[1.6.2] — 2026-04-21engines.vscode+@types/vscodestay in lockstep (no drift this cycle — memoryfeedback_vscode_engines_types_triangle)After merge
Tag
vscode-v1.6.2+ push triggersvscode-release.yml(build VSIX + publish to Marketplace viaVSCE_PAT).Sibling releases:
chore/engine-release-1.12.0,chore/dagster-release-1.8.0.