Skip to content

[AAASM-3526] πŸ› (docker): Fix base-image registry org (agent-assembly β†’ ai-agent-assembly)#1196

Merged
Chisanan232 merged 1 commit into
masterfrom
v0.0.1/AAASM-3526/fix/dockerfile_registry_org
Jun 21, 2026
Merged

[AAASM-3526] πŸ› (docker): Fix base-image registry org (agent-assembly β†’ ai-agent-assembly)#1196
Chisanan232 merged 1 commit into
masterfrom
v0.0.1/AAASM-3526/fix/dockerfile_registry_org

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

Description

The 9 base-image Dockerfile header comments referenced the wrong GHCR org ghcr.io/agent-assembly/... (missing the ai- prefix). The canonical org is ai-agent-assembly, so the published images live at ghcr.io/ai-agent-assembly/.... The wrong spelling would point users at a non-existent registry path.

This replaces every ghcr.io/agent-assembly/ β†’ ghcr.io/ai-agent-assembly/ in the 9 docker/Dockerfile.* base images (python 3.12/3.13/3.14-slim, node 20/22/24-slim, go 1.24/1.25/1.26-alpine). All 9 occurrences are in # FROM ... usage-example comments β€” no real FROM/build line depended on the wrong spelling. Only docker/Dockerfile.* is touched; other docker/ files are owned by a parallel ticket.

Type of Change

  • πŸ› Bug fix

Breaking Changes

  • No

Related Issues

  • Related Jira ticket: AAASM-3526

Testing

  • Manual testing performed
  • No tests required (explain why)

git grep "ghcr.io/agent-assembly/" -- docker/Dockerfile.* returns 0 matches after the fix (was 9 before). Sanity-checked one image builds: docker build -f docker/Dockerfile.go-1.24-alpine . completed successfully (exit 0).

Checklist

  • Code follows project style guidelines (cargo fmt, cargo clippy)
  • Self-review of the diff completed
  • Documentation updated if behaviour changed
  • All CI checks passing
  • Commits are small and follow the Gitmoji convention

Closes AAASM-3526

…embly

The 9 base-image Dockerfile header comments referenced the wrong GHCR
org (ghcr.io/agent-assembly/...), which would mislead users to a
non-existent registry path. The canonical org is ai-agent-assembly.
These are usage-example FROM comments; no real build line depended on
the wrong spelling.

Closes AAASM-3526

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Chisanan232

Copy link
Copy Markdown
Contributor Author

πŸ€– Claude Code β€” PR review (record)

CI: βœ… all green β€” Analyze (rust/python/js-ts), Build language image β€” python/node/go, Resolve language matrix, CodeQL all SUCCESS.

Scope vs AAASM-3526: βœ… fully covers it. All 9 base-image Dockerfiles had their header usage-example registry corrected ghcr.io/agent-assembly/ β†’ ghcr.io/ai-agent-assembly/; git grep "ghcr.io/agent-assembly/" β†’ 0 matches; only docker/Dockerfile.* touched (no overlap with AAASM-3524). The implementer verified docker build still succeeds, and confirmed no real FROM/build line depended on the wrong spelling (the Go module path github.com/.../go-sdk is unrelated and correctly untouched).

Verdict: βœ… Ready to approve & merge. Closes AAASM-3526.

@Chisanan232
Chisanan232 merged commit fb8cda1 into master Jun 21, 2026
10 checks passed
@Chisanan232
Chisanan232 deleted the v0.0.1/AAASM-3526/fix/dockerfile_registry_org branch June 21, 2026 14:26
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