Repository navigation
Use gemini-3-8-flash-boxes in the auto-label docstring examples - #557
Draft
iurisilvio wants to merge 1 commit into
Draft
iurisilvio wants to merge 1 commit into
iurisilvio wants to merge 1 commit into
Conversation
Roboflow's Auto Label catalog lists Gemini Flash as gemini-3-8-flash-boxes (roboflow/roboflow#17866) and keeps accepting gemini-boxes as an alias. The Project.autolabel_preview, Project.autolabel and Workspace.autolabel_models docstrings name the new id, and the CLI models-table test uses it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
iurisilvio
force-pushed
the
iuri/autolabel-gemini-flash-id
branch
from
October 16, 2026 15:00
a2cd8a9 to
1efefbd
Compare
iurisilvio
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Merge together with roboflow/roboflow#17866, after roboflow/roboflow#17823 is deployed.
Roboflow renames the Auto Label catalog id of Gemini Flash from
gemini-boxestogemini-3-8-flash-boxes(display name "Gemini 3.8 Flash (Boxes)"). The rename runs in two steps so no caller breaks:gemini-boxesas the id and acceptsgemini-3-8-flash-boxesas an alias everywhere an id is accepted.gemini-3-8-flash-boxesthe id and keepsgemini-boxesas the alias.Workspace.autolabel_models()then returns"id": "gemini-3-8-flash-boxes", "aliases": ["gemini-boxes"].The SDK and the CLI pass the model id through unchanged, so only the examples change:
Project.autolabel_previewandProject.autolabel: themodelexamples usegemini-3-8-flash-boxes.Workspace.autolabel_models: theidexample usesgemini-3-8-flash-boxes.tests/cli/test_autolabel_handler.py: theautolabel modelstable test uses the new id.Code that passes
model="gemini-boxes"keeps working, because the platform accepts the alias. The past CHANGELOG entry that namesgemini-boxesstays as written.Type of change
How has this change been tested?
python -m unitteston Python 3.12: 1233 tests OK (1 skipped).make check_code_quality(ruff format, ruff check, mypy) is clean.Any specific deployment considerations
None for the SDK: the docstrings reach users with the next release. Merge this with roboflow/roboflow#17866 so the examples match what
autolabel_models()returns.Companion PRs with the same change: roboflow/roboflow-mcp#235 (MCP tool descriptions) and roboflow/docs#385 (Auto Label page).
🤖 Generated with Claude Code