chore(release): prepare v26.6.2#2708
Merged
Merged
Conversation
bump VERSION to v26.6.2 and backfill CHANGELOG.md through v26.6.2 with git-cliff. the changelog had frozen at 26.3.6 while tags advanced to v26.6.1, and VERSION had frozen at v26.2.2 (nothing in the release flow bumps it). regenerate the missing 26.3.7, 26.6.0, 26.6.1 sections and add 26.6.2 for the three commits since v26.6.1 (#2705, #2706, #2707).
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.
Summary
Cuts the
v26.6.2patch on the June line and de-stales the release metadata files.VERSION:v26.2.2->v26.6.2. The binary stamps its version from this embedded file viaconvoy.GetVersion()when no build-arg is passed, so it had been reportingv26.2.2on plain builds.CHANGELOG.md: regenerated with the repo's.git-cliff.toml. It had frozen at26.3.6while tags advanced tov26.6.1, so this backfills the missing26.3.7,26.6.0,26.6.1sections and adds26.6.2.v26.6.2covers the three commits onmainsincev26.6.1:refactor(controlplane): require licenser via service constructors(refactor(controlplane): require licenser via service constructors #2705)fix(controlplane): redact secrets and close SSRF gaps across config, delivery, and notifications(fix(controlplane): redact secrets and close SSRF gaps across config, delivery, and notifications #2706)fix(dataplane): capture delivery attempt timestamps around the dispatch call(fix(dataplane): capture delivery attempt timestamps around the dispatch call #2707)Shipping this patch gets the #2706 security hardening and the #2707 timing fix into a tagged self-hosted release.
Notes
chore/monthly-release, so merging does not auto-trigger the tag-stable-release job. After merge, tagv26.6.2at the merge commit (e.g.gh workflow run tag-stable-release.yml --ref main -f version=26.6.2 -f target_sha=<merge_sha>) to build binaries/images.Note
Low Risk
Docs and version metadata only; no application code changes in this PR.
Overview
Prepares the v26.6.2 patch release by updating release metadata only.
VERSIONmoves fromv26.2.2tov26.6.2, so builds that read the embedded file (e.g. viaconvoy.GetVersion()on/healthzand configuration responses) report the correct June-line version instead of a stalev26.2.2.CHANGELOG.mdis regenerated (git-cliff) to catch up from26.3.6through26.6.2, backfilling26.3.7,26.6.0, and26.6.1and documenting the three commits sincev26.6.1: licenser constructor refactor (#2705), controlplane secret redaction / SSRF hardening (#2706), and dataplane delivery-attempt timestamp capture (#2707).Reviewed by Cursor Bugbot for commit 4c44845. Bugbot is set up for automated code reviews on this repo. Configure here.