Upgrade Gemini CLI and retest ignore paths on symlink-linked trees
Gemini CLI nightly v0.56.0 fixes consistent symlink evaluation in ignore path handling. Upgrade, then re-run ignore-sensitive workflows on repos that use symlinks so excluded paths match the new resolution behavior.Why this loop
Gemini CLI v0.56.0-nightly.20260821.g30573d2e4 (prerelease, tagged breaking) changes core ignore-path handling so symlink evaluation is consistent. Paths reached through links can now be included or excluded differently than on earlier nightlies; any Gemini CLI job that applies ignore rules (context file selection, skipped reads, sandbox path filters) on a tree with symlinks can flip membership. The same tag also refactors shellExecutionService by removing eslint-disable comments and type assertions—expect merge conflicts if you patch or vendor that file, not a user-facing flag change. Pin this exact nightly only where you can re-check ignore results against symlink-linked trees.
Proposed actions
- Upgrade Gemini CLI to exactly v0.56.0-nightly.20260821.g30573d2e4 from https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260821.g30573d2e4 (e.g. npm install -g @google/gemini-cli@0.56.0-nightly.20260821.g30573d2e4). Run gemini --version and fail the task if the output does not contain 0.56.0-nightly.20260821.g30573d2e4.
- In every repo this agent uses with Gemini CLI, list symlinks with: git ls-files -s | awk '$1=="120000"{print $4}'; find . -type l -not -path './.git/*' . For each link, record target vs. realpath.
- Re-run the same ignore-sensitive Gemini CLI jobs you already use (context collection, ignored-path skips, sandbox file access) on those symlink-linked trees. Write a before/after table of paths whose include/exclude status changed after the consistent symlink evaluation fix.
- If we vendor or patch google-gemini/gemini-cli shellExecutionService, rebase onto tag v0.56.0-nightly.20260821.g30573d2e4 and drop local eslint-disable / type-assertion workarounds this refactor removed; keep only functional diffs.
- Pin CI and devcontainer Gemini CLI to v0.56.0-nightly.20260821.g30573d2e4. Do not float to a newer nightly until the symlink ignore-path table has no unexpected flips.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costGoogle Antigravity / agent task
DevAgentRadar → Google Antigravity
Goal: turn this release signal into a safe pilot plan for my stack.
Context
Assistant: Gemini CLI Proposal: Upgrade Gemini CLI and retest ignore paths on symlink-linked trees Summary: Gemini CLI nightly v0.56.0 fixes consistent symlink evaluation in ignore path handling. Upgrade, then re-run ignore-sensitive workflows on repos that use symlinks so excluded paths match the new resolution behavior. Primary source: https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260821.g30573d2e4
Why it matters
Gemini CLI v0.56.0-nightly.20260821.g30573d2e4 (prerelease, tagged breaking) changes core ignore-path handling so symlink evaluation is consistent. Paths reached through links can now be included or excluded differently than on earlier nightlies; any Gemini CLI job that applies ignore rules (context file selection, skipped reads, sandbox path filters) on a tree with symlinks can flip membership. The same tag also refactors shellExecutionService by removing eslint-disable comments and type assertions—expect merge conflicts if you patch or vendor that file, not a user-facing flag change. Pin this exact nightly only where you can re-check ignore results against symlink-linked trees.
Suggested actions
- Upgrade Gemini CLI to exactly v0.56.0-nightly.20260821.g30573d2e4 from https://github.com/google-gemini/gemini-cli/releases/tag/v0.56.0-nightly.20260821.g30573d2e4 (e.g. npm install -g @google/gemini-cli@0.56.0-nightly.20260821.g30573d2e4). Run gemini --version and fail the task if the output does not contain 0.56.0-nightly.20260821.g30573d2e4.
- In every repo this agent uses with Gemini CLI, list symlinks with: git ls-files -s | awk '$1=="120000"{print $4}'; find . -type l -not -path './.git/*' . For each link, record target vs. realpath.
- Re-run the same ignore-sensitive Gemini CLI jobs you already use (context collection, ignored-path skips, sandbox file access) on those symlink-linked trees. Write a before/after table of paths whose include/exclude status changed after the consistent symlink evaluation fix.
- If we vendor or patch google-gemini/gemini-cli shellExecutionService, rebase onto tag v0.56.0-nightly.20260821.g30573d2e4 and drop local eslint-disable / type-assertion workarounds this refactor removed; keep only functional diffs.
- Pin CI and devcontainer Gemini CLI to v0.56.0-nightly.20260821.g30573d2e4. Do not float to a newer nightly until the symlink ignore-path table has no unexpected flips.
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/gemini-cli-v0-56-0-nightly-20260821-g30573d2e4-upgrade-gemini-cli-and-re and mark Applied, Skipped, or Failed. Proposal id: 638303d4-6822-438a-9a06-36a01bede1bb
Please:
- Map the change to concrete pilot steps
- Flag security / permission implications
- Keep the pilot reversible
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.