Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Publish the first stable desktop release

Offen
  • Stimmt etwas nicht?
#217 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
bun, github, github-actions, typescript
Bereich
build-system, desktop, release

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.com is 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 /ace path (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-stable only accepts runs from main (set October 15). The workflow also refuses a stable revision that isn't on main (#434). Canary stays open. No required reviewers.
  • Canary patch versions: canary is 0.0.46.<run> for Sparkle, and shows as 0.0.46+<sha7> (#434). Not yet confirmed on a real canary cut.

Gate

  • #40 domain live; ACE_UPDATE_URL updated; feed serves Cache-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 as dev.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.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.