Repository navigation
Conversation
git tag --sort=-v:refname puts v2.0.0-rc.8 above v2.0.0, so every deploy built the published reference from the release candidate. Select stable vX.Y.Z tags only, in deploy.yml and in the update-api-docs.yml fallback. update-api-docs.yml now skips pre-release dispatches, and deploy.yml installs griffe from scripts/requirements.txt like update-api-docs.yml.
This was referenced Oct 16, 2026
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
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.
Closes #12.
The deploy built the published Python API reference from
v2.0.0-rc.8, not from thev2.0.0release. The cause isgit tag --sort=-v:refname | head -n1: git's version sort puts-rctags above the release.Changes
deploy.yml: select the newest stable tag (^v[0-9]+\.[0-9]+\.[0-9]+$). Install griffe fromscripts/requirements.txt, asupdate-api-docs.ymldoes.update-api-docs.yml: use the same stable-tag selection for the fallback. Skip pre-release dispatches (arefthat contains-), because python-sdk dispatchessdk-releasefor-rctags too.Test
I ran the selection command under
set -euo pipefailon a clone of python-sdk:v2.0.0-rc.8v2.0.0v2.1.0-rc.1v2.1.0-rc.1v2.0.0v2.1.0-rc.1andv2.0.1v2.1.0-rc.1v2.0.1Both workflow files parse as YAML.
Merge order
Merge this first, then #16 (guides, examples and install pages), then #17 (the API reference). The first deploy after #17 then builds the reference from
v2.0.0.