chore: refresh SDK dependencies and block structure - #37
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates several SDK and platform dependencies to their latest versions across the workspace, as reflected in the lockfile and workspace configuration, and adds a corresponding changeset. Additionally, it configures the test formatter to ignore .test_auth.json and removes the build:dev task from turbo.json. No review comments were provided, so there is no feedback to address.
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[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "passThroughEnv": ["AWS_*", "PL_AWS_*"], | ||
| "outputs": ["./dist/**", "./block-pack/**", "./pkg-*.tgz"] | ||
| }, | ||
| "build:dev": { | ||
| "dependsOn": ["build"], | ||
| "outputs": ["./dist/**"] | ||
| }, | ||
| "do-pack": { |
There was a problem hiding this comment.
build:dev task removed from pipeline
The build:dev task definition has been dropped from the Turbo pipeline. If any workspace package.json still declares a build:dev script, it will continue to run when invoked directly but will no longer benefit from Turbo's caching or dependency ordering (it silently becomes an unconfigured task). Confirming no package still relies on this task would prevent silent regressions in incremental-build workflows.
Prompt To Fix With AI
This is a comment left during a code review.
Path: turbo.json
Line: 29-32
Comment:
**`build:dev` task removed from pipeline**
The `build:dev` task definition has been dropped from the Turbo pipeline. If any workspace `package.json` still declares a `build:dev` script, it will continue to run when invoked directly but will no longer benefit from Turbo's caching or dependency ordering (it silently becomes an unconfigured task). Confirming no package still relies on this task would prevent silent regressions in incremental-build workflows.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
3 participants
Refresh SDK dependencies and block structure via
pnpm upgrade-sdk.This runs:
block-tools structure refresh --update-deps-only+pnpm iblock-tools structure refresh+pnpm ipnpm fmtIncludes a patch changeset ("SDK Update").
Greptile Summary
This PR runs
pnpm upgrade-sdkto refresh SDK dependencies and regenerate the block structure, bumping all Platforma SDK packages by one minor or patch version alongside their internal transitive dependencies.pnpm-workspace.yaml(e.g.@platforma-sdk/model1.79.27 → 1.80.2,@platforma-sdk/ui-vue1.79.27 → 1.80.4). The lockfile regeneration introduces one brand-new transitive package,@milaboratories/columns-collection-driver@0.2.1, pulled in by bothpl-middle-layerandui-vue.turbo.json: Thebuild:devpipeline task is removed as part of the block-structure refresh; workspaces that previously declared abuild:devscript will no longer have Turbo-managed caching or dependency ordering for that task.test/.oxfmtrc.json:.test_auth.jsonis added to the formatter's ignore list so test-credential files are not reformatted.upgrade-sdk.md) is included to version all four block packages.Confidence Score: 4/5
Routine automated SDK upgrade with no application logic changes; the only non-trivial structural edit is the removal of the build:dev Turbo task, which is worth a quick check against workspace package scripts before merging.
All changes are generated by the upgrade-sdk toolchain and follow existing conventions. The dependency bumps are consistent across the catalog, lockfile, and changeset. The one structural change — dropping build:dev from turbo.json — could silently break a workspace incremental-build workflow if that script still exists in a package.json, but no evidence of such a package is visible in the changed files.
turbo.json — confirm no workspace package.json still declares a build:dev script that relied on the removed Turbo task definition.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD WS["pnpm-workspace.yaml\n(catalog pins updated)"] WS --> BT["@platforma-sdk/block-tools\n2.12.3 → 2.12.7"] WS --> MODEL["@platforma-sdk/model\n1.79.27 → 1.80.2"] WS --> UIVUE["@platforma-sdk/ui-vue\n1.79.27 → 1.80.4"] WS --> TENGO["@platforma-sdk/workflow-tengo\n6.7.1 → 6.7.2"] WS --> TB["@platforma-sdk/tengo-builder\n4.0.16 → 4.0.18"] WS --> TEST["@platforma-sdk/test\n1.79.33 → 1.80.5"] WS --> HELPERS["@milaboratories/helpers\n1.14.3 → 1.14.4"] MODEL --> PLMC["@milaboratories/pl-model-common\n1.46.4 → 1.47.1\n(+es-toolkit dep)"] MODEL --> PLMML["@milaboratories/pl-model-middle-layer\n1.30.11 → 1.30.13"] MODEL --> PTABLER["@milaboratories/ptabler-expression-js\n1.2.33 → 1.2.35"] UIVUE --> CCD["@milaboratories/columns-collection-driver\n0.2.1 NEW"] UIVUE --> UIKIT["@milaboratories/uikit\n2.15.13 → 2.15.16"] TEST --> PML["@milaboratories/pl-middle-layer\n1.65.8 → 1.66.4\n(+columns-collection-driver)"] PML --> CCD style CCD fill:#d4edda,stroke:#28a745 style WS fill:#cce5ff,stroke:#004085%%{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 WS["pnpm-workspace.yaml\n(catalog pins updated)"] WS --> BT["@platforma-sdk/block-tools\n2.12.3 → 2.12.7"] WS --> MODEL["@platforma-sdk/model\n1.79.27 → 1.80.2"] WS --> UIVUE["@platforma-sdk/ui-vue\n1.79.27 → 1.80.4"] WS --> TENGO["@platforma-sdk/workflow-tengo\n6.7.1 → 6.7.2"] WS --> TB["@platforma-sdk/tengo-builder\n4.0.16 → 4.0.18"] WS --> TEST["@platforma-sdk/test\n1.79.33 → 1.80.5"] WS --> HELPERS["@milaboratories/helpers\n1.14.3 → 1.14.4"] MODEL --> PLMC["@milaboratories/pl-model-common\n1.46.4 → 1.47.1\n(+es-toolkit dep)"] MODEL --> PLMML["@milaboratories/pl-model-middle-layer\n1.30.11 → 1.30.13"] MODEL --> PTABLER["@milaboratories/ptabler-expression-js\n1.2.33 → 1.2.35"] UIVUE --> CCD["@milaboratories/columns-collection-driver\n0.2.1 NEW"] UIVUE --> UIKIT["@milaboratories/uikit\n2.15.13 → 2.15.16"] TEST --> PML["@milaboratories/pl-middle-layer\n1.65.8 → 1.66.4\n(+columns-collection-driver)"] PML --> CCD style CCD fill:#d4edda,stroke:#28a745 style WS fill:#cce5ff,stroke:#004085Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore: refresh SDK dependencies and bloc..." | Re-trigger Greptile