chore: bump versions for v1.3.0 release

[slin1237]

Summary

Bump all crate and artifact versions for the v1.3.0 release.

What changed

• openai-protocol: v1.3.0 → v1.4.0 (minor, protocol changes)
• smg-mesh: v1.1.2 → v1.2.0 (minor, mesh feature changes)
• smg-grpc-client: v1.3.0 → v1.4.0 (minor, gRPC client changes)
• openapi-gen: v0.1.0 → v0.1.1 (patch)
• smg: v1.2.0 → v1.3.0 (minor, Messages API support)
• smg-python: v1.2.0 → v1.3.0 (sync with smg)
• smg-golang: v1.2.0 → v1.3.0 (sync with smg)
• Docker workflows: v1.2.0 → v1.3.0 (sync with smg)
• Workspace Cargo.toml: sync dependency versions

Why

New features merged since v1.2.0 (Messages API gRPC support, mesh HA sync, WebRTC plumbing, MCP extraction) require a minor version bump.

Test plan

• make check-versions passes with no issues after applying fixes

Summary by CodeRabbit

• Chores
  • Updated package versions across bindings and internal crates (multiple 1.2.x → 1.3.x and related bumps).
  • Updated CI/workflow defaults and build behavior: PR builds now default to main while non-PR runs use the configured release commit/tag (updated default release tag to v1.3.0).
  • Bumped internal dependency versions including gRPC client, mesh, and protocol libraries.

[coderabbitai]

📝 Walkthrough

Walkthrough

Coordinated version bumps across workspace crates and bindings plus updates to Docker release workflows' SMG commit defaults; several GitHub Actions now resolve smg_commit to main for pull_request events while non-PR runs use specified or bumped defaults.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/_build-engine-image.yml, .github/workflows/release-sglang-docker.yml, .github/workflows/release-trtllm-docker.yml, .github/workflows/release-vllm-docker.yml	Changed default smg_commit values and added conditional resolution: PR events default to main, non-PR runs use provided input or bumped v1.3.0 defaults; one workflow sets _build-engine-image default to main.
Workspace Configuration Cargo.toml	Bumped workspace/internal dependency versions: openai-protocol 1.3.0→1.4.0, smg-mesh 1.1.2→1.2.0, smg-grpc-client 1.3.0→1.4.0.
Python Bindings bindings/python/Cargo.toml, bindings/python/pyproject.toml	Package/project version bumped 1.2.0→1.3.0 in both Rust and Python manifests.
Golang Bindings bindings/golang/Cargo.toml	Package version bumped 1.2.0→1.3.0.
Internal Crates crates/protocols/Cargo.toml, crates/grpc_client/Cargo.toml, crates/mesh/Cargo.toml	Version increments: protocols 1.3.0→1.4.0, smg-grpc-client 1.3.0→1.4.0, mesh 1.1.2→1.2.0.
Application Packages model_gateway/Cargo.toml, clients/openapi-gen/Cargo.toml	Version bumps: model_gateway 1.2.0→1.3.0, openapi-gen 0.1.0→0.1.1.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix(docker): fix image build failures in engine Dockerfile and release workflows #656 — modifies the same release Docker workflows and smg_commit handling.
• feat(release): bump v1.2.0 with version sync and engine docker auto-triggers #695 — coordinated version/workflow changes touching engine release workflows and manifests.
• chore(mesh): bump smg-mesh version to 1.1.0 #419 — related workspace crate version bump for smg-mesh.

Suggested labels

python-bindings, dependencies, grpc, protocols, model-gateway, ci, docker

Suggested reviewers

• tonyluj
• CatherineSue
• key4ng
• whybeyoung
• XinyueZhang369

Poem

🐇 Hops of code, a gentle cheer,

Versions climb and defaults steer,
Workflows hum, crates wear new threads,
I nibble carrots, update the reds,
Tiny rabbit, big release had near.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately summarizes the main change: bumping versions for the v1.3.0 release, which is the primary objective across all modified files (Cargo.toml files, bindings, and Docker workflows).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/v1.3.0

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, 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 updates the version numbers across various crates and language bindings in preparation for the v1.3.0 release. The version increments reflect the integration of new features such as Messages API gRPC support, mesh high-availability synchronization, WebRTC plumbing, and MCP extraction, ensuring all components are aligned with the latest developments.

