Cut release v0.4.0-rc.3

[Jeffwan]

Pull Request Description

cut another release to test recent change

Related Issues

Resolves: #[Insert issue number(s)]

Important: Before submitting, please complete the description above and review the checklist below.

---

Contribution Guidelines (Expand for Details)

We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

• [Bug]: Corrections to existing functionality
• [CI]: Changes to build process or CI pipeline
• [Docs]: Updates or additions to documentation
• [API]: Modifications to aibrix's API or interface
• [CLI]: Changes or additions to the Command Line Interface
• [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

• PR title includes appropriate prefix(es)
• Changes are clearly explained in the PR description
• New and existing tests pass successfully
• Code adheres to project style and best practices
• Documentation updated to reflect changes (if applicable)
• Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

[gemini-code-assist]

Summary of Changes

Hello @Jeffwan, 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!

I've prepared this pull request to cut a new release candidate, v0.4.0-rc.3, for the aibrix project. This involves updating the version tags for various core aibrix components across several Kustomize configurations and the VKE Helm chart. The primary purpose is to test recent changes under this new release candidate version.

Highlights

• Kustomize Release Overlay Updates: Updated the version tags for aibrix/gateway-plugins, aibrix/metadata-service, aibrix/controller-manager, and aibrix/runtime to v0.4.0-rc.3 in the main release Kustomize overlay.
• Kustomize VKE Overlay Updates: Updated the version tags for aibrix/gateway-plugins, aibrix/metadata-service, aibrix/controller-manager, and aibrix/runtime to v0.4.0-rc.3 within the VKE-specific Kustomize overlay.
• Standalone Controller Kustomize Updates: Updated the aibrix/controller-manager image tag to v0.4.0-rc.3 across multiple standalone Kustomize configurations, including autoscaler, distributed-inference, kv-cache, model-adapter, and stormservice controllers.
• Helm Chart Updates: Updated the image tags for controllerManager, gatewayPlugin, gpuOptimizer, and metadata components to v0.4.0-rc.3 within the VKE Helm chart configuration.

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 or fill out our survey to provide feedback.

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 updates image tags to a new release candidate, v0.4.0-rc.3, across various configuration files. My main feedback concerns the change in the versioning format for release candidates (from vX.Y.Z.rc.N to vX.Y.Z-rc.N). While the new format is more SemVer-compliant, this inconsistency within a release cycle can be confusing. I've suggested maintaining the previous format for this release to ensure consistency. Also, the pull request title should be prefixed (e.g., [CI], [Misc]) as per the contribution guidelines.

[gemini-code-assist]

The versioning format for this release candidate (v0.4.0-rc.3) is inconsistent with the previous one (v0.4.0.rc.2). The separator before rc has changed from a dot (.) to a hyphen (-).

While using a hyphen is more compliant with Semantic Versioning, changing formats for release candidates within the same minor version can be confusing and might break automation scripts that expect a consistent tag format.

For consistency with the previous RC, please consider using the . separator. This comment applies to all similar version updates in this pull request.

  newTag: v0.4.0.rc.3