Repository navigation
Conversation
e0ebe45 to
aa6e841
Compare
|
Also added pull_request event to verify the changes: https://github.com/docker/buildx/actions/runs/31488665508/job/93769785673?pr=4000#step:5:11 |
|
Silly question; could this be done with (forking-)renovate? |
92211a4 to
ebee25e
Compare
I'm not sure tbh, just wanted smth similar to what we already do on other repos: |
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
|
FYI, you can do something like moby/moby#53698 with renovate |
| push: | ||
| branches: | ||
| - 'master' |
There was a problem hiding this comment.
Do we really want to trigger the whole update logic on every push to master?
Can be tricky with the buildkit matrix one and not sure if Renovate is allowed in our org atm |
Forking renovate (what we use in moby) opens PRs from a fork, which means it doesn't need any access to the repository (so, probably more secure than (eg) dependabot) |
| branch: 'deps/scout-version', | ||
| owner: 'docker', | ||
| repo: 'scout-cli', | ||
| path: '.github/workflows/build.yml', |
There was a problem hiding this comment.
Oh, IIRC the default GITHUB_TOKEN will be able to push a branch that modifies the workflows
There was a problem hiding this comment.
Ah good call out, without a GitHub App it will not be able to update workflow files.
I will take a look
4 participants
This adds an
update-depsworkflow that opens dependency update pull requests for the Dockerfile versions used by the test image.The workflow resolves the latest release tags for Docker, registry, BuildKit, Compose, Scout and Undock, updates the matching Dockerfile arguments, and creates a signed pull request for each dependency. The BuildKit update also refreshes the
test-integrationmatrix so it keeps testingmaster,latest,buildx-stable-1, and the latest three stable minor BuildKit release tags.