Skip to content

fix(renovate): skip digest refresh on a released stack - #1006

Merged
catinspace-au merged 1 commit into
mainfrom
fix/propagate-skips-released-stack
Nov 11, 2026
Merged

catinspace-au merged 1 commit into
mainfrom
fix/propagate-skips-released-stack

Conversation

@catinspace-au

Copy link
Copy Markdown
Collaborator

The propagate job ran refresh-digests on current for every Renovate push. Once current is tagged, a third-party image re-pushed under the same tag makes refresh-digests refuse to write. busybox, documentdb-local and the CNPG postgresql image moved after 2.2.2-rc.4 was cut. That failed the job on every Renovate PR, including #960.

refresh-digests takes --skip-released, which prints one line naming the stack and exits 0 when its git tag exists. The propagate job passes --skip-released. The mirrors are still checked. Digest moves wait for the next cut.

The propagate job ran refresh-digests on `current` for every Renovate push. Once `current` is tagged, a third-party image re-pushed under the same tag makes refresh-digests refuse to write. busybox, documentdb-local and the CNPG postgresql image moved after 2.2.2-rc.4 was cut. That failed the job on every Renovate PR, including #960.

refresh-digests takes --skip-released, which prints one line naming the stack and exits 0 when its git tag exists. The propagate job passes --skip-released. The mirrors are still checked. Digest moves wait for the next cut.
@catinspace-au
catinspace-au merged commit fa425d8 into main Nov 11, 2026
15 checks passed
@catinspace-au
catinspace-au deleted the fix/propagate-skips-released-stack branch November 11, 2026 15:17
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