Remove and reserve deprecated fields

[yoctozepto]

Fixes #110

[github-actions]

The latest Buf updates on your PR. Results from workflow buf-ci / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	⏩ skipped	Aug 12, 2025, 9:29 AM

[gemini-code-assist]

Summary of Changes

Hello @yoctozepto, 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 systematically removes deprecated fields from various Protocol Buffer message definitions and their generated Go and TypeScript code. The corresponding field numbers and names have been reserved in the .proto files to prevent accidental reuse and ensure forward compatibility, addressing issue #110.

Highlights

• APBinding Cleanup: Deprecated trust_zone, policy, and federates_with fields, along with their associated getter methods, have been removed from the APBinding message and its generated Go and TypeScript code.
• Cluster Cleanup: The deprecated trust_zone field and its getter method have been removed from the Cluster message and its generated Go and TypeScript code.
• Federation Cleanup: The deprecated from and to fields and their getter methods have been removed from the Federation message and its generated Go and TypeScript code.
• TrustZone Cleanup: Deprecated federations and attestation_policies fields, their getter methods, and related imports have been removed from the TrustZone message and its generated Go and TypeScript code.
• Protocol Buffer Field Reservation: The field numbers and names of all removed deprecated fields have been explicitly reserved in their respective .proto files to prevent future conflicts and maintain wire compatibility.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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

[yoctozepto]

draft to discuss it a bit more (see the issue)

also need to fix buf step to allow breaking changes (at least the "good ones" with reserved fields)

[gemini-code-assist]

Code Review

This pull request correctly removes deprecated fields from several protobuf definitions and reserves their tags and names. This is a good practice for API evolution as it prevents accidental reuse and maintains a degree of backward compatibility. The generated Go and TypeScript files are all updated consistently with the schema changes. The changes are clean, correct, and improve the maintainability of the API definitions.

[markgoddard]

also need to fix buf step to allow breaking changes (at least the "good ones" with reserved fields)

Added the buf skip breaking label

[markgoddard]

LGTM, let's wait a couple of weeks before merging.

[yoctozepto]

also need to fix buf step to allow breaking changes (at least the "good ones" with reserved fields)

Added the buf skip breaking label

Thanks!

LGTM, let's wait a couple of weeks before merging.

As we use released versions and this is internal, I don't think there is much point in waiting now.

In the meantime, I will make sure there are no uses of these fields in the depending projects.

[yoctozepto]

In the meantime, I will make sure there are no uses of these fields in the depending projects.

'Tis done!