bug(#159): Fix malformed image reference, docker registry for buildkitd image in release builds

[kmannislands]

Fixes #159

The released binaries produced by the new automation do not correctly set the buildkitd image to be used by default.

[gemini-code-assist]

Summary of Changes

Hello @kmannislands, 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 resolves a critical bug affecting released binaries, where the buildkitd image reference was incorrectly configured. By making the RELEASE_TAG a mandatory argument in the release build process, the change guarantees that the correct image is consistently applied, ensuring the stability and proper functioning of the released artifacts.

Highlights

• Bug Fix: Addresses an issue where released binaries had a malformed image reference and incorrect Docker registry for the buildkitd image.
• Build Configuration: Introduces RELEASE_TAG as a required argument in the release/Earthfile to ensure the correct buildkitd image is used during release builds.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci-staging-deploy.yml

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. ↩

[github-actions]

➖ Are we earthbuild yet?

No change in "earthly" occurrences

📈 Overall Progress

Branch	Total Count
main	5735
This PR	5735
Difference	+0

---

Keep up the great work migrating from Earthly to Earthbuild! 🚀

💡 Tips for finding more occurrences

Run locally to see detailed breakdown:

./.github/scripts/count-earthly.sh

Note that the goal is not to reach 0.
There is anticipated to be at least some occurences of earthly in the source code due to backwards compatibility with config files and language constructs.

[gemini-code-assist]

Code Review

This pull request correctly fixes a bug in the signed-release target within release/Earthfile. By introducing the --required RELEASE_TAG argument, it ensures that release builds properly receive the release tag. Previously, the missing argument caused a malformed image reference for the buildkitd image because the tag was empty. The change is precise, effectively resolves the issue, and makes the release process more robust. The fix looks good.

[gilescope]

EarthBuild/hello-world#1 - looking forward to this being merged.

[gilescope]

Let's merge this, create another RC and see where we are.