Bump docker/setup-buildx-action from 3.12.0 to 4.3.0 - #6
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
force-pushed
the
dependabot/github_actions/docker/setup-buildx-action-4.3.0
branch
from
September 3, 2026 17:07
b3a8708 to
3fbfde9
Compare
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 3.12.0 to 4.3.0. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@8d2750c...37fe631) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/docker/setup-buildx-action-4.3.0
branch
from
September 4, 2026 15:13
3fbfde9 to
42ec0ed
Compare
Author
|
Superseded by #15. |
dependabot
Bot
deleted the
dependabot/github_actions/docker/setup-buildx-action-4.3.0
branch
September 4, 2026 15:56
karthik1729
added a commit
that referenced
this pull request
Sep 12, 2026
#110, #111, #112, #113, #134, #39, #42, #6, drain #17, commit.verify, B1/B5/B6/B7/B9. `StepReport` carries a `SkipReason`, so `run_state` decides a yield from a value and not from `detail.contains("in flight")`. A finished run that skipped ANY id now ends `skipped`, never `passed` — hourly-1789188203 met the roll guard after stage 2, skipped every step from there and printed "hourly passed" — and `run-job.sh` exits 2 naming the first skip and the passed/failed/skipped counts. The roll guard gets one downgrade window per run, a 10 s cache, and skips only the stage a mid-run roll caught rather than the rest of the journey. A step past its catalogue target is a bad sample while the ceiling stays the timeout, and a stage over 700 s logs `slo.stage.overran`. Assertions: `ws.replicated` and the environment ids that need a StatefulSet read skip rather than pass without a kubeconfig; `git.push.large` skips without a pinned host key instead of filing the HTTP half as the whole SLI; `admin.reads` treats a 503 from the history layer as a skip; `edge.origin` refuses a gateway 5xx; `edge.dns` gives each host a slice of the ceiling and names it; `builder.hidden` reads a visible environment first; `commit.verify` requires the answer to name the oid; `env.exec.ok` names stdout; `srv.drain.handover` asserts `draining` before the repo read; `git.limits` is `reg.limits`. Credentials: `path_of` redacts every long segment under `/v1/cli/`, `/v1/invites/` and `/v2/token`, `call` reports a refusal from those by status alone, and the ProxyCommand workspace id is checked against `^[a-z0-9-]+$` before a shell sees it.
karthik1729
added a commit
that referenced
this pull request
Sep 12, 2026
Review findings #6, #7, #11, #15, #16, #18, #80, #81, #129. Every fix here is one shape: a read that failed was being turned into a value somebody then acted on. A stat that errored listed an image as empty; a visibility read that errored flipped a public repo out of every listing; a body read that errored told the pusher their pack had holes. They now skip, and say what happened. Alongside them: poisoned mutexes recover instead of wedging the node (`LockOrRecover`), accepted peer streams get the dead-peer bounds the dialling side already had, the stranded-merge lane paces whatever its scan found, `remove_protection` validates its pattern like `set` does, a marker's description can no longer forge the fields after it, a blank or too-short `KLOUDLITE_JWT_SECRET` refuses the boot by name instead of panicking, and `head_target` has no `unwrap`.
karthik1729
added a commit
that referenced
this pull request
Sep 12, 2026
Review findings #3, #4, #5, #6, #7, #8, #9, #12, #15, #18, #19, #20, #82. No listing here had a ceiling. `_catalog` stat-ed every unmarked image an owner had to answer a page of two; `referrers` read every signature of a subject on every pull of it; `api_refs`, `volumes`, `volumehistory` and `index::list` each answered whatever was there. Each now takes `?n=`, pages with the object store's own start-after where it has one, and says so with a `Link`. `api_files` reads a size only when asked for one, and `check_repo` scans as far as it can act and no further. The ownership map's own bounds: a map write times out inside the lease that authorised it rather than at it, the epoch is re-checked after every bounded write, a prune pass gets one lease TTL as a whole instead of one per entry, `all()` scans without the role lock held, and a clock reading before a compiled-in floor decides nothing at all — it would have read every live lease as expired and granted every repo away from its owner. Also: the three image write routes get a body limit, and a by-tag push hashes sha512 only for an image that actually holds a sha512 manifest. `deepen-not` lists the repo's refs once and resolves a shorthand under git's own prefixes, not by whichever ref happens to end in that name.
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
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 docker/setup-buildx-action from 3.12.0 to 4.3.0.
Release 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...