chore(signal): promote publisher sha-5c3bb55917c9082e8b77dc61ae284cbf74dd9268 - #13051
chore(signal): promote publisher sha-5c3bb55917c9082e8b77dc61ae284cbf74dd9268#13051gregkonush wants to merge 1 commit into
Conversation
2b6b485 to
08bd888
Compare
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08bd888a50
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| newTag: "sha-b110d41fe899607cb752139b4b67c6f68caf8edd" | ||
| digest: sha256:cac6367e5246635dd8521624b170bf3bee2a1606a2e216b603f894fb6701ca29 |
There was a problem hiding this comment.
Correct the rollout record for this promoted artifact
For this GitOps promotion, the rollout text attached to the reviewed commit records source b1285f3df40407a65f7dcbbd89711cbaf9861323 and digest sha256:4adc50f7..., while this block deploys b110d41fe899607cb752139b4b67c6f68caf8edd with digest sha256:cac6367e...; it also says both writers remain inert even though the managed CronJob is already suspend: false. This leaves the required rollout and impact record pointing at a different artifact and activation state, preventing operators from using it to verify or roll back this promotion; update the notes to match the deployed pin and scheduled-writer impact.
AGENTS.md reference: AGENTS.md:L98-L98
Useful? React with 👍 / 👎.
08bd888 to
90f8f2b
Compare
90f8f2b to
dd525e4
Compare
dd525e4 to
ee3b502
Compare
ee3b502 to
cad13b6
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cad13b6010
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| newTag: "sha-5c3bb55917c9082e8b77dc61ae284cbf74dd9268" | ||
| digest: sha256:0175115e0aa27968919680fd4a6cb99e00e54dc1c40b1ec41d5c34c1bbbbf6df |
There was a problem hiding this comment.
Align the rollout record with the deployed image
Fresh evidence in this revision is that its rollout record names source/tag 2b1c8a2f... and digest sha256:c09116b0..., while this changed pin and the CronJob provenance deploy 5c3bb559... at sha256:0175115e.... Because operators cannot determine which immutable artifact this promotion intends to deploy or use the record reliably for verification and rollback, update the rollout notes to match the manifest (or pin the recorded artifact).
AGENTS.md reference: AGENTS.md:L98-L98
Useful? React with 👍 / 👎.
Summary
Pin the immutable Signal adjusted-daily publisher image and scheduled-writer provenance.
5c3bb55917c9082e8b77dc61ae284cbf74dd9268sha-5c3bb55917c9082e8b77dc61ae284cbf74dd9268sha256:0175115e0aa27968919680fd4a6cb99e00e54dc1c40b1ec41d5c34c1bbbbf6dfRelated Issues
PROOMPT-393
Testing
linux/amd64andlinux/arm64.Screenshots (if applicable)
N/A
Breaking Changes
Pins a bounded publisher without changing scheduled-writer activation. It has no broker or capital authority.
Checklist