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 a1bc1cd
Browse filesBrowse the repository at this point in the historyBrowse files
fork release: check only the server program, never publish below a published release
- check-archives reads only <stem>/t3 (t3.exe in the zip), not client/, and fails when the
program is missing. The web client names this repository on every Actions build, so it
passed while the server still named upstream.
- check-bundle (new) checks apps/server/dist without dist/client, for the same reason.
- resolve and publish refuse a version that is not above every published release on the
server's stable channel: the server updater takes the newest-created release, so an older
build published later would read as a downgrade. Published releases are always latest.
- Preflight runs fork-release-workflow.test.py too.
- The build sets T3CODE_DESKTOP_UPDATE_REPOSITORY (the name release-repository.ts reads); the
former T3CODE_RELEASE_REPOSITORY is gone. The publish job takes its guard script from
github.workflow_sha, not from the commit being built.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
|| die "Published release $other is on the server's stable channel but has no X.Y.Z or X.Y.Z-fork.N version, so $version cannot be ordered against it; nothing was changed."
80
+
version_gt "$version""$other" \
81
+
|| die "$other is published and not below $version. The server updates to the newest-created release, so publishing $version would show every server a downgrade. Build a newer upstream release instead; to go back, install the older release with t3 update --version X --allow-downgrade. Nothing was changed."
if run "$root" check-archives "$root/assets-good";then pass "check-archives: archives naming this fork pass";else fail "check-archives: archives naming this fork pass";fi
210
-
expect_refused "check-archives: an archive naming upstream fails""win-x64.zip does not name me/t3code""$root" check-archives "$root/assets-bad"
229
+
# Layout of scripts/build-cli-archive.ts: <stem>/t3 (t3.exe in the Windows zip) plus <stem>/client/.
230
+
# The web client names this fork on every Actions build (upstream's apps/web/vite.config.ts), so it
231
+
# must not count; only the program does.
232
+
stage() { # stage DIR STEM PROGRAM PROGRAM_REPO CLIENT_REPO
233
+
mkdir -p "$1/$2/client/assets"
234
+
printf'x\0const repo = "%s";\0'"$4">"$1/$2/$3"
235
+
printf'const u = "%s";'"$5">"$1/$2/client/assets/index.js"
if run "$root" check-archives "$root/assets-good";then pass "check-archives: archives whose program names this fork pass";else fail "check-archives: archives whose program names this fork pass";fi
260
+
expect_refused "check-archives: an archive naming upstream fails""$win/t3.exe in $win.zip does not name me/t3code""$root" check-archives "$root/assets-bad"
261
+
expect_refused "check-archives: t3 names upstream, client/ names the fork -> fails""$lin/t3 in $lin.tar.gz does not name me/t3code""$root" check-archives "$root/assets-repro"
262
+
expect_refused "check-archives: a missing program fails""has no $lin/t3""$root" check-archives "$root/assets-noprog"
211
263
expect_refused "check-archives: no archive at all fails""No CLI archive""$root" check-archives "$root/assets-none"
212
264
265
+
# --- check-bundle (apps/server/dist with the web client in dist/client) ------------------------
if run "$root" check-bundle "$root/dist-good";then pass "check-bundle: a server bundle naming this fork passes";else fail "check-bundle: a server bundle naming this fork passes";fi
275
+
expect_refused "check-bundle: server names upstream, client/ names the fork -> fails""outside client/) does not name me/t3code""$root" check-bundle "$root/dist-repro"
0 commit comments