Publish the first stable desktop release
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 8/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- bun, github, github-actions, typescript
- Ambito
- build-system, desktop, release
Direzione di ricerca
This is a release-launch tracker, not a code change: it needs the domain, signing, notarization and secret setup in the desktop-stable environment, which a newcomer cannot access. The publisher and bun desktop ci stable entry points are the places to read; the done state is the gate checklist, ending with a second stable build proving stable-to-stable updates.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Stable 0.0.23 is published and Latest, and its feed returns 200 (it is still on the r2.dev URL). Canary is at 0.0.46. A stable → stable update hasn't been shown yet. Stable builds Ace.app (dev.ace.desktop, green icon, port 4140, ~/.local/state/ace), the desktop-stable environment has every variable and secret, and publishing marks the GitHub release Latest.
Decisions
- Version: one shared version is in place (stable 0.0.23, canary 0.0.46). The launch version will be chosen at launch.
- Download domain (#40): choose the hostname.
ace.githubnext.comis the landing site, so downloads need another name. Every shipped build has the r2.dev feed baked in, so r2.dev must keep publishing after the move. Keep the/acepath (the R2 key prefix is derived from it). - Canary → stable data: stable uses separate data, so canary users start fresh unless we document a manual move. Stable shares data and port 4140 with
bun ace serve, so CLI hosts conflict with Ace Helper. - Publish gate:
desktop-stableonly accepts runs frommain(set October 15). The workflow also refuses a stablerevisionthat isn't on main (#434). Canary stays open. No required reviewers. - Canary patch versions: canary is
0.0.46.<run>for Sparkle, and shows as0.0.46+<sha7>(#434). Not yet confirmed on a real canary cut.
Gate
- #40 domain live;
ACE_UPDATE_URLupdated; feed servesCache-Control: no-store - #41 third-party notices in
Ace.app/Contents/Resources(Bun, Electrobun, Shiki, …) - #42 secret scan of full history and source review recorded
- #39 published upgrade verified on a second Mac (0.0.25 → 0.0.30, on the r2.dev feed; re-check once #40 lands)
- Build-only
bun desktop ci stable: notarized, stapled app and DMG built (run 38398758462). Still to check after installing: green icon, helper registers asdev.ace.desktop.helper, Cmd+O adds a project, coexists with Canary. -
bun desktop ci stable --publish: 0.0.23 is Latest, and its feed returns 200. - Ship a second stable build to prove stable → stable updates before announcing
- docs/updates.md describes stable releases (#219)
Before Universe (moved from #218)
- Sign releases through GitHub's Gatewatcher instead of a personal Developer ID, and rewrite the release credentials docs to match.
- #214: new channels start unshared (#243) with desktop tools off (#258).
- #215: teach first-time users how Ace works and what sharing exposes. The toggle copy is done; the first-run sheet and "tailnet teammates can see your channels" remain.
Tracked by #7.
- Lingua principale
- TypeScript
- Stelle
- 1
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di githubnext/ace2
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
githubnext/ace2#530 · 1 commento ·
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
githubnext/ace2#437 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
githubnext/ace2#529 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
githubnext/ace2#528 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
githubnext/ace2#511 ·
Tutte le issue di githubnext/ace2
Issue simili
-
engine-rs P3 review-deferral wasm
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
maniator/verticopolis#1154 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
telerik/kendo-react#3861 ·
I maintainer di solito rispondono entro 1 giorno
-
[bug]: use-mobile.ts uses pixel logic, causing UI state de-sync with Tailwind CSS rem breakpointsApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
task
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100