chore: release v3.16.0 - #543
Merged
Merged
Conversation
Bump the operator and operator-crds Helm charts to 3.16.0 with appVersion v3.16.0 and regenerate the operator chart dependency lock. Minor bump: main carries feat(connectivity) #522 since v3.15.1.
Dav-14
enabled auto-merge (squash)
September 18, 2026 14:02
sylr
approved these changes
Sep 18, 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
3 participants
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.
Summary
operatorandoperator-crdsHelm charts to3.16.0v3.16.0Why a minor bump
Changes on
mainsincev3.15.1:Impact
This prepares the next minor Operator release. It does not create the Git tag or publish release artifacts; tagging
v3.16.0on the merge commit remains a post-merge step (theReleaseworkflow then publishes binaries, images and the OCI chartsoperator:3.16.0/operator-crds:3.16.0).The follow-up
formancehq/helmbump (regions→formance) depends on that OCI chart being published.Validation
just helm-update(no diff beyond the three version files: generated templates are in sync)helm lint --strictandhelm templatefor both charts (just helm-validate)mainE2E run for feat(connectivity): protect connectivity-api with the stack auth issuer #522 was still in progress when this PR was opened: https://github.com/formancehq/operator/actions/runs/35351287369