Skip to content

chore(release): cut v1.5.0-rc.2 - #2861

Closed
cozystack-ci[bot] wants to merge 1 commit into
mainfrom
release-1.5.0-rc.2
Closed

chore(release): cut v1.5.0-rc.2#2861
cozystack-ci[bot] wants to merge 1 commit into
mainfrom
release-1.5.0-rc.2

Conversation

@cozystack-ci

@cozystack-ci cozystack-ci Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

This PR prepares the release v1.5.0-rc.2.

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 Jun 10, 2026
@github-actions github-actions Bot added size/M This PR changes 30-99 lines, ignoring generated files 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 labels Jun 10, 2026
@myasnikovdaniil myasnikovdaniil removed the release Releasing a new Cozystack version label Jun 11, 2026
myasnikovdaniil added a commit that referenced this pull request Jun 17, 2026
…eral

The two image-pin assertions hard-coded v0.16.1@sha256:..., but release-prep
re-stamps every image tag to the platform version (e.g. v1.5.0-rc.2) and
rebuilds the digest. The exact-literal assertion is green on main yet fails on
every release branch; the breakage stayed hidden because the `release` label
skips the Build job that runs `make unit-tests`, and only surfaced on #2861
once that label was dropped.

Relax both assertions to matchRegex on the cozystack repository + @sha256
digest form, leaving the version string free. A wrong repository or a
non-digest tag still fails the suite.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
myasnikovdaniil added a commit that referenced this pull request Jun 17, 2026
…eral

The two image-pin assertions hard-coded v0.16.1@sha256:..., but release-prep
re-stamps every image tag to the platform version (e.g. v1.5.0-rc.2) and
rebuilds the digest. The exact-literal assertion is green on main yet fails on
every release branch; the breakage stayed hidden because the `release` label
skips the Build job that runs `make unit-tests`, and only surfaced on #2861
once that label was dropped.

Relax both assertions to matchRegex on the cozystack repository + @sha256
digest form, leaving the version string free. A wrong repository or a
non-digest tag still fails the suite.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
@myasnikovdaniil

Copy link
Copy Markdown
Contributor

Release was cancelled

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 size/M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant