Closed
Conversation
francislavoie
approved these changes
Mar 6, 2026
mholt
approved these changes
Mar 6, 2026
Author
✅ Approval Quorum ReachedThis release proposal has been approved by 2 maintainers: @francislavoie, @mholt Tagging InstructionsA maintainer should now create and push the signed tag: git checkout ffb6ab0644f24c5ee6542aca6bd59b7a1b0a8f91
git tag -s v2.11.2 -m "Release v2.11.2"
git push origin v2.11.2
git checkout -The release workflow will automatically start when the tag is pushed. |
Author
🚀 Release Workflow Started
Release workflow is now running. This PR will be updated when the release is published. |
Author
✅ Release PublishedThe release has been successfully published and is now available. |
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 Proposal: v2.11.2
Target Commit:
ffb6ab0644f24c5ee6542aca6bd59b7a1b0a8f91Requested by: @mholt
Commit Status: This is the latest commit (HEAD)
This PR proposes creating release tag
v2.11.2at commitffb6ab0644f24c5ee6542aca6bd59b7a1b0a8f91.Approval Process
This PR requires approval from 2+ maintainers before the tag can be created.
What happens next?
Changes Since Last Release
default_snito work #7325) (httpcaddyfile: Fix missing TLS connection policies when auto_https is default (#7325) #7507) (7ffb640)zstdroll compression (logging: Supportzstdroll compression #7515) (9873752){http.request.tls.client.subject}without client cert #7530) (caddyhttp: Evaluate tls.client placeholders more accurately (fix #7530) #7534) (174fa2d)tls_resolversglobal option for DNS challenge configuration (tls: Addtls_resolversglobal option for DNS challenge configuration #7297) (f145bce)CustomBinaryNameandCustomLongDescription(cmd: Custom binary names throughCustomBinaryNameandCustomLongDescription#7513) (f283062)health_portbeing ignored in health checks (reverseproxy: Fixhealth_portbeing ignored in health checks #7533) (11b56c6)slogerror level logs don't print stack traces (logging: Ensureslogerror level logs don't print stack traces #7512) (45cf61b)/reverse_proxy/upstreams- all in-flight requests #7277) (admin: Track reverse_proxy in-flight requests #7517) (88616e8)copy_headersdoes not strip client-supplied identity headers (Fixes GHSA-7r4p-vjf4-gxv4) (forward_auth:copy_headersdoes not strip client-supplied identity headers (Fixes GHSA-7r4p-vjf4-gxv4) #7545) (2dbcdef)Release Checklist
Note: Tag creation is manual and requires a signed tag from a maintainer.