bug: Workflow failure in gemini-scheduled-issue-dedup due to invalid config key 'enabled'

[Han5991]

What happened?

The gemini-scheduled-issue-dedup.yml workflow failed during the google-github-actions/run-gemini-cli step.

When the action installed the latest version of the CLI (@google/gemini-cli@latest), it failed to validate the configuration file located at .gemini/settings.json. The error message indicates a schema mismatch:

Error in: mcpServers.issue_deduplication
    Unrecognized key(s) in object: 'enabled'

It appears that the enabled key is no longer supported in the mcpServers configuration for the latest CLI version, causing the workflow to exit with code 1.

What did you expect to happen?

The workflow should successfully install and configure the Gemini CLI without schema validation errors. The configuration generated or used by the action should be compatible with the @latest version of the CLI, allowing the issue deduplication process to proceed normally.

Client information

Client Information

Installing Gemini CLI from npm: @google/gemini-cli@latest
Verifying installation:
Invalid configuration in /home/runner/work/gemini-cli/gemini-cli/.gemini/settings.json:

Error in: mcpServers.issue_deduplication
Unrecognized key(s) in object: 'enabled'

Please fix the configuration and try again.
See: https://github.com/google-gemini/gemini-cli/blob/main/docs/get-started/configuration.md
Gemini CLI installed successfully (version command not available)
Run set -euo pipefail
Error: Invalid configuration in /home/runner/work/gemini-cli/gemini-cli/.gemini/settings.json:
Invalid configuration in /home/runner/work/gemini-cli/gemini-cli/.gemini/settings.json:

Error in: mcpServers.issue_deduplication
Unrecognized key(s) in object: 'enabled'

Please fix the configuration and try again.
See: https://github.com/google-gemini/gemini-cli/blob/main/docs/get-started/configuration.md
Error: Process completed with exit code 1.

Login information

No response

Anything else we need to know?

No response