Repository navigation
chore(release): promote v1.7.0-rc.3 -> v1.7.0 - #5161
Merged
Merged
Conversation
Signed-off-by: cozystack-ci[bot] <274107086+cozystack-ci[bot]@users.noreply.github.com>
The full changelog is about 260 KB, far past the 125000 characters GitHub accepts as a release description, so the release body becomes a short file under docs/releasenotes/ that keeps what has to be known before upgrading, links each item to the full changelog and carries the contributor lists. The full changelog had to reach rc.3 as well: the backports since rc.2 change what an upgrade does (FoundationDB release lines, the removed image overrides, the bounded vm-disk wait), and an upgrade test from v1.6.5 found statements the rc.2 text got wrong or left out. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
… notes A check against the code at v1.7.0-rc.3 and the upgrade-test records found statements the evidence does not support. talos.registryMirrors cannot be carried over from v1.6, which never had the key. Setting version: v7.3 does not end the refusal of a release whose cluster.version names 7.1. The lost migration log was one observation on a test cluster, not a property of the chart, which keeps the Job. The same check corrects narrower wording: the PostgreSQL restart was seen from v1.6.5 only and v1.6.0 shipped CloudNativePG 1.28.1; a disk added to spec.disks at v1.6.5 attaches only at the VM's next restart; the controller waits on Kube-OVN only on the isp-full variants; host is the node name; the API accepts a spec.cluster edit and the chart refuses it; the copy clone strategy is a CDI setting; and CRD validation ratcheting lets an unchanged dotted prefix through. The OpenSearch entry gains what a test cluster showed about the stale securityconfig-update Job of an instance created on v1.6.x: deleting it makes the operator recreate it on the platform's cluster domain. It stops short of a recovery, because whether the instance then finishes initializing was not confirmed. The release notes become the GitHub release body, so the three of these they repeat are corrected there too. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
Signed-off-by: cozystack-ci[bot] <274107086+cozystack-ci[bot]@users.noreply.github.com>
Signed-off-by: cozystack-ci[bot] <274107086+cozystack-ci[bot]@users.noreply.github.com>
cozystack-ci
Bot
requested review from
Andrei Kvapil (kvaps) and
Timofei Larkin (lllamnyp)
as code owners
October 29, 2026 10:11
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
cozystack-ci
Bot
requested a review
from Aleksei Sviridkin (lexfrei)
as a code owner
October 29, 2026 10:11
myasnikovdaniil
approved these changes
Oct 29, 2026
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.
Promotes
v1.7.0-rc.3to stablev1.7.0without rebuilding containers. Their digests remain bit-for-bit what passed rc e2e; the tag-rewritten packages tree is re-serialized as a temporary OCI candidate and pinned here by digest. On merge, pull-requests-release.yaml verifies that candidate against this tree before creating the write-oncev1.7.0tag, retagging the candidate and container digests tov1.7.0(+:latestwhen this is the newest stable), publishing the stable cozy-installer chart, and publishing the release. Do NOT squash-merge (decision B): the stable tag must attach to a real merge commit.✅ RC full e2e was verified for
v1.7.0-rc.3before promotion.ℹ️ E2E already ran against the immutable rc, so this promote PR does not run E2E by default. A maintainer may add the
full-e2elabel to run the full suite again.✅ Includes
docs/changelogs/v1.7.0.md, which finalize uses verbatim as the published release body.✅ Website docs PR opened/refreshed on
cozystack/website(branchupdate-docs-v1.7.0), generated from therelease-1.7.0staging branch. Do NOT merge that PR untilv1.7.0is published — merging it early flips the site's latest-version pointer to an unpublished version and 404s its docs/API links (see the PR body).