Skip to content

chore(release): promote v1.7.0-rc.3 -> v1.7.0 - #5161

Merged
myasnikovdaniil merged 5 commits into
release-1.7from
release-1.7.0
Oct 29, 2026
Merged

myasnikovdaniil merged 5 commits into
release-1.7from
release-1.7.0

Conversation

@cozystack-ci

@cozystack-ci cozystack-ci Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Promotes v1.7.0-rc.3 to stable v1.7.0 without 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-once v1.7.0 tag, retagging the candidate and container digests to v1.7.0 (+:latest when 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.3 before promotion.

ℹ️ E2E already ran against the immutable rc, so this promote PR does not run E2E by default. A maintainer may add the full-e2e label 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 (branch update-docs-v1.7.0), generated from the release-1.7.0 staging branch. Do NOT merge that PR until v1.7.0 is 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).

cozystack-ci Bot and others added 5 commits October 27, 2026 09:35
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 cozystack-ci Bot added the release Releasing a new Cozystack version label Oct 29, 2026
@coderabbitai

coderabbitai Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/cleanup Categorizes issue or PR as related to cleanup of code, process, or technical debt size/XXL This PR changes 1000+ lines, ignoring generated files labels Oct 29, 2026
@myasnikovdaniil
myasnikovdaniil merged commit a32334a into release-1.7 Oct 29, 2026
22 of 29 checks passed
@myasnikovdaniil
myasnikovdaniil deleted the release-1.7.0 branch October 29, 2026 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/cleanup Categorizes issue or PR as related to cleanup of code, process, or technical debt release Releasing a new Cozystack version size/XXL This PR changes 1000+ lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant