gridaco/grida / .agents/skills/releasing
releasing
VerifiedPlan, prepare, or verify releases of the Grida CLI and Grida Desktop, including upstream FX dependencies and version alignment.
Releasing Grida
Keep the npm grida CLI and Grida Desktop on the same version by default. An urgent release for one product may advance its patch version independently. Keep the same major and minor versions. When the two next ship together, use a common version higher than both published versions. Check the published npm version and Desktop GitHub tag when choosing a version. FX has its own version. Use externals for shared dependency pins.
Release order
- Start from published FX. If a new FX version is needed, release it before changing Grida's pin. The FX repository owns its version checks, dry run, and approved tag release. Its workflow publishes the platform engines before the npm SDK, then publishes the PyPI wheels. Verify that the exact npm SDK and platform packages are available before adopting them in Grida. The FX tag also supplies the template source archive. Follow the FX release runbook.
- Prepare one reviewed Grida revision. When adopting FX, update both exact pins and lockfiles together and sync the
fx-guidesource to the CLI's pinned FX tag. For a joint release, update the Desktop manifest and CLI npm manifest to the common version. Keep the CLI crate, Cargo lockfile, and generated notices aligned. Verify the installed CLI'sgrida fx --versionand the staged Desktop engine on supported targets. Check Desktop renderer compatibility when the hosted UI changes alongside the native app. See the docs source rules. - Ship the CLI and Desktop through their own workflows. A CLI version change on
mainstarts the npm release workflow, which publishes the exact tested candidate after thenpm-publishapproval. Desktop publication starts with a manual dispatch frommain. The approved builds produce installers and assemble a GitHub draft. Review the draft before publishing and verify the downloads and update feed afterward. Both workflows can use the same reviewed revision. See the CLI release runbook and the Desktop release runbook.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |