Repository navigation
chore: release 1.11.10 - #11304
Merged
Merged
chore: release 1.11.10#11304
Conversation
This was referenced Oct 30, 2026
Merging this PR will not alter performance1 warning
Comparing Footnotes |
fatih-acar
force-pushed
the
fac-prep-release-1.11.10
branch
from
October 30, 2026 13:13
1c31469 to
d863c03
Compare
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.
Release 1.11.10
Files changed for release 1.11.10
CHANGELOG.md: towncrier added the 1.11.10 section from 22 changelog fragments and removed those fragments. The Redis 6.0 entry then received a Breaking: prefix. After the rebase ontostable, the fragment of fix(workflows): remove the concurrency limit from clean-up-deadlocks #11302 was added to the Changed section, where towncrier places it, and removed.docs/docs/release-notes/infrahub/release-1_11_10.mdx: new release notes page with these frontmatter values:release_type: security, because the changelog has a Security section.breaking: true, because of the Redis 6.0 requirement.docs/docs/deploy-manage/install-configure/production-deployment/high-availability.mdx,development/k8s/infrahub-values.yamlanddevelopment/deploy.tf: the HA guide and its examples now name 1.11.10 instead of 1.11.9. These files were wrong before because 1.11.9 does not have theINFRAHUB_CACHE_URLsetting, thequeue_typebroker setting, or Docket 0.27.0, so 1.11.10 is the first release that runs the examples.docker-compose.yml: the "Update Docker Compose & helm chart" workflow pinned the Infrahub images to 1.11.10 (run 41046002931, committed byopsmill-bot). The same run setappVersionandprefectTagto 1.11.10 in opsmill/infrahub-helm, and raised theinfrahubchart to 4.35.2 and theinfrahub-enterprisechart to 4.23.2.Redis 6.0 is now required
Infrahub now opens every Redis connection with the
HELLOcommand, which Redis 5.0 and earlier reject (#9451, issue #9449). Teams that run Redis 5.0 or earlier must upgrade Redis before they upgrade Infrahub. As in 1.11.3, the Changed entry has a Breaking: prefix and the release notes page setsbreaking: true.Pull requests merged into
stablesince 1.11.9infrahub-testcontainers.stablewithout a pull request againststable; its pull request againstdevelop, fix(frontend): keep table scrollbars above the table's pinned cells #11195, was closed.uvin the image build stage and update it to 0.13.6.clean-up-deadlockstask.Open pull requests in opsmill/infrahub-helm
None of the open pull requests in opsmill/infrahub-helm ship in 1.11.10, so none were merged:
Checks run locally
uv run invoke release.validate-docker-compose --version 1.11.10passes.node scripts/backfill-release-frontmatter.mjs --checkpasses.uv run invoke docs.lintreports 0 errors.uv run invoke docs.validateleaves no changes.pyproject.tomlandpython_testcontainers/pyproject.tomlare unchanged.Graph migration 080 on
stableandrelease-1.12This release ships graph migration 080 as
m080_delete_generator_capture_diffs. Onrelease-1.12anddevelop, 080 ism080_number_pool_ranges(minimum version 79), followed by 081 and 082. A database upgraded to 1.11.10 is at graph version 80, so an upgrade to 1.12 skipsm080_number_pool_rangesunlessrelease-1.12anddeveloprenumber their 080–082 to 081–083 whenstableis merged in. The comment on #11275 describes this.Steps after merge
Tag the commit on
stablethat contains all the commits of this pull request withinfrahub-v1.11.10, then create the GitHub release from that tag to start the New Release workflow.🤖 Generated with Claude Code