Skip to content

chore: prepare release - #784

Closed
natalie-o-perret wants to merge 1 commit into
masterfrom
release/v3.1.40
Closed

chore: prepare release#784
natalie-o-perret wants to merge 1 commit into
masterfrom
release/v3.1.40

Conversation

@natalie-o-perret

@natalie-o-perret natalie-o-perret commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Description

Prep for cutting the v3.1.40 release.

What it actually contains:

  • exoscale/egoscale#767: ListZones no longer sends an Authorization header, so DBaaS-only IAM keys (and other restricted keys) can switch zones without hitting 403 on the public /zone endpoint.

Side fix:

Files:

  • CHANGELOG.md
  • v3/version.go (v3.1.39 -> v3.1.40)

Checklist

(For exoscale contributors)

  • Changelog updated (under new 3.1.40 block)
  • Testing

Testing

Diff is two lines plus a CHANGELOG reshuffle. The CI on the release workflow is tag-driven, so it'll be exercised when the maintainer pushes the v3.1.40 tag.

Notes for reviewers

Note

AI-assisted: identified the duplicate 3.1.39 block, drafted the 3.1.40 entry, and bumped the version constant.

- v3: list-zones: skip auth header to avoid IAM enforcement on public endpoint (#767)

Also collapses the duplicate 3.1.39 CHANGELOG block that #767 introduced
on master. The tagged v3.1.39 only contains the enum separator fix
from #783; #767 is added under a fresh 3.1.40 block.
@natalie-o-perret natalie-o-perret changed the title chore: prepare release v3.1.40 chore: prepare release Jun 15, 2026
@natalie-o-perret
natalie-o-perret deleted the release/v3.1.40 branch June 15, 2026 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant