Skip to content

v1.3.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Apr 03:51
· 27 commits to main since this release
v1.3.4
8f6a701

What's Changed in v1.3.4

fix: make hook commands cross-platform (Windows PowerShell) — fixes #42 (#43) by @Jamkris

Issue #42 reports "Alerta constante" parser errors on Windows, caused by POSIX-only shell syntax in hooks/hooks.json:

node "$HOME/.../scripts/hooks/pre-compact.js" 2>/dev/null \
  || node "$HOME/.gemini/scripts/hooks/pre-compact.js" 2>/dev/null \
  || true

Windows PowerShell 5.x (the default shell on Windows 10/11) rejects || as an "invalid statement separator" and has no /dev/null or true.

Replace the six script-launching hook commands with a single Node launcher:

node "$HOME/.../scripts/hooks/run.js" <hook-name>

The launcher (scripts/hooks/run.js) resolves the target hook file via __dirname, silently skips missing hooks (preserving the prior || true semantics), and never fails the parent Gemini CLI action. Inline node -e "..." hooks are untouched — the JS string is consumed by Node, not the shell, so they are already cross-platform.

Tests:

  • Add a regression guard asserting no hook command contains ||, 2>/dev/null, or || true (inline node -e commands exempted).
  • Add a sanity check on run.js for __dirname + argv[2] usage.

Summary by CodeRabbit

  • Chores
    • Unified hook execution mechanism for improved reliability and maintainability.
    • Added cross-platform compatibility validation to prevent Windows PowerShell issues.
    • Expanded hook testing to verify correct execution paths and error handling behavior.

docs: note Antigravity-only bare workflow names vs Gemini CLI egc- pr… (#41) by @Jamkris

…efix

Only /egc-plan gets the egc- prefix under Antigravity (it would otherwise shadow Antigravity's built-in /plan). Every other workflow installed via scripts/install.sh --antigravity keeps its bare name (/tdd, /build-fix, /code-review, …). Gemini CLI still requires the prefix on every command to avoid its built-in command collisions.

Add this note to the Slash Commands section of the EN/KO/ZH READMEs so users don't assume commands were renamed everywhere.

Summary by CodeRabbit

  • Documentation
    • Added clarification on command naming conventions for Antigravity workflows, explaining that workflows use bare command names (e.g., /tdd, /code-review, /build-fix) with the exception of /egc-plan to avoid conflicts with built-in commands.
    • Updated documentation in English, Korean, and Chinese.

chore: release v1.3.3 (#40) by @Jamkris

Bump version to 1.3.3

Contributors

Jamkris
Assets 2
Loading