chore: refresh SDK dependencies and block structure

[mike-ainsel]

Refresh SDK dependencies and block structure via pnpm upgrade-sdk.

This runs:

• block-tools structure refresh --update-deps-only + pnpm i
• block-tools structure refresh + pnpm i
• pnpm fmt

Includes a patch changeset ("SDK Update").

Greptile Summary

This PR upgrades SDK dependencies via pnpm upgrade-sdk, bumping @platforma-sdk/block-tools (2.12.6→2.12.7), @platforma-sdk/test (1.80.3→1.80.5), and the transitive @milaboratories/pl-middle-layer (1.66.3→1.66.4). A patch changeset marks all four block packages for release, but the package.json packageManager field was unintentionally overwritten as a side-effect.

• @platforma-sdk/block-tools 2.12.6→2.12.7 and @platforma-sdk/test 1.80.3→1.80.5: straightforward patch/minor bumps reflected consistently across pnpm-workspace.yaml and pnpm-lock.yaml.
• packageManager field regressed: changed from pnpm@9.14.4+sha512.c8180b3... to pnpm@9.12.0 — the version was rolled back two minor releases and the sha512 integrity hash was stripped, weakening supply-chain verification for anyone using corepack.

Touched Terms:

Term	Definition	Change in this PR
packageManager	package.json field consumed by corepack to pin the exact package manager binary (version + sha512 hash) for a repo	Downgraded from pnpm@9.14.4+sha512.c8180b3… to pnpm@9.12.0; integrity hash removed
@platforma-sdk/block-tools	CLI tool used to scaffold and refresh Platforma block structure	Bumped from 2.12.6 to 2.12.7 in catalog and lockfile
@platforma-sdk/test	SDK testing utilities for Platforma blocks (wraps vitest + pl-client)	Bumped from 1.80.3 to 1.80.5 (skips 1.80.4) in catalog and lockfile
@milaboratories/pl-middle-layer	Middleware layer that connects the Platforma client to the backend; transitive dependency of @platforma-sdk/test	Updated from 1.66.3 to 1.66.4 in lockfile snapshots
catalog	pnpm workspace catalog — a shared version-pin table in pnpm-workspace.yaml consumed by all workspace packages via specifier: 'catalog:'	Two catalog entries (block-tools, test) bumped to reflect new SDK versions

Confidence Score: 4/5

The SDK bumps are clean and consistent across all files, but the packageManager field was inadvertently downgraded and its integrity hash stripped.

The dependency updates are well-formed and internally consistent. The one real issue is in package.json: the block-tools refresh command appears to have overwritten the packageManager field, rolling it back from pnpm 9.14.4 (with a corepack-verifiable sha512 hash) to pnpm 9.12.0 without a hash. This means any engineer or CI pipeline using corepack will silently switch to an older pnpm binary and lose cryptographic verification of it. The SDK changes themselves look safe to ship once the packageManager regression is resolved.

package.json — the packageManager field needs to be restored to pnpm@9.14.4 with its original sha512 hash (or updated to the intended newer version with a fresh hash).

Important Files Changed

