From a633001951a7fee7dca46356c591d926964ca2f9 Mon Sep 17 00:00:00 2001
From: scttfrdmn <3011922+scttfrdmn@users.noreply.github.com>
Date: Sat, 1 Aug 2026 18:39:39 -0700
Subject: [PATCH] ci: bump the composition test's substrate pin to v0.85.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Verified locally against a real v0.85.0 server: the seedable task-completion
contract is byte-identical and both TESTs pass unmodified.

v0.85.0 carries substrate#457, which we filed: HeadObject did not resolve a
synthesized completion record, so HEAD answered 404 for a key GET served with
a 200 body. This test never depended on it — spawn's fetchCompletion calls
GetObject directly — but `aws s3 cp` on a completion record was broken below
v0.85.0, so the comment now warns against reaching for it under an older pin.
---
 .github/workflows/composition-test.yml | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/composition-test.yml b/.github/workflows/composition-test.yml
index f5923f3..3102cc3 100644
--- a/.github/workflows/composition-test.yml
+++ b/.github/workflows/composition-test.yml
@@ -19,11 +19,16 @@ on:
 
 env:
   # v0.75.0 was the first release with seedable task-completion (substrate#360);
-  # v0.81.0 keeps that contract byte-identical (verified: POST/DELETE
-  # /v1/spawn/task-completion with the same snake_case payload) and adds the S3 and
-  # error-code fidelity fixes this test's staging step exercises (substrate#391,
-  # #392, #396, #398, #399, #406).
-  SUBSTRATE_VERSION: v0.81.0
+  # v0.85.0 keeps that contract byte-identical (verified locally: POST/DELETE
+  # /v1/spawn/task-completion with the same snake_case payload, and both TESTs
+  # below pass unchanged) and adds the S3 and error-code fidelity fixes this
+  # test's staging step exercises (substrate#391, #392, #396, #398, #399, #406).
+  # v0.85.0 specifically fixes substrate#457 — HeadObject now resolves a
+  # synthesized completion, so HEAD and GET agree. This test doesn't depend on
+  # that (spawn's fetchCompletion calls GetObject directly), but `aws s3 cp` on a
+  # completion record only works from v0.85.0 on, so don't reach for it below a
+  # pin that has it.
+  SUBSTRATE_VERSION: v0.85.0
   SPAWN_VERSION: 0.95.0        # spawn release providing `spawn task run`
 
 jobs: