Skip to content

chore: refresh the structure and raise the SDK to latest - #10

Merged
AStaroverov merged 3 commits into
mainfrom
chore/structure-refresh-vscode-settings
Sep 11, 2026
Merged

AStaroverov merged 3 commits into
mainfrom
chore/structure-refresh-vscode-settings

Conversation

@AStaroverov

@AStaroverov AStaroverov commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

What

sequence-embeddings is already fully migrated — it has a kind with a real
init-params contract, templateParams, and the V3 data model. Nothing to
migrate; this is the housekeeping that was outstanding.

Three commits:

  1. .vscode/settings.json — the one file block-tools structure check
    reported missing.
  2. pnpm upgrade-sdk — the SDK catalog to latest.
  3. The changeset.

Why the SDK bump

The require-latest preflight was already failing on main's content:

Old package '@platforma-sdk/block-tools' detected:
  latest version: 2.15.0
  version used: 2.14.6

And the lock had drifted off the catalog besides — it recorded
specifier: 1.83.7 for @platforma-sdk/test and 4.0.25 for
tengo-builder, versions the committed catalog never declared (it said
1.83.2 and 4.0.23). So the two sides disagreed, and neither held the
current versions.

Both now agree, at the top:

package was now
@platforma-sdk/block-tools 2.14.6 2.15.0
@platforma-sdk/model 1.83.0 1.83.9
@platforma-sdk/ui-vue 1.83.3 1.83.13
@platforma-sdk/test 1.83.2 1.83.14
@platforma-sdk/tengo-builder 4.0.23 4.0.25
@platforma-sdk/workflow-tengo 6.8.3 6.9.0
@platforma-sdk/package-builder 3.15.0 3.16.0

No package.json changed — every package references the catalog — so the diff
is pnpm-workspace.yaml plus the lock.

Verification

  • pnpm check — 12/12 on the new SDK
  • pnpm build:dev-no-software — 12/12
  • block-tools structure checkup to date (0 changes)
  • changeset status — block patch

Note on the anchored column ids

Worth recording since two sibling blocks had a bug here: a scope's columns
are anchored ids minted by getCanonicalOptions, which isColumnUniversalId
rejects. This kind never used that guard — it accepts any non-empty string and
says why ("what the id resolves against is about the anchor it is read against,
not about the shape of the params"), so it is immune to the failure that broke
template apply in redefine-clonotypes and immune-assay-data.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VToqtNVxsuCYJ1z81ngJ7p

@greptile-apps

greptile-apps Bot commented Sep 10, 2026

Copy link
Copy Markdown

No reviewable files after applying ignore patterns.

Output of `block-tools structure refresh` — the one file this block was
missing. `structure check` is a fixpoint again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VToqtNVxsuCYJ1z81ngJ7p
@AStaroverov
AStaroverov force-pushed the chore/structure-refresh-vscode-settings branch from f79ed91 to 3f1de30 Compare September 10, 2026 15:39
AStaroverov and others added 2 commits September 11, 2026 11:28
`pnpm upgrade-sdk`. block-tools 2.14.6 -> 2.15.0, model 1.83.0 -> 1.83.9,
ui-vue 1.83.3 -> 1.83.13, test 1.83.2 -> 1.83.14, tengo-builder 4.0.23 ->
4.0.25, workflow-tengo 6.8.3 -> 6.9.0, package-builder 3.15.0 -> 3.16.0.

The `require-latest` preflight was failing on block-tools, and the lock had
drifted off the catalog besides: it recorded `specifier: 1.83.7` for
`@platforma-sdk/test` and `4.0.25` for tengo-builder, versions the committed
catalog never declared. Both sides now agree, at the top versions.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VToqtNVxsuCYJ1z81ngJ7p
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VToqtNVxsuCYJ1z81ngJ7p
@AStaroverov AStaroverov changed the title chore: add the structurer's .vscode/settings.json chore: refresh the structure and raise the SDK to latest Sep 11, 2026
@AStaroverov
AStaroverov merged commit 9716f70 into main Sep 11, 2026
10 checks passed
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.

1 participant