deps(deps): bump lambda/provided from 777e461 to 915c26c#310
Closed
dependabot[bot] wants to merge 1 commit into
Closed
deps(deps): bump lambda/provided from 777e461 to 915c26c#310dependabot[bot] wants to merge 1 commit into
777e461 to 915c26c#310dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
requested review from
Cre-eD,
Laboratory,
smecsia and
universe-ops
as code owners
June 3, 2026 00:39
Semgrep Scan ResultsRepository:
Scanned at 2026-06-13 13:10 UTC |
Security Scan ResultsRepository:
Scanned at 2026-06-13 13:11 UTC |
Cre-eD
previously approved these changes
Jun 13, 2026
Cre-eD
added a commit
that referenced
this pull request
Jun 13, 2026
govulncheck reads the stdlib version from go.mod's `go` directive via go-version-file, so a PR branched off a stale base re-flags stdlib advisories that main already fixed by bumping the directive — even when the PR only touches a Dockerfile or an Actions pin. That is why the June-3 digest/action Dependabot PRs (#310, #311) 'failed' a go 1.26.3 stdlib advisory that 1.26.4 main had already resolved. Add a gate step that lists the PR's files and runs the scan only when a Go input (*.go / go.mod / go.sum) changed. The job always runs and reports, so a required status check is never left pending; main-push + the weekly cron still scan unconditionally. Signed-off-by: Dmitrii Creed <creeed22@gmail.com>
Cre-eD
added a commit
that referenced
this pull request
Jun 13, 2026
…R gate (#323) ## Consolidated dependency bumps + govulncheck gate fix Bundles the four open Dependabot PRs into one branch so they can be reviewed and merged together, plus the CI change that stops this class of false block from recurring. Each is a separate, signed commit off current `main`: | Commit | Replaces | Change | |---|---|---| | Go modules | #317 | 17 modules in the `gomod-minor-and-patch` group — `golang.org/x/crypto` 0.52→0.53, `golang.org/x/text` 0.37→0.38, `aws-sdk-go-v2` 1.41.7→1.42.0, `pulumi` 3.243→3.245, `gocloud.dev` 0.45→0.46, `google.golang.org/api` 0.280→0.284, Azure SDK keyvault module restructure, + transitives | | CI actions | #311 | `actions/checkout` v6.0.2→v6.0.3, `github/codeql-action` v4 digest | | caddy | #314 | `caddy` 2.11.3→2.11.4 (builder + runtime stages) | | lambda base | #310 | `public.ecr.aws/lambda/provided:al2023` digest refresh | | **govulncheck gate** | — | skip the reachability scan on PRs that touch no Go input (see below) | `go.mod`/`go.sum` are byte-identical to #317's head (which already passed govulncheck + CodeQL). Locally verified: `go mod tidy` is a no-op and `go build ./...` is clean on `go 1.26.4`. CI on the first four commits was fully green (govulncheck, Build Setup, all Build matrix targets, Run tests, CodeQL, Fuzz). ### Why the Dependabot PRs were stuck on govulncheck `govulncheck.yml` uses `go-version-file: go.mod`, so it scans the **standard library of whatever `go` directive the PR carries**. `main` is now `go 1.26.4` (stdlib `crypto/x509` + `net/textproto` advisories fixed). The two June-3 PRs (#310, #311) were branched while `main` was still `go 1.26.3`, so their stale base still trips those stdlib vulns — even though one only bumps a Docker digest and the other only bumps GitHub Actions, neither of which touches Go. The June-8/11 PRs (#314, #317) were branched after the bump and pass cleanly. ### The gate fix (prevents recurrence) The 5th commit adds a "Decide whether to scan" step: on a PR it lists the changed files and runs govulncheck only when a Go input (`*.go` / `go.mod` / `go.sum`) changed. A PR that changes no Go input cannot alter reachability, and cannot change the stdlib version govulncheck reads from the `go` directive — so a Docker/Actions-only PR is skipped (and reports success) instead of re-flagging whatever sits on its stale base. The job always runs and reports, so a required status check is never left pending; `main`-push and the weekly cron still scan unconditionally, so nothing escapes the gate before release. This PR itself touches `go.mod`/`go.sum`, so it runs the full scan. Once merged, the four Dependabot PRs (#310, #311, #314, #317) can be closed. --------- Signed-off-by: Dmitrii Creed <creeed22@gmail.com>
Bumps lambda/provided from `777e461` to `915c26c`. --- updated-dependencies: - dependency-name: lambda/provided dependency-version: al2023 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
402646e to 777e461777e461 to 915c26c
dependabot
Bot
force-pushed
the
dependabot/docker/lambda/provided-777e461
branch
from
June 13, 2026 13:09
bde9512 to
9235a54
Compare
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
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 lambda/provided from
777e461to915c26c.