You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8ac99b6
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ci): read a suffixed image key as a ref, not a config change
The classifier accepted a key only when it was exactly image, repository,
registry, tag or digest. A chart that renders several images names the extras
after what they are for, so backupstrategy-controller carries
chBackupClientImage, rabbitmqBackupClientImage and redisBackupClientImage. The
first two reach the classifier through the @sha256: branch; the third is pinned
by tag alone, so it read as a config change and cost the WHOLE file its overlay.
That package therefore kept its committed release ref in every lane that did not
rebuild it, and served an image from v1.6.0 (22 July) against a tree carrying
four backup strategy drivers added after it. Five of the seven chainsaw failures
behind #4257 trace to that, across three unrelated pull requests.
Accept a prefix before image in the key branch.
Assisted-by: LLM
Signed-off-by: IvanHunters <[email protected]>
0 commit comments