fix(workflow): quack

[wcatz]

Summary by CodeRabbit

Release Notes

• Chores
  • Improved Docker image tagging logic with stricter conditions for the latest tag designation.
  • Enhanced tag generation with additional semantic versioning options.
  • Added build metadata (version, commit, date) to Docker image builds for better traceability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@wcatz has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 12 minutes and 14 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 18581cd and cc8dce6.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

• Dockerfile
• go.mod

📝 Walkthrough

Walkthrough

The Docker build-push workflow is enhanced to apply the "latest" tag only on master or version-tagged pushes, adds new semantic versioning tag patterns and PR event handling, and includes explicit build arguments (VERSION, COMMIT_SHA, BUILD_DATE) propagated to the Docker build step.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration \.github/workflows/docker-build-push\.yml	Restricts latest image tag to master branch or tags beginning with v; adds PR event type and semantic version patterns (major.minor, major) to metadata flavor generation; injects build arguments (VERSION, COMMIT_SHA, BUILD_DATE) into build-push step for Docker layer metadata

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A Docker tale, so neat and tight:
Latest tags now take flight,
Only on master, or v-tags so grand,
Semver patterns expand across the land!
Build args whisper, metadata flows—
Where the version goes, everyone knows!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'fix(workflow): quack' is overly vague and does not clearly describe the actual changes made to the Docker build workflow.	Replace the title with a more descriptive summary, such as 'fix(workflow): refine Docker image tagging and add build metadata' or similar, that accurately reflects the substantive changes to the workflow.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}