Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

ghost
Copy link

@ghost ghost commented Oct 22, 2024

This PR contains the following updates:

Package Type Update Change
docker/build-push-action action major v5.4.0 -> v6.9.0

Release Notes

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

v6.9.0

Compare Source

Full Changelog: docker/build-push-action@v6.8.0...v6.9.0

v6.8.0

Compare Source

Full Changelog: docker/build-push-action@v6.7.0...v6.8.0

v6.7.0

Compare Source

Full Changelog: docker/build-push-action@v6.6.1...v6.7.0

v6.6.1

Compare Source

Full Changelog: docker/build-push-action@v6.6.0...v6.6.1

v6.6.0

Compare Source

Full Changelog: docker/build-push-action@v6.5.0...v6.6.0

v6.5.0

Compare Source

Full Changelog: docker/build-push-action@v6.4.1...v6.5.0

v6.4.1

Compare Source

Full Changelog: docker/build-push-action@v6.4.0...v6.4.1

v6.4.0

Compare Source

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

v6.3.0

Compare Source

Full Changelog: docker/build-push-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

Full Changelog: docker/build-push-action@v6.1.0...v6.2.0

v6.1.0

Compare Source

Full Changelog: docker/build-push-action@v6.0.2...v6.1.0

v6.0.2

Compare Source

Full Changelog: docker/build-push-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

Full Changelog: docker/build-push-action@v6.0.0...v6.0.1

v6.0.0

Compare Source

[!NOTE]
This major release adds support for generating Build summary and exporting build record for your build. You can disable this feature by setting DOCKER_BUILD_NO_SUMMARY: true environment variable in your workflow.

Full Changelog: docker/build-push-action@v5.4.0...v6.0.0


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@ghost ghost added the auto-update label Oct 22, 2024
@codiumai-pr-agent-free codiumai-pr-agent-free bot added the dependencies Pull requests that update a dependency file label Oct 22, 2024
Copy link

Copy link

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Version Compatibility
Ensure that the new version of docker/build-push-action (v6.9.0) is compatible with the existing workflow and doesn't introduce any breaking changes or unexpected behavior.

Copy link

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Score
Best practice
Use version tags instead of commit hashes for GitHub Actions to improve maintainability

Consider using a version tag instead of a specific commit hash for the
docker/build-push-action. This allows for easier updates and better readability
while still ensuring consistency.

.github/workflows/container_image.yaml [48]

-uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v6.9.0
+uses: docker/build-push-action@v6
  • Apply this suggestion
Suggestion importance[1-10]: 7

Why: Using version tags instead of commit hashes can improve maintainability and readability by making it easier to update to newer versions. However, it may introduce risks if the version tag is updated with breaking changes, so the suggestion is valid but should be considered carefully.

7

💡 Need additional feedback ? start a PR chat

@venkatamutyala venkatamutyala merged commit 914dedc into main Oct 23, 2024
5 checks passed
@venkatamutyala venkatamutyala deleted the renovate/docker-build-push-action-6.x branch October 23, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants