|
| 1 | +# Pearcecodes Fork Release Setup |
| 2 | + |
| 3 | +This fork is configured for public GitHub Releases, Blacksmith runners, macOS |
| 4 | +signing when Apple credentials are present, and npm publishing under the |
| 5 | +`pearcecodes` npm organization. |
| 6 | + |
| 7 | +## P1 release setup |
| 8 | + |
| 9 | +### GitHub |
| 10 | + |
| 11 | +- Repository: `Pearcekieser/t3code` |
| 12 | +- Keep the repository public so GitHub Releases can be used directly by |
| 13 | + `electron-updater`. |
| 14 | +- Enable GitHub Actions for the fork. |
| 15 | +- Install the Blacksmith GitHub app for this repository. |
| 16 | +- In repository Actions settings, allow workflows to create and approve pull |
| 17 | + requests if needed, and set workflow permissions to allow read/write tokens. |
| 18 | + |
| 19 | +The release workflow uses the built-in `GITHUB_TOKEN` for GitHub Releases and |
| 20 | +stable-version bump commits. It does not require a custom release GitHub App. |
| 21 | + |
| 22 | +### npm |
| 23 | + |
| 24 | +- Package: `@pearcecodes/t3code` |
| 25 | +- Binary: `t3code` |
| 26 | +- Access: public |
| 27 | +- Dist-tags: |
| 28 | + - stable releases publish `latest` |
| 29 | + - nightly releases publish `nightly` |
| 30 | + |
| 31 | +The internal workspace package remains named `t3` so Effect deterministic |
| 32 | +service keys keep matching source paths. The release publish script rewrites the |
| 33 | +published package name to `@pearcecodes/t3code` immediately before `npm publish`. |
| 34 | + |
| 35 | +Configure npm trusted publishing for `@pearcecodes/t3code`: |
| 36 | + |
| 37 | +- Provider: GitHub Actions |
| 38 | +- Repository: `Pearcekieser/t3code` |
| 39 | +- Workflow file: `.github/workflows/release.yml` |
| 40 | + |
| 41 | +The npm publish job intentionally uses a GitHub-hosted runner, because npm |
| 42 | +trusted publishing does not currently support self-hosted runners. Keep the |
| 43 | +desktop build jobs on Blacksmith, but keep `publish_cli` on `ubuntu-24.04` |
| 44 | +unless this npm restriction changes. |
| 45 | + |
| 46 | +### Apple signing and notarization |
| 47 | + |
| 48 | +Add these GitHub Actions secrets after enrolling in the Apple Developer Program: |
| 49 | + |
| 50 | +- `CSC_LINK`: base64-encoded `.p12` export of the Developer ID Application |
| 51 | + certificate and private key |
| 52 | +- `CSC_KEY_PASSWORD`: password for the `.p12` |
| 53 | +- `APPLE_API_KEY`: raw App Store Connect API key `.p8` contents |
| 54 | +- `APPLE_API_KEY_ID`: App Store Connect API key ID |
| 55 | +- `APPLE_API_ISSUER`: App Store Connect issuer ID |
| 56 | + |
| 57 | +If any of these are missing, macOS release artifacts are built unsigned. |
| 58 | + |
| 59 | +## P2 hosted web app |
| 60 | + |
| 61 | +The Vercel deployment is intentionally deferred. Planned domains: |
| 62 | + |
| 63 | +- router: `https://code.pearcecodes.com` |
| 64 | +- stable: `latest.code.pearcecodes.com` |
| 65 | +- nightly: `nightly.code.pearcecodes.com` |
| 66 | + |
| 67 | +Before enabling the Vercel job, make `apps/web/vercel.ts` use environment-driven |
| 68 | +hostnames instead of hardcoded `app.t3.codes` origins. |
0 commit comments