ci(docker): Add latest tag for v* release tags and modify push events

[yamadashy]

Checklist

• Run npm run test
• Run npm run lint

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to two GitHub Actions workflow files: docker.yml and homebrew.yml. The Docker workflow is enhanced with additional triggers for version tags and a new metadata generation step for Docker image tagging. The Homebrew workflow receives a minor name change from "release" to "Homebrew" while maintaining its existing functionality for package management.

Changes

File	Change Summary
.github/workflows/docker.yml	- Added tag trigger for version patterns v[0-9]+.[0-9]+.[0-9]+ - Introduced "Docker metadata" step using docker/metadata-action@v5 - Enhanced image tagging strategies
.github/workflows/homebrew.yml	- Renamed workflow from "release" to "Homebrew" - No functional changes to workflow logic

Possibly related PRs

• Add support for Docker #222: Introduced a new Docker workflow, directly related to Docker workflow modifications.
• ci(docker): Add release permissions to docker workflow #227: Added permissions to the Docker workflow, sharing context with current Docker workflow changes.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6cfd354 and 5746276.

📒 Files selected for processing (1)

• .github/workflows/docker.yml (3 hunks)

🔇 Additional comments (1)

.github/workflows/docker.yml (1)

5-6: LGTM! Version tag trigger pattern is correctly defined.

The semantic versioning pattern v[0-9]+.[0-9]+.[0-9]+ will correctly trigger the workflow for version tags like v1.2.3.

Let's verify the existing tags in the repository to ensure they match this pattern:

✅ Verification successful

✅ Version tag pattern matches existing repository tags

The verification confirms that the repository uses semantic versioning tags that perfectly match the pattern v[0-9]+.[0-9]+.[0-9]+. All existing tags (from v0.1.1 through v0.2.8) follow this format, so the workflow trigger pattern is correctly defined and will work with both existing and future version tags.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check existing version tags for compatibility with the new trigger pattern

# List all tags and validate against the pattern
git ls-remote --tags origin | grep -o 'refs/tags/.*' | cut -d/ -f3 | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' || echo "No matching version tags found"

Length of output: 512

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.07%. Comparing base (baa772f) to head (5746276).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #229   +/-   ##
=======================================
  Coverage   92.07%   92.07%           
=======================================
  Files          44       44           
  Lines        2058     2058           
  Branches      450      450           
=======================================
  Hits         1895     1895           
  Misses        163      163           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.