docs(changelog): record --url becoming mandatory - #766
Merged
Conversation
#764 made --url required — the server now refuses to start without it. That shipped with no changelog entry, and the existing Security bullet still described --url as a new optional flag that "sets" the trusted source, implying deployments could leave it unset. It is the most disruptive change in 2.4.0: every 2.3.x deployment that never set --url fails to boot on upgrade. Recorded as BREAKING under Changed, alongside the --encryption-key entry it parallels. Refs #764
This was referenced Aug 14, 2026
Merged
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
1 participant
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.
What
Records that
--urlis now required, as a BREAKING entry under### Changed, and corrects the existing Security bullet that still described it as optional.Why
#764 made
--urlmandatory —validateAuthorizerURLrefuses startup without it — and landed no changelog entry. The only existing mention (Security, from #698) reads as though the flag is optional:This is the most disruptive change in 2.4.0. Every 2.3.x deployment that never set
--urlfails to boot on upgrade, and nothing in the release notes warns them. Verified against a build ofmain:Placed under
### Changedfollowing the--encryption-keyprecedent — the other "refuses to start until you set it" security fix in this release.Related
The docs site has the same gap and worse: 22 of 24 pages with a runnable
authorizercommand omit--url, so their commands no longer boot. Fixed separately in authorizerdev/docs.Refs #764