Filename	Overview
.changeset/upgrade-sdk.md	Standard patch changeset file listing all four block sub-packages; no issues.
package.json	packageManager field unintentionally downgraded from pnpm@9.14.4 (with sha512 hash) to pnpm@9.12.0 (hash stripped), weakening supply-chain verification and rolling back the package manager version.
pnpm-workspace.yaml	Catalog bumps block-tools 2.12.6→2.12.7 and test 1.80.3→1.80.5; consistent with lockfile changes.
pnpm-lock.yaml	Generated lockfile; updates block-tools, test, and the transitive pl-middle-layer 1.66.3→1.66.4 consistently across all importers.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pnpm upgrade-sdk\n(block-tools CLI)"] --> B["block-tools structure refresh\n--update-deps-only"]
    B --> C["pnpm i"]
    A --> D["block-tools structure refresh"]
    D --> E["pnpm i"]
    A --> F["pnpm fmt"]

    C --> G["pnpm-workspace.yaml\ncatalog updated"]
    E --> G
    G --> H["@platforma-sdk/block-tools\n2.12.6 → 2.12.7"]
    G --> I["@platforma-sdk/test\n1.80.3 → 1.80.5"]

    H --> J["pnpm-lock.yaml\nlockfile regenerated"]
    I --> J
    J --> K["@milaboratories/pl-middle-layer\n1.66.3 → 1.66.4\n(transitive)"]

    B --> L["package.json modified\n⚠️ packageManager\npnpm@9.14.4+sha512 → pnpm@9.12.0\n(downgrade + hash removed)"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["pnpm upgrade-sdk\n(block-tools CLI)"] --> B["block-tools structure refresh\n--update-deps-only"]
    B --> C["pnpm i"]
    A --> D["block-tools structure refresh"]
    D --> E["pnpm i"]
    A --> F["pnpm fmt"]

    C --> G["pnpm-workspace.yaml\ncatalog updated"]
    E --> G
    G --> H["@platforma-sdk/block-tools\n2.12.6 → 2.12.7"]
    G --> I["@platforma-sdk/test\n1.80.3 → 1.80.5"]

    H --> J["pnpm-lock.yaml\nlockfile regenerated"]
    I --> J
    J --> K["@milaboratories/pl-middle-layer\n1.66.3 → 1.66.4\n(transitive)"]

    B --> L["package.json modified\n⚠️ packageManager\npnpm@9.14.4+sha512 → pnpm@9.12.0\n(downgrade + hash removed)"]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
package.json:35
**pnpm version downgraded and integrity hash removed**

The `packageManager` field changed from `pnpm@9.14.4+sha512.c8180b3...` to `pnpm@9.12.0`. This is a two-part regression: (1) the version is rolled back by two minor releases, which will cause any developer or CI runner relying on corepack to switch to an older binary; (2) the sha512 hash is dropped entirely, removing the cryptographic guarantee that corepack downloads the exact trusted binary. Without the hash, corepack will accept any pnpm binary that self-reports as 9.12.0. Was this change intentional, or did `block-tools structure refresh` inadvertently overwrite the field?

_{Reviews (1): Last reviewed commit: "chore: refresh SDK dependencies and bloc..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Context used - Terms is a types in codebase. Provide the list of ... (source)

[gemini-code-assist]

Code Review

This pull request updates several SDK dependencies, upgrading @platforma-sdk/block-tools to 2.12.7 and @platforma-sdk/test to 1.80.5, along with an update to @milaboratories/pl-middle-layer to 1.66.4. It also downgrades the packageManager version in package.json to pnpm@9.12.0 and adds a corresponding changeset file. No review comments were provided, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[greptile-apps]

pnpm version downgraded and integrity hash removed

The packageManager field changed from pnpm@9.14.4+sha512.c8180b3... to pnpm@9.12.0. This is a two-part regression: (1) the version is rolled back by two minor releases, which will cause any developer or CI runner relying on corepack to switch to an older binary; (2) the sha512 hash is dropped entirely, removing the cryptographic guarantee that corepack downloads the exact trusted binary. Without the hash, corepack will accept any pnpm binary that self-reports as 9.12.0. Was this change intentional, or did block-tools structure refresh inadvertently overwrite the field?

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 35

Comment:
**pnpm version downgraded and integrity hash removed**

The `packageManager` field changed from `pnpm@9.14.4+sha512.c8180b3...` to `pnpm@9.12.0`. This is a two-part regression: (1) the version is rolled back by two minor releases, which will cause any developer or CI runner relying on corepack to switch to an older binary; (2) the sha512 hash is dropped entirely, removing the cryptographic guarantee that corepack downloads the exact trusted binary. Without the hash, corepack will accept any pnpm binary that self-reports as 9.12.0. Was this change intentional, or did `block-tools structure refresh` inadvertently overwrite the field?

How can I resolve this? If you propose a fix, please make it concise.