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 1e54c55
Browse filesBrowse the repository at this point in the historyBrowse files
fix(desktop): a stale update pointer keeps the API fallback, and previews skip npm
Council round 1:
- The updater still scans the API when the feed has no nightly and the
pointer offers nothing newer than the installed build.
- Preview runs no longer publish the npm launcher, which cannot download
a draft's files.
- The feed job compares the first nightly in releases.atom, respects
PAUSE_NIGHTLY, repairs the pointer when the feed is unreadable, and does
not rewrite the pointer on a GitHub error.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
- name: Fail when the feed hides the newest nightly
1095
-
if: steps.feed.outputs.in_feed == 'false'
1095
+
if: steps.feed.outputs.feed_names_it == 'false'
1096
1096
env:
1097
1097
RELEASE_TAG: ${{ steps.feed.outputs.tag }}
1098
1098
run: |
1099
-
echo "::error::releases.atom does not list $RELEASE_TAG. Nightly installs older than 0.1.10-nightly.20261112.4603 cannot update. See docs/operations/release.md#update-feed."
1099
+
echo "::error::releases.atom could not be read, or its first nightly 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."
1100
1100
exit 1
1101
1101
1102
1102
# The `t3` npm package is a launcher that downloads this version's CLI
1103
1103
# archive from the GitHub Release, so it publishes only once that release
1104
-
# exists. Preview publishes too, under the `preview` dist-tag, which
1105
-
#nothing resolves unless asked for by name.
1104
+
# exists. A preview release stays a draft, whose files are not public, so
0 commit comments