Repository navigation
Pin Grida FX 0.5.1 and release grida 0.5.2 - #1098
Merged
Merged
Conversation
Pins @grida/fx to 0.5.0 (from 0.4.0), so `grida fx` runs FX 0.5.0 (gridaco/fx#58), and bumps grida to 0.5.2 for the release workflow. Host contract unchanged. - packages/grida-cli/package.json: @grida/fx 0.5.0, version 0.5.2 - crates/grida-cli/Cargo.toml, Cargo.lock: 0.5.2; notices regenerated - apps/docs/sources.lock.json: FX guide at gridaco/fx@v0.5.0 - pnpm-lock.yaml, pnpm-workspace.yaml: minimumReleaseAgeExclude names the FX 0.5.0 packages
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (6)
✨ Finishing Touches
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 |
Moves @grida/fx to 0.5.1 (gridaco/fx#59), still host contract 1, and gives the grida package npm keywords. - packages/grida-cli/package.json: @grida/fx 0.5.1, keywords - apps/docs/sources.lock.json: FX guide at gridaco/fx@v0.5.1 - pnpm-lock.yaml, pnpm-workspace.yaml: minimumReleaseAgeExclude names the FX 0.5.1 packages
softmarshmallow
marked this pull request as ready for review
October 12, 2026 13:28
This branch had an error being 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/fxto0.5.1(from0.4.0), sogrida fxruns FX 0.5.1, and bumpsgridato0.5.2so the release workflow publishes it on merge. The host contract is unchanged (HOST_CONTRACT1), so the launcher stays as it is.FX changes since 0.4.0:
init(a starter, example templates and the FX skills); AI providers in the READMEChanges:
packages/grida-cli/package.json:@grida/fx0.5.1, version0.5.2, and npmkeywords(the package had none)crates/grida-cli/Cargo.toml,Cargo.lock:0.5.2THIRD-PARTY-NOTICES.txt,native/licenses.json: regenerated (native-notices.mjs)apps/docs/sources.lock.json: FX guide moved togridaco/fx@v0.5.1(pnpm sources:sync fx-guide)pnpm-lock.yaml,pnpm-workspace.yaml:minimumReleaseAgeExcludenames the FX 0.5.1 packages instead of 0.4.0Draft: the FX pin may move to a later 0.5.x before this merges (hence the branch name). Squash-merge.
Lockfile note. As in #1093, 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
node --test scripts/cli-release/*.test.mjs: 26/26 (clean checkout, freshgridabuild)native-notices.mjs --check: cleancargo metadata --locked: the lockfile is consistentsources.js verify: every pin passes;v0.5.1resolves to806fbcb@grida/fx/clireports version 0.5.1,HOST_CONTRACT1The
Vercel – blogcheck builds only because the lockfile changed (apps/blog/skip-build.sh). Its failure was not investigated.