Skip to content

Update deprecated ghcr.io image reference to public.ecr.aws - #49

Open
luisina-santos wants to merge 1 commit into
mainfrom
luisinasantos/fix-ghcr-image-references
Open

Update deprecated ghcr.io image reference to public.ecr.aws#49
luisina-santos wants to merge 1 commit into
mainfrom
luisinasantos/fix-ghcr-image-references

Conversation

@luisina-santos

Copy link
Copy Markdown

Summary

  • README.md referenced this connector's image via ghcr.io/conductorone/baton-postgresql:latest; container images are now published to public.ecr.aws/conductorone/baton-postgresql:latest instead.
  • Only this connector's own image reference was updated.
  • Related audit: CXH-2418.

Test plan

  • Verified public.ecr.aws/conductorone/baton-postgresql:latest resolves (manifest exists) before opening this PR.
  • Diff reviewed — only the image domain changed.

🤖 Generated with Claude Code

README.md referenced this connector's image via ghcr.io/conductorone;
container images are now published to public.ecr.aws/conductorone
instead. Only this connector's own image reference was updated.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Connector PR Review: Update deprecated ghcr.io image reference to public.ecr.aws

Blocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base a8f945bc2c10.
Review mode: full
View review run

Review Summary

The full PR diff was scanned for security and correctness: it is a single-line documentation change in README.md swapping the connector's Docker image registry from ghcr.io/conductorone/baton-postgresql:latest to public.ecr.aws/conductorone/baton-postgresql:latest. No Go source, go.mod, go.sum, or config files changed, so no connector behavior, sync path, provisioning path, or dependency surface is affected. The new reference matches what docs/connector.mdx:155 already publishes, so this removes a docs inconsistency rather than creating one.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

  • README.md:41 — the adjacent baton CLI line still uses ghcr.io/conductorone/baton:latest; it is another ConductorOne image and may be covered by the same registry deprecation (CXH-2418). The PR description intentionally scoped it out, so this is informational only — confidence: low, since the baton CLI image is published from a different repo and may still be valid on ghcr.io.
Prompt for AI agents
Verify each finding against the current code and only fix it if needed.

## Suggestions

In `README.md`:
- Around line 41: The second docker command still pulls the baton CLI from
  `ghcr.io/conductorone/baton:latest`, while line 40 now uses
  `public.ecr.aws/conductorone/baton-postgresql:latest`. Confirm whether the
  baton CLI image is also part of the ghcr.io -> public.ecr.aws migration
  (CXH-2418). If it is, update line 41 to
  `public.ecr.aws/conductorone/baton:latest` so both commands in the same code
  block use the same registry. If the baton CLI image is still published to
  ghcr.io, leave line 41 unchanged.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

No blocking issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant