fix(create-manifest): manifest not using right tags by arch

[icecrasher321]

Description

Manifest not using right tags by arch -- fix by getting tags as variable.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally and in CI (bun run test)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I have updated version numbers as needed (if needed)
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Security Considerations:

• My changes do not introduce any new security vulnerabilities
• I have considered the security implications of my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2025 11:19pm
sim	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2025 11:19pm

[icecrasher321]

need these to not make manifest lists

[greptile-apps]

Greptile Summary

This PR fixes a critical bug in the Docker manifest creation process within the GitHub Actions workflow. The core issue was that the manifest creation logic wasn't properly constructing architecture-specific image names, which would cause multi-architecture manifest creation to fail or produce incomplete manifests.

The key changes include:

1. Variable renaming for clarity: Changed TAGS to MANIFEST_TAGS to better reflect the purpose of the variable
2. Fixed architecture-specific tag construction: The workflow now properly appends -amd64 and -arm64 suffixes to the base manifest tags when looking for architecture-specific images
3. Added build configuration flags: Disabled provenance and SBOM generation (provenance: false, sbom: false) to prevent potential interference with manifest creation
4. Improved error handling: Added detailed logging and changed from warning-based handling to hard failures when architecture images are missing

This fix is crucial for the Docker build pipeline as it ensures that multi-architecture manifests are properly created and pushed. The workflow builds images with architecture suffixes (as defined in the build matrix), but the previous manifest creation logic failed to account for this naming convention. Now users can pull images without specifying architecture-specific tags, and the manifest will properly route to the correct architecture-specific image.

Confidence score: 4/5

• This is a solid bug fix that addresses a fundamental issue in the Docker manifest creation process
• The score reflects that while the logic is sound, CI/CD changes can have subtle deployment implications that may not be immediately apparent
• The .github/workflows/build.yml file needs careful attention to ensure the matrix build strategy aligns with the new manifest creation logic

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}