Highlights

• Version Bump: openai-protocol: The openai-protocol crate version was bumped from 1.3.0 to 1.4.0, reflecting minor protocol changes.
• Version Bump: smg-mesh: The smg-mesh crate version was bumped from 1.1.2 to 1.2.0, indicating minor mesh feature changes.
• Version Bump: smg-grpc-client: The smg-grpc-client crate version was bumped from 1.3.0 to 1.4.0, due to gRPC client changes.
• Version Bump: openapi-gen: The openapi-gen crate received a patch version bump from 0.1.0 to 0.1.1.
• Version Bump: smg (model gateway): The main smg package version was bumped from 1.2.0 to 1.3.0, incorporating Messages API support.
• Version Bump: smg-python: The smg-python binding version was synchronized with smg, bumping from 1.2.0 to 1.3.0.
• Version Bump: smg-golang: The smg-golang binding version was synchronized with smg, bumping from 1.2.0 to 1.3.0.
• Workspace Dependency Synchronization: Dependency versions for openai-protocol, smg-mesh, and smg-grpc-client were synchronized in the root Cargo.toml.

Changelog

• Cargo.toml
  • Updated openai-protocol from v1.3.0 to v1.4.0 (minor, protocol changes)
  • Updated smg-mesh from v1.1.2 to v1.2.0 (minor, mesh feature changes)
  • Updated smg-grpc-client from v1.3.0 to v1.4.0 (minor, gRPC client changes)
• bindings/golang/Cargo.toml
  • Updated smg-golang from v1.2.0 to v1.3.0 (sync with smg)
• bindings/python/Cargo.toml
  • Updated smg-python from v1.2.0 to v1.3.0 (sync with smg)
• bindings/python/pyproject.toml
  • Updated smg from v1.2.0 to v1.3.0 (sync with smg)
• clients/openapi-gen/Cargo.toml
  • Updated openapi-gen from v0.1.0 to v0.1.1 (patch)
• crates/grpc_client/Cargo.toml
  • Updated smg-grpc-client from v1.3.0 to v1.4.0 (minor, gRPC client changes)
• crates/mesh/Cargo.toml
  • Updated smg-mesh from v1.1.2 to v1.2.0 (minor, mesh feature changes)
• crates/protocols/Cargo.toml
  • Updated openai-protocol from v1.3.0 to v1.4.0 (minor, protocol changes)
• model_gateway/Cargo.toml
  • Updated smg from v1.2.0 to v1.3.0 (minor, Messages API support)

Ignored Files

• Ignored by pattern: .github/workflows/** (4)
  • .github/workflows/_build-engine-image.yml
  • .github/workflows/release-sglang-docker.yml
  • .github/workflows/release-trtllm-docker.yml
  • .github/workflows/release-vllm-docker.yml

Activity

• No specific activity (comments, reviews, progress) 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 correctly bumps versions for multiple crates for the v1.3.0 release, and the changes in the Cargo.toml and pyproject.toml files are consistent. However, there's a critical omission: the PR description mentions that 'Docker workflows' were updated from v1.2.0 to v1.3.0, but the corresponding workflow files (e.g., .github/workflows/release-sglang-docker.yml, .github/workflows/release-vllm-docker.yml) are not part of this pull request. For a release PR, it's crucial that all version references are updated consistently. Please add the missing workflow file changes to ensure the release process uses the correct versions.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release-sglang-docker.yml:
- Line 7: The run-name's smg variable currently defaults to a hard-coded
'v1.3.0' (smg=${{ inputs.smg_commit || 'v1.3.0' }}) which can mismatch the
expression used elsewhere for PR runs; update the smg assignment to mirror the
same expression used for pull_request runs (the same conditional used later in
the file) so that smg and run-name consistently reflect the effective commit/ref
(use the existing conditional logic instead of the hard-coded 'v1.3.0',
referencing smg and inputs.smg_commit).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 685a4433-81f0-471a-b2cf-5f6409d7cbdb

📥 Commits

Reviewing files that changed from the base of the PR and between cac29a4 and 2114206.

📒 Files selected for processing (4)

• .github/workflows/_build-engine-image.yml
• .github/workflows/release-sglang-docker.yml
• .github/workflows/release-trtllm-docker.yml
• .github/workflows/release-vllm-docker.yml