chore(deps): update docker/build-push-action action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	v3 -> v6

---

Release Notes

docker/build-push-action (docker/build-push-action)

v6

Compare Source

v5

Compare Source

v4

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This update involves upgrading the version of the docker/build-push-action in multiple GitHub Actions workflow files from version 3 to version 6. This enhancement may introduce new features, optimizations, and bug fixes, improving the process of building and pushing Docker images. The core functionality and structure of the workflows remain unchanged.

Changes

Files	Change Summary
.github/workflows/build_and_release_for_{btop,fastfetch,genmon,ncdu,pihole_unbound,pocketbase}.yaml	Upgraded docker/build-push-action from v3 to v6.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Docker Hub

    Developer->>GitHub Actions: Trigger build
    GitHub Actions->>Docker Hub: Build image (v6)
    Docker Hub-->>GitHub Actions: Image built successfully
    GitHub Actions-->>Developer: Build complete

Loading

Poem

🐇 In fields of code, we hop with glee,
Upgrading actions, as spry as can be!
From v3 to v6, we leap and cheer,
New features and fixes, our path is clear!
So let’s build those images, with joy and flair,
A bountiful harvest, we’ll proudly share! 🌼✨

---

🪧 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 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.

[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 52e77fc and 6490e67.

Files selected for processing (6)

• .github/workflows/build_and_release_for_btop.yaml (1 hunks)
• .github/workflows/build_and_release_for_fastfetch.yaml (1 hunks)
• .github/workflows/build_and_release_for_genmon.yaml (1 hunks)
• .github/workflows/build_and_release_for_ncdu.yaml (1 hunks)
• .github/workflows/build_and_release_for_pihole_unbound.yaml (1 hunks)
• .github/workflows/build_and_release_for_pocketbase.yaml (1 hunks)

Additional comments not posted (6)

.github/workflows/build_and_release_for_btop.yaml (1)

39-39: Verify compatibility with docker/build-push-action@v6.

Ensure that the updated action version does not introduce breaking changes or require additional configuration adjustments. Review the release notes for version 6 to confirm compatibility with your current setup.

Verification successful

---

Compatibility Verified for docker/build-push-action@v6

The update to docker/[email protected] does not introduce any breaking changes or require additional configuration adjustments according to the release notes. The upgrade should be compatible with your current workflow setup.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of docker/build-push-action@v6 with the current workflow configuration.

# Test: Check for any breaking changes or additional configuration requirements.
# Expect: No breaking changes and no additional configuration needed.
gh release view v6 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'

Length of output: 122

---

Script:

#!/bin/bash
# List all available releases for the docker/build-push-action repository to verify the existence of version 6.
gh release list --repo docker/build-push-action

Length of output: 1148

---

Script:

#!/bin/bash
# Fetch the release notes for the latest sub-version of v6, which is v6.6.1, to check for breaking changes.
gh release view v6.6.1 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes\|configuration'

Length of output: 123

---

Script:

#!/bin/bash
# Fetch the entire release notes for v6.6.1 to manually verify for any breaking changes or configuration requirements.
gh release view v6.6.1 --repo docker/build-push-action --json body --jq '.body'

Length of output: 280

.github/workflows/build_and_release_for_ncdu.yaml (1)

39-39: Verify compatibility with docker/build-push-action@v6.

Ensure that the updated action version does not introduce breaking changes or require additional configuration adjustments. Review the release notes for version 6 to confirm compatibility with your current setup.

Verification successful

---

No breaking changes found for docker/[email protected].

The release notes for version 6.6.1 of docker/build-push-action do not mention any breaking changes. However, it's advisable to manually review the release notes for any additional configuration requirements.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of docker/build-push-action@v6 with the current workflow configuration.

# Test: Check for any breaking changes or additional configuration requirements.
# Expect: No breaking changes and no additional configuration needed.
gh release view v6 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'

Length of output: 122

---

Script:

#!/bin/bash
# List all releases in the docker/build-push-action repository to verify available versions.
gh release list --repo docker/build-push-action

Length of output: 1148

---

Script:

#!/bin/bash
# Fetch and check the release notes for v6.6.1 of the docker/build-push-action to verify compatibility.
gh release view v6.6.1 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'

Length of output: 108

.github/workflows/build_and_release_for_genmon.yaml (1)

39-39: Verify compatibility with docker/build-push-action@v6.

Ensure that the updated action version does not introduce breaking changes or require additional configuration adjustments. Review the release notes for version 6 to confirm compatibility with your current setup.

Verification successful

---

Compatibility with docker/build-push-action@v6 Verified

The update to version 6 of docker/build-push-action does not introduce any breaking changes. A new feature for generating build summaries is included, which can be disabled if not needed. Ensure to review this feature in your workflow configuration.

• New feature: Build summary generation (can be disabled with DOCKER_BUILD_NO_SUMMARY: true).

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of docker/build-push-action@v6 with the current workflow configuration.

# Test: Check for any breaking changes or additional configuration requirements.
# Expect: No breaking changes and no additional configuration needed.
gh release view v6 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'

Length of output: 122

---

Script:

#!/bin/bash
# List all available releases for docker/build-push-action to verify the existence of version 6.
gh release list --repo docker/build-push-action

Length of output: 1148

---

Script:

#!/bin/bash
# Fetch the release notes for version 6.0.0 of docker/build-push-action to check for breaking changes.
gh release view v6.0.0 --repo docker/build-push-action --json body --jq '.body'

Length of output: 1051

.github/workflows/build_and_release_for_fastfetch.yaml (1)

39-39: Verify compatibility with docker/build-push-action@v6.

The update from v3 to v6 may include breaking changes. Ensure that the workflow is compatible with the new version by reviewing the release notes and testing the workflow.

.github/workflows/build_and_release_for_pocketbase.yaml (1)

39-39: Verify compatibility with docker/build-push-action@v6.

The update from v3 to v6 may include breaking changes. Ensure that the workflow is compatible with the new version by reviewing the release notes and testing the workflow.

.github/workflows/build_and_release_for_pihole_unbound.yaml (1)

43-43: Verify compatibility with docker/build-push-action@v6.

The update from v3 to v6 may include breaking changes. Ensure that the workflow is compatible with the new version by reviewing the release notes and testing the workflow.