Bump the actions group with 5 updates - #100
Merged
carole-lavillonniere merged 1 commit intoSep 2, 2026
Merged
Conversation
Bumps the actions group with 5 updates: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `3` | `7` | | [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) | `1` | `4` | | [docker/login-action](https://github.com/docker/login-action) | `2` | `4` | | [docker/metadata-action](https://github.com/docker/metadata-action) | `4` | `6` | | [docker/build-push-action](https://github.com/docker/build-push-action) | `3` | `7` | Updates `actions/checkout` from 3 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v3...v7) Updates `docker/setup-buildx-action` from 1 to 4 - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@v1...v4) Updates `docker/login-action` from 2 to 4 - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@v2...v4) Updates `docker/metadata-action` from 4 to 6 - [Release notes](https://github.com/docker/metadata-action/releases) - [Commits](docker/metadata-action@v4...v6) Updates `docker/build-push-action` from 3 to 7 - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v3...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: docker/setup-buildx-action dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: docker/login-action dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: docker/metadata-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: docker/build-push-action dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
carole-lavillonniere
added a commit
that referenced
this pull request
Sep 2, 2026
The rebuild published only IMAGE:$NEW, so latest stayed on 2026.8.0 while the fix shipped as 2026.9.0. Normally the v* git tag reaches build-push-docker.yml, whose metadata-action mints $NEW, v$NEW, sha-* and moves latest (latest=auto) -- but the bot pushes that tag with GITHUB_TOKEN, which does not trigger workflows. The secops scanner and `docker extension install` both read latest, so it refiled CVE-2026-14456 (BEE-1172, BEE-1173) against the image we had already fixed. Mint the same tag set here instead. type=sha is left out: the candidate is built from the commit before the version bump, so sha-* would point at the wrong tree. Also SHA-pin build-push-docker.yml's five actions, at the versions Dependabot proposes in #100 -- that file has always used floating tags, and it is the one holding the Docker Hub credentials. Both tags already ship provenance attestations, so the major bumps do not change the published index shape.
carole-lavillonniere
added a commit
that referenced
this pull request
Sep 2, 2026
Yesterday's rebuild cleared CVE-2026-14456 and published 2026.9.0, and the scan refiled that same CVE this morning (BEE-1172, BEE-1173). It never looked at the rebuilt image: secops resolves this product from our last two GitHub *releases* (localstack/secops, localstack_products.json: type=github, github_releases_fetch_limit=2), looking each release's tag_name up verbatim on Docker Hub. We pushed a bare git tag and no release, so the scan window stayed on v2026.8.0 -- and Docker Hub had no v2026.9.0 tag for it to resolve either, since the publish step minted only the bare version. So: publish v${NEW} alongside ${NEW}, and cut the release. Also move latest, which nothing in the scan reads but `docker pull` and the marketplace do -- it still points at the superseded 2026.8.0. type=sha stays dropped: the candidate is built from the commit before the version bump. This does not stop a *new* Alpine CVE being ticketed. localstack_products.json still has docker-desktop as rebuild_model=on-release, so classify_findings.py rule 3 tickets OS-layer findings instead of leaving them to the rebuild; that entry wants flipping to scheduled now that this workflow exists. Also SHA-pin build-push-docker.yml's five actions, at the versions Dependabot proposes in #100 -- that file has always used floating tags, and it is the one holding the Docker Hub credentials. Both tags already ship provenance attestations, so the major bumps do not change the published index shape.
Merged
carole-lavillonniere
added a commit
that referenced
this pull request
Sep 2, 2026
Yesterday's rebuild cleared CVE-2026-14456 and published 2026.9.0, and the scan refiled that same CVE this morning (BEE-1172, BEE-1173). It never looked at the rebuilt image: secops resolves this product from our last two GitHub *releases* (localstack/secops, localstack_products.json: type=github, github_releases_fetch_limit=2), looking each release's tag_name up verbatim on Docker Hub. We pushed a bare git tag and no release, so the scan window stayed on v2026.8.0 -- and Docker Hub had no v2026.9.0 tag for it to resolve either, since the publish step minted only the bare version. So: publish v${NEW} alongside ${NEW}, and cut the release. Also move latest, which nothing in the scan reads but `docker pull` and the marketplace do -- it still points at the superseded 2026.8.0. type=sha stays dropped: the candidate is built from the commit before the version bump. This does not stop a *new* Alpine CVE being ticketed. localstack_products.json still has docker-desktop as rebuild_model=on-release, so classify_findings.py rule 3 tickets OS-layer findings instead of leaving them to the rebuild; that entry wants flipping to scheduled now that this workflow exists. Also SHA-pin build-push-docker.yml's five actions, at the versions Dependabot proposes in #100 -- that file has always used floating tags, and it is the one holding the Docker Hub credentials. Both tags already ship provenance attestations, so the major bumps do not change the published index shape.
carole-lavillonniere
approved these changes
Sep 2, 2026
dependabot
Bot
deleted the
dependabot/github_actions/actions-4ef91543cb
branch
September 2, 2026 08:33
carole-lavillonniere
added a commit
that referenced
this pull request
Sep 2, 2026
The repo has no CODEOWNERS in any of the three locations GitHub reads, and nothing in dependabot.yml fills in for it (`reviewers` is gone from Dependabot's options reference; we set no `assignees`). So Dependabot PRs open with no reviewer and no assignee -- #100 has been sitting that way -- and every other PR depends on someone noticing it. @localstack/saas matches where secops already routes this image's CVE findings (localstack_products.json, team: SaaS), and the one collaborator with push access who has been reviewing here is in that team. Same single-glob pattern as secops' CODEOWNERS, which is what auto-requests core-systems on its Dependabot PRs (e.g. localstack/secops#110), so this is proven to work for bot PRs in this org. Note it only auto-requests: main has no branch protection or rulesets, so nothing blocks a merge without review. Enforcing that needs a ruleset with "Require review from Code Owners".
carole-lavillonniere
added a commit
that referenced
this pull request
Sep 3, 2026
…101) Yesterday's rebuild cleared CVE-2026-14456 and published 2026.9.0, and the scan refiled that same CVE this morning (BEE-1172, BEE-1173). It never looked at the rebuilt image: secops resolves this product from our last two GitHub *releases* (localstack/secops, localstack_products.json: type=github, github_releases_fetch_limit=2), looking each release's tag_name up verbatim on Docker Hub. We pushed a bare git tag and no release, so the scan window stayed on v2026.8.0 -- and Docker Hub had no v2026.9.0 tag for it to resolve either, since the publish step minted only the bare version. So: publish v${NEW} alongside ${NEW}, and cut the release. Also move latest, which nothing in the scan reads but `docker pull` and the marketplace do -- it still points at the superseded 2026.8.0. type=sha stays dropped: the candidate is built from the commit before the version bump. This does not stop a *new* Alpine CVE being ticketed. localstack_products.json still has docker-desktop as rebuild_model=on-release, so classify_findings.py rule 3 tickets OS-layer findings instead of leaving them to the rebuild; that entry wants flipping to scheduled now that this workflow exists. Also SHA-pin build-push-docker.yml's five actions, at the versions Dependabot proposes in #100 -- that file has always used floating tags, and it is the one holding the Docker Hub credentials. Both tags already ship provenance attestations, so the major bumps do not change the published index shape.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the actions group with 5 updates:
3714244637Updates
actions/checkoutfrom 3 to 7Release notes
Sourced from actions/checkout's releases.
... (truncated)
Commits
3d3c42eprep v7.0.1 release (#2531)2880268escape values passed to --unset (#2530)12cd223trim only ascii whitespace for branch (#2521)62661c4skip running unsafe pr check if input is default (#2518)e8d4307Bump the minor-actions-dependencies group with 2 updates (#2499)631c942eslint 9 (#2474)4f1f4aeBump actions/upload-artifact from 4 to 7 (#2476)ba09753Bump actions/checkout from 6 to 7 (#2488)b9e0990Bump docker/login-action from 3.3.0 to 4.2.0 (#2479)e8cb398Bump docker/build-push-action from 6.5.0 to 7.2.0 (#2478)Updates
docker/setup-buildx-actionfrom 1 to 4Release notes
Sourced from docker/setup-buildx-action's releases.
... (truncated)
Commits
37fe631Merge pull request #595 from docker/dependabot/npm_and_yarn/docker/actions-to...b5c4f91[dependabot skip] chore: update generated content3e93b63build(deps): bump@docker/actions-toolkitfrom 0.92.0 to 0.95.0e527031Merge pull request #600 from docker/dependabot/npm_and_yarn/brace-expansion-1...c68814b[dependabot skip] chore: update generated content3f891b0build(deps): bump brace-expansion from 1.1.13 to 1.1.18787db26Merge pull request #585 from docker/dependabot/npm_and_yarn/js-yaml-5.2.1f779368[dependabot skip] chore: update generated content7d5e604build(deps): bump js-yaml from 5.2.0 to 5.3.0292c2fbMerge pull request #590 from docker/dependabot/github_actions/actions/setup-n...Updates
docker/login-actionfrom 2 to 4Release notes
Sourced from docker/login-action's releases.
... (truncated)
Commits
dbcb813Merge pull request #1051 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...5bcb015[dependabot skip] chore: update generated contentb30b2f2build(deps): bump the aws-sdk-dependencies group across 1 directory with 2 up...9087f1eMerge pull request #1057 from docker/dependabot/npm_and_yarn/js-yaml-5.2.20009830[dependabot skip] chore: update generated content2325523build(deps): bump js-yaml from 5.2.1 to 5.2.24ec1d4aMerge pull request #1056 from docker/dependabot/npm_and_yarn/postcss-8.5.225fc99baMerge pull request #1053 from docker/dependabot/github_actions/aws-actions/co...e512bd5Merge pull request #1052 from docker/dependabot/github_actions/codeql-actions...a146c91Merge pull request #1059 from crazy-max/harden-buildx-scope-pathsUpdates
docker/metadata-actionfrom 4 to 6Release notes
Sourced from docker/metadata-action's releases.
... (truncated)
Commits
dc80280Merge pull request #696 from docker/dependabot/npm_and_yarn/docker/actions-to...2b9fe83[dependabot skip] chore: update generated content8128ce3chore(deps): Bump@docker/actions-toolkitfrom 0.91.0 to 0.92.01d1c895Merge pull request #695 from docker/dependabot/npm_and_yarn/semver-7.8.57f0c2ddMerge pull request #694 from docker/dependabot/npm_and_yarn/sigstore-4.1.1025f8c5[dependabot skip] chore: update generated contente98d63cchore(deps): Bump semver from 7.8.1 to 7.8.537d9379chore(deps): Bump sigstore from 4.1.0 to 4.1.1a1b8072Merge pull request #690 from docker/dependabot/npm_and_yarn/sigstore/core-3.2.1e0e3381[dependabot skip] chore: update generated contentUpdates
docker/build-push-actionfrom 3 to 7Release notes
Sourced from docker/build-push-action's releases.
... (truncated)
Commits
53b7df9Merge pull request #1572 from docker/dependabot/npm_and_yarn/docker/actions-t...154298c[dependabot skip] chore: update generated contentcb1238bchore(deps): Bump@docker/actions-toolkitfrom 0.91.0 to 0.92.024f845dMerge pull request #1566 from docker/dependabot/npm_and_yarn/js-yaml-4.2.09c69730[dependabot skip] chore: update generated contentbc3a3a5Merge pull request #1574 from docker/dependabot/github_actions/aws-actions/co...a82c504chore(deps): Bump js-yaml from 4.1.1 to 4.3.00285a75Merge pull request #1573 from docker/dependabot/github_actions/actions/cache-...c6ad2a3Merge pull request #1575 from docker/dependabot/github_actions/actions/checko...d37484fMerge pull request #1564 from docker/dependabot/npm_and_yarn/undici-6.27.0Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions