Skip to content

chore(deps): bump busybox from 1.37 to 1.38 in /docker#1

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/docker/busybox-1.38
Open

chore(deps): bump busybox from 1.37 to 1.38 in /docker#1
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/docker/busybox-1.38

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 23, 2026

Copy link
Copy Markdown

Bumps busybox from 1.37 to 1.38.

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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 busybox from 1.37 to 1.38.

---
updated-dependencies:
- dependency-name: busybox
  dependency-version: '1.38'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker Pull requests that update docker code labels May 23, 2026
MattJackson added a commit that referenced this pull request Jun 8, 2026
…ing, LastSync correctness

Full hardening pass on the cross-cluster replication engine (decided: full).
Proportionate to a single-writer control plane — gating + epoch/CAS, NOT consensus.

Data safety:
- Promotion gating: pickHealthiestReplica now excludes never-synced
  (LastSync zero), HealthStale, and HealthBroken replicas. If no
  acceptably-fresh replica exists, auto-failover is SKIPPED + audited
  (reason=no acceptably-fresh replica) rather than promoting an empty/stale
  backend and silently losing the recoverable primary's data.
- LastSync high-water-mark: recordSuccess advances LastSync only when the
  tick fully drains the diff; a truncated tick (>MaxBatchPerTick changes, or
  computeDiff hit the scan cap) stays 'lagging' and leaves LastSync so the
  next tick re-scans the tail — fixes the silent permanent strand of objects
  101+. Deletes route through recordDeleteSuccess and never advance LastSync
  (a delete moves no content; bumping the watermark could shadow un-replicated
  objects).

Fencing (lightweight, monotonic, auditable):
- Add FederatedBucket.FailoverEpoch (back-compat: absent=0). triggerAutoFailover
  bumps epoch on promotion and stamps epoch=N into the audit event.
- store.PromoteWithEpoch does a compare-and-swap under the store lock: the
  promotion persists only if the stored epoch still matches what the watchdog
  read; a stale/concurrent promotion is rejected (ErrEpochChanged) + audited,
  no clobber. Regular Update unchanged for non-promotion edits.

Tests (-race): never-synced/stale not promoted; eligible promoted + epoch
increments + old primary demoted; stale-epoch CAS rejected; >100-object tick
fully replicates across ticks. go build/test ./... + -race green.
@MattJackson MattJackson force-pushed the dependabot/docker/docker/busybox-1.38 branch from 8c35925 to 7d939a8 Compare June 8, 2026 00:33
@MattJackson MattJackson self-requested a review as a code owner June 8, 2026 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docker Pull requests that update docker code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants