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

[renovate]

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

• Bump @​docker/actions-toolkit from 0.37.1 to 0.38.0 in https://github.com/docker/build-push-action/pull/1230

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.

[neteler]

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

[echoix]

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.