chore(release): bump version to 1.3.1

[slin1237]

Summary

Patch release v1.3.1 — bumps all version references from 1.3.0 to 1.3.1.

What changed

• model_gateway/Cargo.toml: 1.3.0 → 1.3.1
• bindings/python/Cargo.toml: 1.3.0 → 1.3.1
• bindings/python/pyproject.toml: 1.3.0 → 1.3.1
• bindings/golang/Cargo.toml: 1.3.0 → 1.3.1
• release-sglang-docker.yml: v1.3.0 → v1.3.1 (defaults, fallbacks, description examples)
• release-vllm-docker.yml: v1.3.0 → v1.3.1
• release-trtllm-docker.yml: v1.3.0 → v1.3.1
• check_release_versions.sh: remove build-engine from SMG_VERSION_SYNC — it uses default: 'main' (branch ref), not a version tag, so it should not be version-synced

How

Generated via VERSION_OVERRIDE=1.3.1 ./scripts/check_release_versions.sh (from #764).

Test plan

• make check-versions VERSION_OVERRIDE=1.3.1 reports all versions consistent
• cargo build --release succeeds
• CI passes

Summary by CodeRabbit

• Chores
  • Updated version from v1.3.0 to v1.3.1 across Docker workflows, Python and Go bindings, and related packages.
  • Synchronized version references in build and release configurations.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 259d5845-175c-4649-b622-70c29ed9c277

📥 Commits

Reviewing files that changed from the base of the PR and between feb6f06 and 0d8c49d.

📒 Files selected for processing (8)

• .github/workflows/release-sglang-docker.yml
• .github/workflows/release-trtllm-docker.yml
• .github/workflows/release-vllm-docker.yml
• bindings/golang/Cargo.toml
• bindings/python/Cargo.toml
• bindings/python/pyproject.toml
• model_gateway/Cargo.toml
• scripts/check_release_versions.sh

💤 Files with no reviewable changes (1)

• scripts/check_release_versions.sh

---

📝 Walkthrough

Walkthrough

This pull request bumps the SMG version from v1.3.0 to v1.3.1 across package manifests, Docker release workflows, and CI/CD configuration. The changes include updating default SMG commit references in three GitHub Actions workflows, incrementing version strings in Cargo.toml and pyproject.toml files, and removing one entry from the release version synchronization check script.

Changes

Cohort / File(s)	Summary
Docker Release Workflows .github/workflows/release-sglang-docker.yml, release-trtllm-docker.yml, release-vllm-docker.yml	Updated default and fallback SMG commit references from v1.3.0 to v1.3.1 in workflow inputs and job configurations. Updated image tag override descriptions to reflect v1.3.1.
Cargo.toml Package Manifests bindings/golang/Cargo.toml, bindings/python/Cargo.toml, model_gateway/Cargo.toml	Bumped package version from 1.3.0 to 1.3.1 in the [package] section of each manifest.
Python Bindings Configuration bindings/python/pyproject.toml	Updated project version from 1.3.0 to 1.3.1; no dependency or build system changes.
Version Synchronization Script scripts/check_release_versions.sh	Removed entry for _build-engine-image.yml workflow from the SMG\_VERSION\_SYNC checklist, reducing scope of version consistency validation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat(scripts): replace release notes generator with workspace version checker #484: Modifies scripts/check_release_versions.sh along with version-related artifacts; directly related to version synchronization changes.
• ci(docker): add engine-specific image build pipelines #651: Updates default/fallback SMG commit values and descriptions in the release workflow inputs that are being bumped in this PR.
• fix: render README images on PyPI/crates.io and bump version to 1.0.1 #420: Edits the same package manifest files (Cargo.toml and pyproject.toml) for version bumping across bindings.

Suggested labels

python-bindings, dependencies, ci, model-gateway, docker, workflow

Suggested reviewers

• CatherineSue
• whybeyoung
• key4ng
• gongwei-130
• XinyueZhang369

Poem

🐰 From one-three-oh to one-three-one,
A version bump beneath the sun,
Workflows dance and configs align,
Manifests updated, all looking fine! ✨

🚥 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 clearly and concisely describes the main change: a version bump from 1.3.0 to 1.3.1 across all relevant files in the repository.
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 docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/1.3.1

📝 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 performs a patch release, incrementing the project version from 1.3.0 to 1.3.1 across various configuration files and CI/CD workflows. It ensures consistency in versioning throughout the codebase and refines the version synchronization script by removing an irrelevant entry.

Highlights

• Version Bump: All version references across model_gateway/Cargo.toml, bindings/python/Cargo.toml, bindings/python/pyproject.toml, and bindings/golang/Cargo.toml have been updated from 1.3.0 to 1.3.1.
• CI/CD Workflow Updates: Version references in release-sglang-docker.yml, release-vllm-docker.yml, and release-trtllm-docker.yml have been updated from v1.3.0 to v1.3.1.
• Release Version Check Script Modification: The build-engine entry was removed from the SMG_VERSION_SYNC array in scripts/check_release_versions.sh as it uses a branch reference instead of a version tag.

Changelog

• bindings/golang/Cargo.toml
  • Updated project version from 1.3.0 to 1.3.1.
• bindings/python/Cargo.toml
  • Updated project version from 1.3.0 to 1.3.1.
• bindings/python/pyproject.toml
  • Updated project version from 1.3.0 to 1.3.1.
• model_gateway/Cargo.toml
  • Updated project version from 1.3.0 to 1.3.1.
• scripts/check_release_versions.sh
  • Removed 'build-engine' from the SMG_VERSION_SYNC array.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/release-sglang-docker.yml
  • .github/workflows/release-trtllm-docker.yml
  • .github/workflows/release-vllm-docker.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. ↩

[gemini-code-assist]

Code Review

This pull request prepares for the v1.3.1 patch release by bumping version numbers. The versions in bindings/golang/Cargo.toml, bindings/python/Cargo.toml, bindings/python/pyproject.toml, and model_gateway/Cargo.toml have been correctly updated from 1.3.0 to 1.3.1. The modification to scripts/check_release_versions.sh to remove an item from version synchronization is also correct based on the reasoning provided.

However, there is a critical discrepancy. The pull request description states that release-sglang-docker.yml, release-vllm-docker.yml, and release-trtllm-docker.yml were also updated. These changes are missing from the pull request. Please update the pull request to include the changes to these files to ensure a consistent and successful release.