build: bump docker/setup-buildx-action from 4.3.0 to 4.4.1 - #49
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
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 4.3.0 to 4.4.1. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](docker/setup-buildx-action@v4.3.0...v4.4.1) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-version: 4.4.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
CMGS
added a commit
that referenced
this pull request
Sep 21, 2026
Contributor
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
CMGS
deleted the
dependabot/github_actions/docker/setup-buildx-action-4.4.1
branch
September 21, 2026 06:03
CMGS
added a commit
that referenced
this pull request
Sep 21, 2026
* review: drop the stray sentence above markFailed Reconcile re-enters the desire switch regardless of Failed, and the RetryRequested event announces it; the comment restated that. * test: the podpatch short-circuits must never reach the client The three ShortCircuitsNoOp tests asserted only err == nil, which a version without the guards also returns against the fake client. One interceptor-counted test replaces them and fails when a guard is removed. * docs: match the suspend gate, wake short-circuit, sub-agent bind and Failed retry to the code * build: pin cocoon-common at 5d8d95e and import its CRDs The pseudo-version carries meta.VMLive and the toolbox-name bound; the tag bump follows the cocoon-common release. * cut: vmLive and vmClonedAndRunning give way to meta.VMLive The two predicates were the same test with the operands swapped; the shared form now lives in cocoon-common. * cut: drop the two godocs the predicate hoist left behind * build: bump the docker actions and the golang base image docker/setup-qemu-action 4.3.0 -> 4.4.0, docker/setup-buildx-action 4.3.0 -> 4.4.1, docker/build-push-action 7.3.0 -> 7.4.0, and the golang:1.27.1-alpine3.24 digest cf6fca6 -> 4cb7ac9, as Dependabot proposed in #47, #48, #49 and #50. * fix: a migration stuck on an unschedulable target raises MigrateNoCapacity advanceMigration polled Migrating silently when the restored main could not be scheduled on the target node. The arm now mirrors the released-seat wake: podUnschedulable surfaces the scheduler message as a Warning Event and bumps cocoon_operator_migrate_unschedulable_total; the set keeps polling. * fix: a dead-lettered pod turns Progressing False with reason DeadLettered A pod parked at the current generation left the CocoonSet reading Running/Ready with observedGeneration caught up, so nothing in the status said a pod still ran the old spec. buildStatus now collects the parked pods and the Progressing condition reports them; the Ready condition and the phase are unchanged because the parked pod may well be Ready. * fix: a suspend that cannot complete reports Failed after suspendTimeout spec.suspend on a set whose hibernate vk-cocoon refuses (a macOS agent) sat in Suspending forever with no Event and no terminal phase. The suspend gate and the release drain now share pollSuspend: the entry into Suspending is stamped on the cocoonset.cocoonstack.io/suspending-since annotation, after three minutes the set reports Failed with a SuspendTimedOut Warning, and the next pass re-enters Suspending with a fresh deadline, the cadence the CR path uses for HibernateTimedOut. The stamp is cleared when the set settles Suspended. * fix: the suspend deadline counts while the registry probe keeps failing allOwnedPodsHibernated returned the probe error before pollSuspend ran, so an unreachable registry left a set in Suspending behind the requeue backoff with the deadline never evaluated. pollSuspend now takes the probe error: before the deadline it is returned as before, past it the set reports Failed with a SuspendTimedOut Event that carries the error, as the CR path does. * fix: MigrateNoCapacity names no target node The event said the pod was unschedulable on the current spec.nodeName, but a main recreated mid-migration is pinned by the affinity it was built with, so a retarget while it is still Pending leaves it waiting on the old node. The scheduler message already names the node; the docs no longer claim that a spec.nodeName change moves a pending pod. * fix: a suspend retried after its timeout re-enters Suspending before the probe error returns With the registry still failing after a SuspendTimedOut, the set stayed in Failed and every pass reset the deadline stamp, so the timeout could never fire again. pollSuspend now persists Suspending before returning the probe error; the status patch is a no-op once the phase is already Suspending. * docs: the node a pending migration waits on is read from the pod's affinity * fix: start hibernation deadlines before returning probe errors Enter Hibernating before returning a registry probe error so initial requests and retries from Failed receive a deadline. Preserve the existing clock during an active attempt and the completed-snapshot fast path. * docs: the hibernate timeout starts on the first pass and counts failing probes
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 docker/setup-buildx-action from 4.3.0 to 4.4.1.
Release notes
Sourced from docker/setup-buildx-action's releases.
Commits
f87e599Merge pull request #624 from crazy-max/skip-pull-with-endpointe700274chore: update generated content3061c91skip BuildKit image pre-pulls for explicit endpoints594f3bfMerge pull request #609 from crazy-max/pull-buildkit-image-before-createbd6e702chore: update generated content6268c9dpull BuildKit image before builder creatione823525Merge pull request #621 from docker/dependabot/github_actions/codeql-actions-...533ed8ebuild(deps): bump the codeql-actions group with 2 updatesbedaf13Merge pull request #620 from crazy-max/shared-error-helpersd5079fbchore: update generated contentDependabot 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 this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)