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 f45bb46
Browse filesBrowse the repository at this point in the historyBrowse files
# The install steps used to live inline in this file, which made the release body the only
596
+
# place they existed — and the download page pointed at "the release notes" without linking
597
+
# them, so a first-time reader could go from the landing page to an app macOS calls damaged
598
+
# having never seen one (issue #72). Both surfaces now render
599
+
# scripts/t3x/install-instructions.json.
600
+
#
601
+
# A rendering failure must not cost a release: by the time this step runs, both matrix legs
602
+
# have finished and ~22 minutes of macOS and Windows compute is already spent. So a failure
603
+
# here degrades to a minimal body that still points at the download page, and warns.
604
+
- name: Render the release notes
605
+
id: notes
606
+
shell: bash
607
+
env:
608
+
FULL_SHA: ${{ needs.resolve.outputs.sha }}
609
+
SHORT_SHA: ${{ needs.resolve.outputs.short_sha }}
610
+
NOTES_PATH: ${{ runner.temp }}/release-notes.md
611
+
run: |
612
+
set -uo pipefail
613
+
if ! node scripts/t3x/render-release-notes.mjs \
614
+
--sha "$FULL_SHA" --short-sha "$SHORT_SHA" > "$NOTES_PATH"; then
615
+
echo "::warning::Could not render the install notes; publishing a minimal body. This is a bug in scripts/t3x/render-release-notes.mjs — the release itself is fine."
616
+
printf 'Automated fork build of `%s`.\n\nInstall instructions: https://coil.curlycloud.dev/download\n' \
617
+
"$FULL_SHA" > "$NOTES_PATH"
618
+
fi
619
+
echo "path=$NOTES_PATH" >> "$GITHUB_OUTPUT"
620
+
595
621
- name: Create release
596
622
id: create_release
597
623
uses: softprops/action-gh-release@v2
@@ -607,40 +633,7 @@ jobs:
607
633
staged/T3Code-*
608
634
staged/t3x-latest.json
609
635
fail_on_unmatched_files: true
610
-
# The manual-install commands are here rather than in a doc because this page is where
611
-
# someone stands when they need them. Both platforms' in-app updaters already handle
612
-
# this — macAttachCommands/macCopyCommands strip quarantine from the dmg and the staged
613
-
# bundle — so ONLY a hand-downloaded copy hits it, which is exactly the bootstrap case:
614
-
# the first install on a machine, and any install after the updater itself breaks.
615
-
body: |
616
-
Automated fork build of `${{ needs.resolve.outputs.sha }}`.
617
-
618
-
Unsigned. In-app updates strip quarantine themselves; a **manually downloaded** copy
619
-
does not go through that path and needs one command by hand.
620
-
621
-
**macOS** — drag the app to `/Applications` FIRST. Launching from the mounted dmg
622
-
triggers App Translocation, and the updater refuses to replace a translocated app.
Copy file name to clipboardExpand all lines: README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,21 @@ We wanted something performant, remote-ready, and truly open. If we ever go the
12
12
13
13
## Installation
14
14
15
+
> [!IMPORTANT]
16
+
> **This repository is `radroid/t3code`, a fork. It builds an app called Coil, and the package-registry commands further down do not install it.**
17
+
>
18
+
> `winget install T3Tools.T3Code`, `brew install --cask t3-code` and `yay -S t3code-bin` all install upstream's T3 Code — a different app, from a different repository, that updates from a different place. They are correct if upstream is what you want; they are the wrong thing if you got here looking for this fork's build.
19
+
>
20
+
> **Fork builds live at [coil.curlycloud.dev/download](https://coil.curlycloud.dev/download).** That page carries the per-platform first-launch steps inline, and you will need them: these builds are not code-signed, so macOS calls the app _damaged_ on first launch rather than merely unsigned, and right-click → Open does not get past that. The same steps are in the body of every [GitHub release](https://github.com/radroid/t3code/releases) — both are rendered from `scripts/t3x/install-instructions.json`, so they cannot drift.
0 commit comments