Fix release_tag mismatch in release workflow

[Copilot]

The docker-image job fails with "release not found" when gh-extension-precompile creates a release with an unpredictable tag (from git describe --tags --abbrev=0), while downstream jobs expect needs.release.outputs.release_tag.

Changes

• Pass explicit release_tag parameter to gh-extension-precompile action to ensure consistent tag usage across all jobs

Before:

- name: Release with gh-extension-precompile
  uses: cli/gh-extension-precompile@9e2237c30f869ad3bcaed6a4be2cd43564dd421b
  with:
    go_version_file: go.mod
    build_script_override: scripts/build-release.sh

After:

- name: Release with gh-extension-precompile
  uses: cli/gh-extension-precompile@9e2237c30f869ad3bcaed6a4be2cd43564dd421b
  with:
    go_version_file: go.mod
    build_script_override: scripts/build-release.sh
    release_tag: ${{ needs.config.outputs.release_tag }}

This ensures gh-extension-precompile creates the release at the exact tag computed by the config job, which all downstream jobs (docker-image, generate-sbom) rely on.

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/21089132494/job/60658002027

Make sure release_tag is correct. Review the use of release_tag

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.