Migration/arm64 images

[lorenzocorallo]

No description provided.

[coderabbitai]

Warning

Review limit reached

@lorenzocorallo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 50330677-f08c-4061-a0e8-1e758f28fa21

📥 Commits

Reviewing files that changed from the base of the PR and between 66f0064 and 426e40c.

📒 Files selected for processing (1)

• .github/workflows/build.yml

Walkthrough

The workflow now builds separate AMD64 and ARM64 images, uses architecture-scoped caches and tags, then publishes both images through a multi-architecture manifest job.

Changes

Multi-architecture image publishing

Layer / File(s)	Summary
Architecture-specific image builds .github/workflows/build.yml	A fail-fast-disabled matrix builds AMD64 and ARM64 images on separate runners. Registry login is unconditional. Image tags and caches include the target architecture.
Manifest release publishing .github/workflows/build.yml	A dependent job generates release tags, combines the architecture-specific images into a multi-architecture manifest, and inspects the first generated tag.

Sequence Diagram(s)

sequenceDiagram
  participant Matrix as GitHub Actions matrix
  participant AMD64 as linux/amd64 runner
  participant ARM64 as linux/arm64 runner
  participant Registry as Container registry
  participant Manifest as manifest job
  Matrix->>AMD64: Build and push AMD64 image
  Matrix->>ARM64: Build and push ARM64 image
  AMD64->>Registry: Push architecture-specific tag
  ARM64->>Registry: Push architecture-specific tag
  Manifest->>Registry: Publish multi-architecture manifest
  Manifest->>Registry: Inspect generated release tag

Loading

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: migrating the build workflow to support ARM64 images.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

.github/workflows/build.yml (2)

58-61: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Restore a tag-push trigger for semantic releases.

The workflow runs only for pushes to main, so vX.Y.Z tags do not trigger semantic-version manifest creation. Add a push.tags filter that matches the repository release tags.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/build.yml around lines 58 - 61, Add a push.tags filter to
the workflow so pushes matching the repository’s vX.Y.Z release-tag pattern
trigger semantic-version manifest creation, while preserving the existing main
branch trigger and metadata configuration.

---

45-50: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

Add a tag trigger for semantic-version image tags.

This workflow runs only for pushes to main, so tag pushes do not run docker/metadata-action and its type=semver rules never produce version tags. Add a tags filter under on.push, or remove the unused semver rules.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/build.yml around lines 45 - 50, Add a semantic-version tag
filter under the workflow’s on.push configuration so pushes matching the
existing docker/metadata-action type=semver rules trigger the build and image
tagging flow. Preserve the current main branch trigger.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In @.github/workflows/build.yml:
- Around line 58-61: Add a push.tags filter to the workflow so pushes matching
the repository’s vX.Y.Z release-tag pattern trigger semantic-version manifest
creation, while preserving the existing main branch trigger and metadata
configuration.
- Around line 45-50: Add a semantic-version tag filter under the workflow’s
on.push configuration so pushes matching the existing docker/metadata-action
type=semver rules trigger the build and image tagging flow. Preserve the current
main branch trigger.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1a895c29-90d4-41de-bf73-ab9a926d76fb

📥 Commits

Reviewing files that changed from the base of the PR and between 91c77dd and 66f0064.

📒 Files selected for processing (1)

• .github/workflows/build.yml