prep release 1.23.2 - #1334
Merged
Merged
Conversation
Build the 1.23.2 changelog section from the pending towncrier fragment and remove it. The package version is derived from the git tag by hatch-vcs, so there is nothing to bump in pyproject.toml or uv.lock - tagging v1.23.2 after this merges is what sets the version. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying infrahub-sdk-python with
|
| Latest commit: |
d2ee8ef
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d6f55269.infrahub-sdk-python.pages.dev |
| Branch Preview URL: | https://fac-prep-1-23-2-hecha.infrahub-sdk-python.pages.dev |
fatih-acar
marked this pull request as ready for review
September 8, 2026 15:10
ogenstad
approved these changes
Sep 9, 2026
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.
Why
stablehas one user-facing change with a pending towncrier fragment since v1.23.1 (the transient-failure retry work, ff7a597). This assembles it into a 1.23.2 changelog section so the release can be tagged.What changed
CHANGELOG.mdgains a1.23.2section built byuv run towncrier build --version 1.23.2.changelog/+transient-retry.added.md) is removed.No runtime code changes.
No version bump here. The package version is derived from the git tag by hatch-vcs (
[tool.hatch.version] source = "vcs"), sopyproject.tomlanduv.lockcarry no hard-coded version. Taggingv1.23.2after this merges is what sets the released version.The other commits on
stablesince v1.23.1 are docs/CI dependency bumps and a regeneration ofinfrahub_sdk/protocols.py(refresh_tokenson the account, #1307). Neither category carries changelog fragments in this repo, so the section has a single entry.Release contents
Added
retry_on_failureenabled, the client now retries every transient failure, not only connection errors: dropped or timed-out connections, HTTP500/502/503/504responses, and GraphQL errors the server flags with one of those statuses, on every request path. Retries use exponential backoff with jitter (retry_delayup to the newretry_max_delay),retry_status_codestunes what counts as transient, andmax_retry_duration=0retries indefinitely.How to test
Impact & rollout
Configfields (retry_max_delay,retry_status_codes,max_retry_duration) and widens whatretry_on_failureretries; existing defaults keep the previous connection-error behaviour opt-in as before.v1.23.2onstableand publish the release to triggerrelease.yml(PyPI publish + submodule update + repository dispatch).Checklist
Summary by cubic
Builds the 1.23.2 changelog section from the pending transient-retry fragment so
stablecan be tagged. No runtime code changes and no version bump; the package version comes from the git tag via hatch-vcs.Rollout
v1.23.2onstableand publish the release to trigger PyPI publish and submodule updates.Written for commit d2ee8ef. Summary will update on new commits.