Skip to content

Comments

CI(deps): Update docker/build-push-action action to v6.8.0#4398

Merged
echoix merged 1 commit intomainfrom
renovate/docker-build-push-action-6.x
Sep 27, 2024
Merged

CI(deps): Update docker/build-push-action action to v6.8.0#4398
echoix merged 1 commit intomainfrom
renovate/docker-build-push-action-6.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 27, 2024

This PR contains the following updates:

Package Type Update Change
docker/build-push-action action minor v6.7.0 -> v6.8.0

Release Notes

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

v6.8.0

Compare Source

Full Changelog: docker/build-push-action@v6.7.0...v6.8.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.

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

@github-actions github-actions bot added the CI Continuous integration label Sep 27, 2024
@echoix echoix merged commit bcb2938 into main Sep 27, 2024
@renovate renovate bot deleted the renovate/docker-build-push-action-6.x branch September 27, 2024 14:40
@neteler
Copy link
Member

neteler commented Sep 27, 2024

Is there a way to enforce that the milestone is set upon PR merging?

@echoix echoix added this to the 8.5.0 milestone Sep 28, 2024
@echoix
Copy link
Member

echoix commented Sep 28, 2024

Is there a way to enforce that the milestone is set upon PR merging?

@neteler I've managed to wire something up this afternoon, and works with pull request target, on merges. Now I only have to make sure it works well when we change versions in include/VERSION. Otherwise, the worse would be that one or two merges per year when that file is changed might use the previous version instead of the new value, if the milestone isn't set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants