Update quay.io references from enterprise-contract to conforma

[jsmid1]

Replace references to the old quay.io/enterprise-contract/ec-release-policy with quay.io/conforma/release-policy in configuration documentation examples.

Ref: https://issues.redhat.com/browse/EC-1914

[coderabbitai]

Warning

Review limit reached

@jsmid1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: a72b9883-8f6b-43a4-a259-9acfe5b772b4

📥 Commits

Reviewing files that changed from the base of the PR and between 449633a and 1d0e929.

📒 Files selected for processing (1)

• docs/modules/ROOT/pages/configuration.adoc

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 12:03 PM UTC · Completed 12:06 PM UTC
Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

Review of #3393 — Update quay.io references from enterprise-contract to conforma

Outcome: ✅ Approve

Summary

This is a straightforward documentation-only change that replaces all 17 instances of quay.io/enterprise-contract/ec-release-policy with quay.io/conforma/release-policy in the configuration documentation (docs/modules/ROOT/pages/configuration.adoc). The change is a consistent find-and-replace that correctly updates every occurrence in the file.

Analysis

Dimension	Result
Correctness	✅ All 17 occurrences in configuration.adoc are updated. The replacement string is consistent and correct across YAML and JSON examples. No formatting or structural issues introduced.
Security	✅ No security concerns — documentation-only change to OCI registry references.
Intent & coherence	✅ Change aligns with the enterprise-contract → conforma rebranding (EC-1914). Appropriately scoped to one documentation file.
Style/conventions	✅ Follows existing formatting. No whitespace or structural changes beyond the URL substitution.
Documentation currency	✅ This PR updates stale references. See note below about remaining references in other files.

Note — remaining old references (out of scope)

Other files in the repo still reference quay.io/enterprise-contract/ec-release-policy, including docs/modules/ROOT/pages/ec_inspect_policy.adoc, docs/modules/ROOT/pages/ec_fetch_policy.adoc, cmd/compare/README.md, cmd/inspect/inspect_policy.go, cmd/fetch/fetch_policy.go, hack/demo.sh, benchmark scripts, and test fixtures. These are presumably tracked by EC-1914 and out of scope for this PR.

---

✅ This change is safe to merge.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	53.61% <ø> (-0.01%)	⬇️
generative	17.18% <ø> (ø)
integration	28.36% <ø> (ø)
unit	71.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.