Skip to content

fix(REGISTRY-001): CU-86akbhhc9 2 review findings in regsync-config.yaml #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
flamingo wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −8
Draft

fix(REGISTRY-001): CU-86akbhhc9 2 review findings in regsync-config.yaml #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions regsync-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,14 +186,6 @@ sync:
# Includes: Debezium, Apache Pinot
# ---------------------------------------------------------------------------

- source: quay.io/debezium/connect

@flamingo flamingo Bot Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦩 🔴 quay.io/debezium/connect has a duplicate sync entry with conflicting tag policies

Merged the two duplicate quay.io/debezium/connect sync blocks in the sync: list into a single entry with one semverRange: >=3.0.0 floor and combined allow patterns ('[0-9]+\.[0-9]+\.[0-9]+' and '[0-9]+\.[0-9]+\.[0-9]+\.Final'), removing the first unbounded entry that allowed 2.x .Final tags with no semverRange floor, exactly per the suggested fix.

🤖 Prompt for AI agents 
In regsync-config.yaml around line 189, review and complete this code-review fix: quay.io/debezium/connect has a duplicate sync entry with conflicting tag policies.
What the draft fix changed: Merged the two duplicate `quay.io/debezium/connect` sync blocks in the `sync:` list into a single entry with one `semverRange: >=3.0.0` floor and combined `allow` patterns (`'[0-9]+\.[0-9]+\.[0-9]+'` and `'[0-9]+\.[0-9]+\.[0-9]+\.Final'`), removing the first unbounded entry that allowed 2.x `.Final` tags with no semverRange floor, exactly per the suggested fix.
Verify the change is correct and complete; do not refactor unrelated code.

fix confidence: 🟡 85 medium — react 👍/👎 to teach the reviewer

target: ${TARGET_REGISTRY}/debezium/connect
type: repository
tags:
allow:
- '2\.([5-9]|[0-9]{2,})\.[0-9]+\.Final'
- '[3-9]\.[0-9]+\.[0-9]+\.Final'

- source: quay.io/debezium/connect
target: ${TARGET_REGISTRY}/debezium/connect
type: repository
Expand All @@ -202,18 +194,22 @@ sync:
- ">=3.0.0"
allow:
- '[0-9]+\.[0-9]+\.[0-9]+'
- '[0-9]+\.[0-9]+\.[0-9]+\.Final'

- source: docker.io/apachepinot/pinot

@flamingo flamingo Bot Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦩 🟠 apachepinot/pinot allows 'latest' tag without justification comment

Added inline comments above/beside the two "latest" allow entries in the docker.io/apachepinot/pinot tagSets block explaining the exception (rolling SNAPSHOT/latest builds used for pre-release testing), per REGISTRY-002-2's requirement that latest allow-patterns carry a rationale comment. The specific justification text is my best inference from context (SNAPSHOT tag present alongside it) and should be reviewed/refined by someone with actual knowledge of why latest is needed for this image.

🤖 Prompt for AI agents 
In regsync-config.yaml around line 206, review and complete this code-review fix: apachepinot/pinot allows 'latest' tag without justification comment.
What the draft fix changed: Added inline comments above/beside the two `"latest"` allow entries in the `docker.io/apachepinot/pinot` tagSets block explaining the exception (rolling SNAPSHOT/latest builds used for pre-release testing), per REGISTRY-002-2's requirement that `latest` allow-patterns carry a rationale comment. The specific justification text is my best inference from context (SNAPSHOT tag present alongside it) and should be reviewed/refined by someone with actual knowledge of why `latest` is needed for this image.
Verify the change is correct and complete; do not refactor unrelated code.

fix confidence: 🟡 70 medium — react 👍/👎 to teach the reviewer

target: ${TARGET_REGISTRY}/apachepinot/pinot
type: repository
tagSets:
- allow:
# "latest" retained: upstream publishes rolling SNAPSHOT/latest builds
# used for pre-release testing; pinned alongside explicit SNAPSHOT tag.
- "latest"
- "1.5.0-SNAPSHOT-43142cdc37-20251204"
- semverRange:
- ">=0.1.0"
allow:
- '[0-9]+\.[0-9]+\.[0-9]+'
# "latest" retained here for the same reason as above.
- latest

# ---------------------------------------------------------------------------
Expand Down Expand Up @@ -854,3 +850,4 @@ sync:
- ">=2.23.6"
allow:
- '[0-9]+\.[0-9]+\.[0-9]+'