chore: prepare release - #784
Closed
natalie-o-perret wants to merge 1 commit into
Closed
Conversation
2 tasks
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.
Description
Prep for cutting the v3.1.40 release.
What it actually contains:
ListZonesno longer sends anAuthorizationheader, so DBaaS-only IAM keys (and other restricted keys) can switch zones without hitting 403 on the public/zoneendpoint.Side fix:
CHANGELOG.mdon master had two3.1.39blocks because v3: list-zones: do not send auth header #767's CHANGELOG entry was added on top of an already-released tag. This PR collapses them:3.1.40for v3: list-zones: do not send auth header #767,3.1.39for generator: support '+' symbol as enum separator #783 (enum separator). The taggedv3.1.39content is unchanged.Files:
CHANGELOG.mdv3/version.go(v3.1.39->v3.1.40)Checklist
(For exoscale contributors)
3.1.40block)Testing
Diff is two lines plus a CHANGELOG reshuffle. The CI on the
releaseworkflow is tag-driven, so it'll be exercised when the maintainer pushes thev3.1.40tag.Notes for reviewers
Note
AI-assisted: identified the duplicate 3.1.39 block, drafted the 3.1.40 entry, and bumped the version constant.