Skip to content

Upgrade the shared SDK dependency tuple for Auctioneer #467

Open

Description

@aram356

Purpose

Deliver the coordinated EdgeZero prerequisite for IABTechLab/auctioneer#165. The user explicitly approved a separate SDK upgrade first on 2026-11-11. This is new work after the closed toolchain-refresh issue #365, not a request to reopen it or edit another implementer's checkout.

Scope

Prepare a reviewed, isolated upgrade of the SDK-owned dependency tuple before Auctioneer takes corresponding updates. The candidate must preserve #275's retained outbound HTTP, bounded collection/decoding, deadline, cancellation, completion, header/raw-JSON and resource-ownership contracts. Do not switch consumers to unrelated main and lose those APIs. Coordinate the base/stack with #275's owner; do not mutate its active worktree or branch. An integration branch is not a stable release or deployed-provider qualification.

Observed constraints at #275 head b97efec185abbaa901e633a980975c98ef2f6c3b:

Family Current SDK constraint Observed candidate
Fastly provider family 0.13.1 0.13.2
Worker 0.8.5 0.9.0
Spin fork 7.0.0 at 6c59ed5b4fcb377072763aee0b27a3abdd8edb72 maintained upstream 8.0.0 at acf428a09f516dd1b9fe6ddfd33038f5b0f3e7e0
HTTP / JSON http 1.4.2; serde_json 1.0.150; bytes 1.12.1 http 1.5.0; serde_json 1.0.154; bytes unchanged if still current
Native HTTP reqwest 0.13.4 0.13.5
Async codec stack async-compression 0.4.43; compression-codecs 0.4.38; compression-core 0.4.32 0.4.52; 0.4.47; 0.4.34
Codec implementations brotli 8.0.4; brotli-decompressor 5.0.1; flate2 1.1.9; crc32fast 1.5.0; simd-adler32 0.3.9 9.1.1; 5.0.3; 1.1.11; 1.5.5; 0.3.10

These are audit observations, not a qualified tuple. Refresh source/registry inventory at implementation selection, freeze one exact tuple and report any constraint rather than claiming a partially updated decoder is complete. Spin's eager spawned-task progress repair #169 is merged upstream; tag presence alone does not prove ABI, HTTP/body conversions or runtime progress. Preserve narrow SDK features rather than enabling broad defaults.

Acceptance

  • Review a spec and ordered SDK implementation plan before coding; identify the carrying base and preserve the outbound contract lineage.
  • Refresh root and excluded/generated-consumer dependency graphs and version emitters affected by these shared requirements. Keep shared requirements workspace-owned and .tool-versions authoritative.
  • Migrate provider/shared-type boundaries without incompatible duplicate exposed HTTP/body types. Record every retained old package instance and its owning upstream constraint.
  • Preserve codec framing, truncation, window, cancellation/cleanup and bounded-allocation controls against the new source tuple. Do not relax tests, limits, resource ceilings or capability/readiness claims.
  • Prove Spin eager-progress and completion/lifetime behavior on the selected maintained source; compile and execute the existing guest controls and provider packaging checks where prescribed.
  • Run the full SDK prescribed matrix and generated-consumer/demo checks at the exact proposed revision, with commands, exit codes and real result lines. Missing hosted prerequisites are explicit blockers, never passing evidence.
  • Deliver an immutable revision in IABTechLab/edgezero with dependency/source identities and review evidence for Auctioneer adoption. SDK and Auctioneer remain separately reviewed changes; neither is merged by this issue's authorization.

Downstream Boundary

Auctioneer retains responsibility for its own vendor patches, Unicode 16 migration, cookie compatibility, configuration/compiler/resource controls and full four-adapter matrix. Its single-copy codec source guard cannot simply be weakened to permit an upgraded encoder beside an old decoder. This task is a dependency prerequisite, not a claim that Auctioneer or all deployment targets are qualified.

Activity

  1. added theissue type on Nov 12, 2026
  2. aram356 commented on Nov 12, 2026

    @aram356
    CollaboratorAuthor

    CREATOR: Follow-up read: PR #275 advanced from b97efec185abbaa901e633a980975c98ef2f6c3b to 14a6ca8bb5a5cbe055a1f725bdab8f42569a3bf0 during planning. The GitHub comparison reports two commits and only Fastly lifecycle/progress-test files changed; direct inspection of the latter revision's Cargo.toml confirms the listed shared dependency constraints remain.

    This does not verify or adopt the new lifecycle code. Keep this upgrade separate from the active #275 checkout, coordinate its carrying base, and freeze one reviewed immutable revision before downstream acceptance. Auctioneer #165 has a native blocked-by link to this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions