You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a5beac1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(release): the Releases backfill skips a version whose publish is in flight in another run
release-integrity's audit now asks `release-pending-publish.mjs in-flight`
before it sets releases-missing. npm settles before the publish job reaches
its own "Create GitHub Releases" step, so a landing audited in that window
used to write the same Releases beside it (17.6.0: run 36958423332 against the
publish of run 36955885276). An in-flight publish, or an answer that cannot be
read, leaves releases-missing unset with a notice or warning; the step stays
green and the image request is untouched. The job gains `actions: read`.
release-verify-npm.mjs batteries 12 and 13 run the audit step's own text, so
their stubs now answer the Actions read; battery 12 gains seven cases pinning
the branch (in flight, unreadable, another version, the control, and no read
on the common path).
Claude-Session: https://claude.ai/code/session_01T9u38rswFp5Rw8DswRUReJ
Co-authored-by: Claude <noreply@anthropic.com>
echo "::warning::${version}'s GitHub Releases or ADR-0087 D4 asset are incomplete, and whether its publish is still in flight could not be asked (reason above). Nothing is backfilled off a guess; the next landing reads again."
1091
+
elif [ "$(jq -r '.state' <<<"$flight")" != 'clear' ]; then
1092
+
jq -c . <<<"$flight"
1093
+
if [ "$(jq -r '.reason' <<<"$flight")" = 'publish-in-flight' ]; then
1094
+
echo "::notice::${version}'s GitHub Releases or ADR-0087 D4 asset are incomplete, but its publish is still in flight ($(jq -r '.detail' <<<"$flight")). That run creates them; nothing is backfilled beside it. A landing after it finishes backfills whatever it did not."
1095
+
else
1096
+
echo "::warning::${version}'s GitHub Releases or ADR-0087 D4 asset are incomplete, and whether its publish is still in flight could not be read ($(jq -r '.detail' <<<"$flight")). Nothing is backfilled off a guess; the next landing reads again."
1097
+
fi
1071
1098
else
1099
+
jq -c . <<<"$flight"
1072
1100
echo "::warning::${version} is on npm but its GitHub Releases or the ADR-0087 D4 asset are incomplete (#4900) — backfilling."
t("a later landing's new package does not hold the backfill back: the image is requested",later.status===0&&later.outputs['image-missing']==='true',said(later));
1766
1821
t('...because the group read is the version commit\'s: the new package is never asked about',later.asked.length===2&&!later.asked.includes('@objectstack/fresh'),said(later));
1822
+
1823
+
// The 17.6.0 race: npm settled before the publish job reached its own
1824
+
// Releases step, and a landing's audit wrote the same Releases beside it.
1825
+
// The two writers are in different runs, so the audit asks the Actions
1826
+
// API whether this version's publish is in flight elsewhere.
t('a publish of ANOTHER version in flight does not hold this one back: the Releases are backfilled',other.outputs['releases-missing']==='true',said(other));
0 commit comments