Skip to content

Fix: Document all architecture-specific Docker tags in release notes#40

Merged
konard merged 4 commits intomainfrom
issue-39-fc90ac7ce636
Feb 13, 2026
Merged

Fix: Document all architecture-specific Docker tags in release notes#40
konard merged 4 commits intomainfrom
issue-39-fc90ac7ce636

Conversation

@konard
Copy link
Member

@konard konard commented Feb 13, 2026

Summary

  • Fixed release notes template to document all architecture-specific Docker tags (-amd64, -arm64) for all sandbox images
  • Added case study documentation analyzing the root cause

Problem

The v1.3.0 release notes only mentioned architecture-specific tags for the full sandbox image, but not for essentials, JS, or language sandboxes. However, the CI workflow already correctly builds and pushes these tags to Docker Hub.

Evidence

All images actually have -amd64 and -arm64 tags on Docker Hub:

  • konard/sandbox-essentials:1.3.0-amd64, 1.3.0-arm64
  • konard/sandbox-js:1.3.0-amd64, 1.3.0-arm64
  • konard/sandbox-python:1.3.0-amd64, 1.3.0-arm64
  • (all other language sandboxes) ✅

But the release notes only showed (multi-arch) for these images.

Changes

  1. .github/workflows/release.yml - Updated release notes template:

    • Added -amd64 and -arm64 tag documentation for essentials sandbox
    • Added -amd64 and -arm64 tag documentation for JS sandbox
    • Replaced language sandbox list with a markdown table showing all architecture variants
    • Updated GHCR section to mention all tag patterns
    • Added Quick Start examples for pulling specific architectures
  2. docs/case-studies/issue-39/README.md - Case study documenting:

    • Timeline of events
    • Investigation findings with Docker Hub verification
    • Root cause analysis
    • Solution details

Test Plan

  • YAML syntax verified (python3 -c "import yaml; yaml.safe_load(...)")
  • CI checks pass
  • Next release will include all architecture-specific tags in notes

Closes

Closes #39


🤖 Generated with Claude Code

Adding CLAUDE.md with task information for AI processing.
This file will be removed when the task is complete.

Issue: #39
@konard konard self-assigned this Feb 13, 2026
The release workflow already builds and pushes architecture-specific tags
(-amd64, -arm64) for all sandbox images, but the release notes only
documented "(multi-arch)" for essentials, JS, and language sandboxes.

Changes:
- Add -amd64 and -arm64 tag documentation for essentials sandbox
- Add -amd64 and -arm64 tag documentation for JS sandbox
- Add architecture-specific tags table for all 11 language sandboxes
- Update GHCR section to mention all tag variants
- Update Quick Start with examples for pulling specific architectures
- Add case study documentation for issue #39

Closes #39

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@konard konard changed the title [WIP] Make sure all docker versions support multi-arch, arm64 only, and amd64 only Fix: Document all architecture-specific Docker tags in release notes Feb 13, 2026
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@konard konard marked this pull request as ready for review February 13, 2026 13:10
@konard
Copy link
Member Author

konard commented Feb 13, 2026

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

  • Public pricing estimate: $3.967230
  • Calculated by Anthropic: $2.708983 USD
  • Difference: $-1.258247 (-31.72%)
    📎 Log file uploaded as Gist (657KB)
    🔗 View complete solution draft log

Now working session is ended, feel free to review and add any feedback on the solution draft.

@konard konard merged commit da0a77d into main Feb 13, 2026
19 checks passed
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.

Make sure all docker versions support multi-arch, arm64 only, and amd64 only

1 participant