Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions .changeset/upgrade-sdk.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
"@platforma-open/milaboratories.clonotype-browser-3": patch
"@platforma-open/milaboratories.clonotype-browser-3.model": patch
"@platforma-open/milaboratories.clonotype-browser-3.ui": patch
"@platforma-open/milaboratories.clonotype-browser-3.workflow": patch
---

SDK Update
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,5 +32,5 @@
"oxfmt": "*",
"oxlint": "*"
},
"packageManager": "pnpm@9.14.4+sha512.c8180b3fbe4e4bca02c94234717896b5529740a6cbadf19fa78254270403ea2f27d4e1d46a08a0f56c89b63dc8ebfd3ee53326da720273794e6200fcf0d184ab"
"packageManager": "pnpm@9.12.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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.

Fix in Claude Code

}
40 changes: 20 additions & 20 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions pnpm-workspace.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ catalog:
"@platforma-sdk/ui-vue": 1.80.4
"@platforma-sdk/tengo-builder": 4.0.18
"@platforma-sdk/package-builder": 3.14.1
"@platforma-sdk/block-tools": 2.12.6
"@platforma-sdk/block-tools": 2.12.7

"@platforma-sdk/test": 1.80.3
"@platforma-sdk/test": 1.80.5
"@milaboratories/helpers": 1.14.4

"@platforma-open/milaboratories.runenv-python-3": ^1.7.7
Expand Down
Loading