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 4ea0b78
Browse filesBrowse the repository at this point in the historyBrowse files
fix(release): the update-feed release can never become "latest"
Council round 3:
- Publishing a drafted update-feed release now also sets prerelease and
latest=false, so it cannot become the release stable installs update to.
- An unreadable releases.atom is a warning, not a failed run. Only a feed
that was read and names another nightly first fails. An HTML error page
that answers HTTP 200 counts as unreadable.
- Test: the pointer also wins over a feed whose first nightly is older.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
echo "::error::releases.atom could not be read, so this run could not check it. No tag cleanup is needed unless a later run reports a hidden nightly."
1104
-
else
1105
-
echo "::error::The first nightly in releases.atom is not $RELEASE_TAG. Nightly installs older than 0.1.10-nightly.20261112.4603 cannot reach it. A preview from a branch not rebased onto main is the usual cause. See docs/operations/release.md#update-feed."
1106
+
echo "::warning::releases.atom could not be read, so this run did not check it."
1107
+
exit 0
1106
1108
fi
1109
+
echo "::error::The first nightly in releases.atom is not $RELEASE_TAG. Nightly installs older than 0.1.10-nightly.20261112.4603 cannot reach it. A preview from a branch not rebased onto main is the usual cause. See docs/operations/release.md#update-feed."
1107
1110
exit 1
1108
1111
1109
1112
# The `t3` npm package is a launcher that downloads this version's CLI
0 commit comments