Repository navigation
Pin Grida FX 0.6.1 and release grida 0.5.3 - #1103
Merged
Merged
Conversation
Pins @grida/fx to 0.6.0 (from 0.5.1), so `grida fx` runs FX 0.6.0: node bodies, builders and stand-ins in TypeScript, hosted by @grida/fx on Node 24 or later (gridaco/fx#71). Host contract unchanged (HOST_CONTRACT 1), so the launcher needs no change. - packages/grida-cli/package.json: @grida/fx 0.6.0 - pnpm-lock.yaml, pnpm-workspace.yaml: minimumReleaseAgeExclude names the FX 0.6.0 packages - apps/docs/sources.lock.json: FX guide at gridaco/fx@v0.6.0
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe CLI package version changes from 0.5.2 to 0.5.3, and its ChangesCLI release alignment
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Docstring Coverage |  |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
| Description check | |
The description clearly explains the FX pin to 0.6.1, the grida version bump to 0.5.3, related generated-file updates, and validation results. |
| Title check | |
The title clearly and concisely summarizes the two main changes: pinning Grida FX to 0.6.1 and releasing grida 0.5.3. |
✨ Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Moves the @grida/fx pin to 0.6.1 and bumps grida to 0.5.3 so the release workflow publishes it on merge. Host contract unchanged (HOST_CONTRACT 1). - packages/grida-cli/package.json: @grida/fx 0.6.1, version 0.5.3 - crates/grida-cli/Cargo.toml, Cargo.lock: 0.5.3; notices regenerated - pnpm-lock.yaml, pnpm-workspace.yaml: minimumReleaseAgeExclude names the FX 0.6.1 packages - apps/docs/sources.lock.json: FX guide at gridaco/fx@v0.6.1
softmarshmallow
changed the title
softmarshmallow
marked this pull request as ready for review
October 13, 2026 21:04
This branch was successfully deployed
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
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.
Pins
@grida/fxto 0.6.1 (from 0.5.1), so thatgrida fxruns FX 0.6.1, and bumpsgridato 0.5.3 so the release workflow publishes it on merge. The host contract is unchanged (HOST_CONTRACT1), so the launcher needs no change.FX changes since 0.5.1:
@grida/fxon Node 24 or laterdoctorfound, trusts the platform's certificate store for HTTPS, previews video outputs on canvas cards, and downloads a run's outputs as one zip from the viewerChanges
packages/grida-cli/package.json:@grida/fx0.6.1, version 0.5.3crates/grida-cli/Cargo.toml,Cargo.lock: 0.5.3THIRD-PARTY-NOTICES.txt,native/licenses.json: regenerated (native-notices.mjs)pnpm-lock.yaml,pnpm-workspace.yaml:minimumReleaseAgeExcludenames the FX 0.6.1 packagesapps/docs/sources.lock.json: the FX guide atgridaco/fx@v0.6.1, viapnpm sources:sync fx-guideThe pin stays exact, because
sources:verifyrequires an exact version. Squash-merge.Lockfile note. As in #1093 and #1098, the FX entries were re-resolved once with
--config.minimum-release-age=0. The lockfile diff touches only the five@grida/fxentries, their integrity hashes matchnpm view … dist.integrity, andpnpm install --frozen-lockfilepasses under the workspace's real policy.Checked locally
pnpm install --frozen-lockfilepasses the supply-chain policies.pnpm sources:verifyreports every pin passes;v0.6.1resolves to7b7209f.native-notices.mjs --check: cleancargo metadata --locked: the lockfile is consistentgrida fx --version(through the launcher) printsgrida-fx 0.6.1; installed@grida/fx/clireportsHOST_CONTRACT1.