What happened
The review agent on PR #1771 identified that hack/update-infra-deployments.sh line 30 contains a hardcoded reference to quay.io/enterprise-contract/ec-task-policy:latest. This was explicitly called out in the agent's review notes: 'Unlike the dual-push infrastructure in update-bundles.sh, this script has a single hardcoded reference with no conforma equivalent. Worth updating in a follow-up.' The PR was correctly scoped to documentation files and this script reference was noted but not blocking. After PR #1771 merged on Jul 14, no follow-up issue was created to track this remaining reference.
What could go better
The review agent correctly identified this stale reference and assessed it as non-blocking for the documentation PR — good judgment. However, the finding was only captured in the review comment body and no tracking issue was created, meaning this improvement could be lost. Confidence is medium because the reference may be intentionally unchanged if the ec-task-policy bundle is not yet published under the conforma org. The review agent could improve by offering to file follow-up issues for non-blocking findings it identifies.
Proposed change
File an issue in conforma/policy to track updating hack/update-infra-deployments.sh line 30 from quay.io/enterprise-contract/ec-task-policy:latest to its conforma equivalent (likely quay.io/conforma/task-policy:latest, following the naming convention where ec- prefix is dropped). If the conforma equivalent does not yet exist, the issue should document that and link to the migration tracking (EC-1914). This is distinct from the intentional dual-push infrastructure in update-bundles.sh and push-bundles.yaml, which pushes to both registries by design.
Validation criteria
An issue exists in conforma/policy tracking the stale reference. The issue is resolved either by updating the reference to the conforma equivalent, or by documenting why it is intentionally deferred (e.g., bundle not yet published under conforma org).
Generated by retro agent from #1771
What happened
The review agent on PR #1771 identified that hack/update-infra-deployments.sh line 30 contains a hardcoded reference to quay.io/enterprise-contract/ec-task-policy:latest. This was explicitly called out in the agent's review notes: 'Unlike the dual-push infrastructure in update-bundles.sh, this script has a single hardcoded reference with no conforma equivalent. Worth updating in a follow-up.' The PR was correctly scoped to documentation files and this script reference was noted but not blocking. After PR #1771 merged on Jul 14, no follow-up issue was created to track this remaining reference.
What could go better
The review agent correctly identified this stale reference and assessed it as non-blocking for the documentation PR — good judgment. However, the finding was only captured in the review comment body and no tracking issue was created, meaning this improvement could be lost. Confidence is medium because the reference may be intentionally unchanged if the ec-task-policy bundle is not yet published under the conforma org. The review agent could improve by offering to file follow-up issues for non-blocking findings it identifies.
Proposed change
File an issue in conforma/policy to track updating hack/update-infra-deployments.sh line 30 from quay.io/enterprise-contract/ec-task-policy:latest to its conforma equivalent (likely quay.io/conforma/task-policy:latest, following the naming convention where ec- prefix is dropped). If the conforma equivalent does not yet exist, the issue should document that and link to the migration tracking (EC-1914). This is distinct from the intentional dual-push infrastructure in update-bundles.sh and push-bundles.yaml, which pushes to both registries by design.
Validation criteria
An issue exists in conforma/policy tracking the stale reference. The issue is resolved either by updating the reference to the conforma equivalent, or by documenting why it is intentionally deferred (e.g., bundle not yet published under conforma org).
Generated by retro agent from #1771