feat(.github): use docker/metadata-action to generate tags and use cache for apk on build

[KeisukeYamashita]

Why

To improve our CI.

Summary by CodeRabbit

• New Features

  • Enhanced Docker image tagging process to support more dynamic versioning and semantic versioning patterns.
  • Optimized package installation in Docker builds with a caching mechanism to reduce build times.

• Chores

  • Updated .gitignore to better support Rust development by excluding unnecessary files and directories.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Recent changes streamline the GitHub Actions workflow by removing the info job, enhancing Docker image tagging through the use of docker/metadata-action@v5. The .gitignore file has been updated to better accommodate Rust development by ignoring unnecessary files and directories, while the Dockerfile now employs a caching mechanism for APK updates, improving build efficiency.

Changes

Files	Change Summary
.github/workflows/release.yaml	Removed info job; integrated docker/metadata-action@v5 for dynamic image tagging.
.gitignore	Expanded to include patterns for Rust development, ignoring compiled files and executables, and handling Cargo.lock.
Dockerfile	Added a cache mount for apk update to optimize package installation and reduce build times.

Poem

🐇 In a world of code, so neat and bright,
Changes hop in, bringing delight.
Tags now dance with a metadata spin,
Rust files tucked away, let the fun begin!
Docker builds faster, a joyful cheer,
Code rabbits rejoice, for the springtime is here! ✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 31a167d and b470ba6.

Files selected for processing (3)

• .github/workflows/release.yaml (1 hunks)
• .gitignore (1 hunks)
• Dockerfile (1 hunks)

Files skipped from review due to trivial changes (1)

• .gitignore

Additional comments not posted (2)

Dockerfile (1)

4-5: Efficient use of caching for APK updates.

The addition of cache mounts for apk update is a great way to optimize build times by reusing downloaded packages.

Also applies to: 15-16

.github/workflows/release.yaml (1)

100-108: Streamlined Docker image tagging with docker/metadata-action.

The use of docker/metadata-action@v5 for dynamic image tagging simplifies the workflow and enhances the flexibility of version tagging.

[github-actions]

[actionlint] _{reported by reviewdog 🐶}
the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

commitlint-rs/.github/workflows/release.yaml

Line 48 in 00ced16

- uses: actions-rs/toolchain@v1

[github-actions]

[actionlint] _{reported by reviewdog 🐶}
the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]

commitlint-rs/.github/workflows/release.yaml

Line 69 in 00ced16

- uses: actions-rs/toolchain@v1