Update deprecated ghcr.io image reference to public.ecr.aws

[luisina-santos]

Summary

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

Test plan

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

🤖 Generated with Claude Code

[github-actions]

🟡 Suggestion: The adjacent baton CLI image on this line still points at ghcr.io/conductorone/baton:latest. If the ghcr.io deprecation applies org-wide (as the PR title implies), this line will break too and the block is now inconsistent — one line on ECR, one on GHCR. Intentionally out of scope per the PR description, so non-blocking, but worth confirming whether public.ecr.aws/conductorone/baton:latest exists and updating it here as well.

[github-actions]

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 60f0ca3efe3d.
Review mode: full
View review run

Review Summary

The full PR diff was scanned for security and correctness: it is a single-line README documentation change swapping this connector's Docker image from ghcr.io/conductorone/baton-linear:latest to public.ecr.aws/conductorone/baton-linear:latest. No Go source, go.mod/go.sum, config, or provisioning code changed, so no connector-behavior, dependency, or breaking-change criteria apply. The new registry path matches what docs/connector.mdx:216 already documents, so the docs are consistent after this change; one non-blocking consistency note is below.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

• README.md:24 — the adjacent baton CLI image still uses ghcr.io/conductorone/baton:latest, leaving the docker block split across two registries; confirm whether an ECR equivalent exists and update it too (explicitly out of scope per the PR description).

Prompt for AI agents

Verify each finding against the current code and only fix it if needed.

## Suggestions

In `README.md`:
- Around line 24: The docker usage block now mixes two registries. Line 23 was updated to
  `public.ecr.aws/conductorone/baton-linear:latest`, but line 24 still pulls the baton CLI
  from `ghcr.io/conductorone/baton:latest`. Check whether
  `public.ecr.aws/conductorone/baton:latest` is published; if it is, update line 24 to use it
  so both commands reference the same (non-deprecated) registry. If the baton CLI is still
  only published to ghcr.io, leave line 24 as is.

[github-actions]

No blocking issues found.