Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Bump docker/setup-buildx-action from 1 to 2 #5551

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 18, 2022

Bumps docker/setup-buildx-action from 1 to 2.

Release notes

Sourced from docker/setup-buildx-action's releases.

v2.0.0

  • Node 16 as default runtime by @​crazy-max (#131)
    • This requires a minimum Actions Runner version of v2.285.0, which is by default available in GHES 3.4 or later.

Full Changelog: docker/setup-buildx-action@v1.7.0...v2.0.0

v1.7.0

  • Standalone mode by @​crazy-max in (#119)
  • Update dev dependencies and workflow by @​crazy-max (#114 #130)
  • Bump tmpl from 1.0.4 to 1.0.5 (#108)
  • Bump ansi-regex from 5.0.0 to 5.0.1 (#109)
  • Bump @​actions/core from 1.5.0 to 1.6.0 (#110)
  • Bump actions/checkout from 2 to 3 (#126)
  • Bump @​actions/tool-cache from 1.7.1 to 1.7.2 (#128)
  • Bump @​actions/exec from 1.1.0 to 1.1.1 (#129)
  • Bump minimist from 1.2.5 to 1.2.6 (#132)
  • Bump codecov/codecov-action from 2 to 3 (#133)
  • Bump semver from 7.3.5 to 7.3.7 (#136)

v1.6.0

  • Add config-inline input (#106)
  • Bump @​actions/core from 1.4.0 to 1.5.0 (#104)
  • Bump codecov/codecov-action from 1 to 2 (#101)

v1.5.1

  • Explicit version spec for caching (#100)

v1.5.0

  • Allow building buildx from source (#99)

v1.4.1

  • Fix docker: invalid reference format (#97)

v1.4.0

  • Update dev deps (#95)
  • Use built-in getExecOutput (#94)
  • Use core.getBooleanInput (#93)
  • Bump @​actions/exec from 1.0.4 to 1.1.0 (#85)
  • Bump y18n from 4.0.0 to 4.0.3 (#91)
  • Bump hosted-git-info from 2.8.8 to 2.8.9 (#89)
  • Bump ws from 7.3.1 to 7.5.0 (#90)
  • Bump @​actions/tool-cache from 1.6.1 to 1.7.1 (#82 #86)
  • Bump @​actions/core from 1.2.7 to 1.4.0 (#80 #87)

v1.3.0

  • Display BuildKit version (#72)

v1.2.0

  • Remove os limitation (#71)
  • Add test job for config input (#68)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 1 to 2.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](docker/setup-buildx-action@v1...v2)

---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested review from a team and chevdor as code owners May 18, 2022 14:09
@dependabot dependabot bot added A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. E2-dependencies Pull requests that update a dependency file. labels May 18, 2022
TriplEight
TriplEight previously approved these changes May 18, 2022
@paritytech-ci paritytech-ci requested a review from a team May 18, 2022 14:18
@TriplEight TriplEight dismissed their stale review May 18, 2022 14:19

wanna experiment with updating SHA

.github/workflows/publish-docker-manual.yml Outdated Show resolved Hide resolved
.github/workflows/publish-docker-release.yml Outdated Show resolved Hide resolved
@paritytech-ci paritytech-ci requested a review from a team May 18, 2022 14:22
The rationale is that dependabot will start to update the SHAs of the deps' versions if there is SHA already. As we wanted https://github.com/paritytech/ci_cd/issues/79

After this is merged, dependabot should raise a new PR with a new SHA of version `v2`.
@chevdor
Copy link
Contributor

chevdor commented May 18, 2022

Using the SHA does not make it very easy for a reader to know what version is used. I see the comment but that means relying on it being correct. Sure you want to do that ?

@paritytech-ci paritytech-ci requested a review from a team May 18, 2022 14:45
@TriplEight
Copy link
Contributor

Yes, there are several security concerns to it. I.e. $someone can tag a malicious version or te-tag one with an approved tag. Many repos of github itself are updating dependencies with dependabot updating them on trusted versions with SHA. The inconvenience is that a human has to update the comment for readability.

@chevdor
Copy link
Contributor

chevdor commented May 18, 2022

Would that not be a better alternative to define an ENV/secret called DOCKER_SETUP-BUILDX-ACTION=<sha> # v2.
That could even be defined globally on the repo so the CI team can bump all approved versions from a single place without digging into each GH workflow ?

@chevdor
Copy link
Contributor

chevdor commented May 18, 2022

An event better alternative would be to fork those actions and you set a latest or safe tag. That makes it simple to check that all our actions are set to paritytech/<name> and you can maintain all in one single place controlled by us and properly tested and security audited. That would be less obfuscated than a random hash and a comment.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A2-insubstantial Pull request requires no code review (e.g., a sub-repository hash update). B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. E2-dependencies Pull requests that update a dependency file.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants