Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Publish the first stable desktop release

Abierto
#217 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
bun, github, github-actions, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/ace2

Todos los issues de githubnext/ace2

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.