Nightly Release Failed for v0.48.0-nightly.20260612.g4e10a34be on 2026-06-12

[github-actions]

The nightly-release workflow failed. See the full run for details: https://github.com/google-gemini/gemini-cli/actions/runs/27387480398

[gemini-cli]

Effort Analysis:
The release-nightly workflow failure (Issue #27865) involves a highly complex orchestration pipeline. The failure occurred after the nightly version tag (v0.48.0-nightly.20260612.g4e10a34be) was successfully generated by scripts/get-release-version.js, narrowing the root cause to either the .github/actions/publish-release composite action or the .github/actions/create-pull-request action. The publish-release action is architecturally complex, performing stateful operations across multiple packages (packages/cli, packages/core, and packages/a2a-server) including: 1) synchronized version bumping via npm run release:version, 2) multi-arch macOS binary management in dist/, 3) concurrent npm publishing for three distinct packages with temporary staging-tmp tags, and 4) GitHub Release creation using gh release create with automated notes generation based on the previous-tag output. The fact that the version in package.json remains at 20260609 suggests a persistent blockage in the PR-to-main merge flow or the release branch cleanup logic (Clean up release branch step in publish-release/action.yml). This represents a 'platform-specific complexity' that is 'difficult to reproduce' and involves 'OS-level shell behavior' and 'Core Architecture' within the release automation, explicitly mapping to the effort/large guideline.

[rmedranollamas]

I've identified that the nightly release was stalling because scheduled runs were defaulting to the 'prod' environment, which requires manual approval. I've updated the workflow to use the 'internal' environment (unprotected) for scheduled runs. This should allow the automated nightly releases to proceed as expected.

Fixed in 19af3d4.