ci: add SLSA build provenance to docker images

[duwenxin99]

Ref: Generate Cloud Build provenance

• Remove the original binary upload steps.
• Let artifact registry config automatically upload binaries & dockers and generate provenance.
• Add a new final step to create versioned directories containing binaries to be automatically uploaded.

[gemini-code-assist]

Summary of Changes

Hello @duwenxin99, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the integrity and verifiability of the project's release artifacts. By adopting SLSA build provenance, it ensures that all generated binaries and Docker images come with cryptographically signed metadata detailing their build process. This change streamlines artifact storage and improves supply chain security without altering the core build logic.

Highlights

• SLSA Build Provenance: Integrated SLSA build provenance generation for release binaries and Docker images by configuring Cloud Build's artifact management to include requestedVerifyOption: VERIFIED.
• Artifact Handling Refactor: Replaced individual gcloud storage cp steps with a unified prepare-artifacts step that organizes all built binaries into a structured directory for Cloud Build's native artifact upload feature.
• Go Build Optimization: Added the -trimpath flag to all go build commands, which removes all file system paths from the compiled executable, improving build reproducibility and reducing binary size.

Changelog

• .ci/versioned.release.cloudbuild.yaml
  • Removed redundant store-* steps for various platform binaries (Linux, macOS, Windows, AMD64, ARM64, geminicli variants) as artifact storage is now handled by Cloud Build's built-in feature.
  • Added -trimpath flag to all go build commands to remove build path information from binaries.
  • Introduced a new prepare-artifacts step to consolidate all built binaries into a standardized artifacts directory structure.
  • Configured the artifacts section in the Cloud Build YAML to automatically upload the artifacts directory to Google Cloud Storage.
  • Enabled SLSA provenance generation by adding requestedVerifyOption: VERIFIED to the Cloud Build options.
  • Corrected the output filename for Windows binaries to consistently include the .exe extension in go build commands.

Activity

• No specific activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the Cloud Build release process to generate SLSA build provenance for release binaries and Docker images, replacing manual artifact storage with the artifacts block and updating go build commands for reproducibility. However, the implementation introduces a medium-severity path traversal vulnerability in a build script, where an attacker could manipulate a version file to compromise build integrity. Additionally, a critical issue in the new prepare-artifacts step could cause build failure, and there's an opportunity to improve script maintainability.

[github-actions]

🧨 Preview deployments removed.

Cloudflare Pages environments for pr-2556 have been deleted.