remix init fails: registry-stable branch is missing and promotion can't recreate it

Open
#504 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
dart, flutter, github-actions
Domain
cli, release

Research direction

Read open_code/RELEASING.md and inspect the promote workflow and the remix_cli init flow. Start by tracing how promotion creates registry-stable and how the published CLI smoke step resolves it. Done means the branch can be bootstrapped, protected as specified, and fresh apps can run each default preset with the published CLI.

Written by the indexing model from the issue text.

Description

Problem

remix init fails for every new consumer because the registry-stable branch no longer exists on btwld/remix.

$ remix init --preset fortal
No registry-stable branch is published for btwld/remix. GitHub ref registry-stable not found:
https://api.github.com/repos/btwld/remix/commits/registry-stable.

Reproduced with published remix_cli 1.0.0-rc.1 in a fresh Flutter app. GET /repos/btwld/remix/branches/registry-stable returns 404.

Timeline

  • 2026-11-15: Promote registry run 43668656026 created registry-stable at d376f388 (the remix 1.0.0-rc.4 / naked_ui 2.0.0-rc.2 release commit).
  • 2026-11-18 01:01 UTC: The branch was deleted (DeleteEvent in the repo event feed).
  • 2026-11-19: Promote registry run 44463452398 failed on main for all three presets at the published-CLI step, because remix init can't resolve registry-stable.

Why it doesn't recover on its own

Promotion creates or advances registry-stable, but its published-CLI smoke runs the default remix init first. The default init needs registry-stable to exist. Without the branch, every promotion fails, so the branch is never recreated. This is a deadlock.

This was also noted as a checklist item in #495. This issue tracks it on its own because it blocks every new install, independent of the search rollout.

Workaround for users today

Write remix.yaml by hand, then run remix init (which preserves the file):

schema: 3
prefix: Ui
preset: fortal
paths:
  ui: lib/ui
defaultRegistry: "@remix"
registries:
  "@remix":
    repository: btwld/remix
    path: registry
    ref: main
    revision: "d376f388c4c82ea3e26f986d06e4dc78d8fc90e8"

Proposed fix

  • Restore registry-stable at d376f388 (the last promoted revision), through the release process.
  • Protect registry-stable as open_code/RELEASING.md already requires: only GitHub Actions may push, and force pushes and deletion are disabled.
  • Break the deadlock in the promote workflow: when registry-stable is missing, bootstrap it instead of failing in the published-CLI init step (or have that step pin the candidate SHA).
  • remix_cli: add remix init --ref <ref> / --revision <sha>, so users and CI have an official path when the default ref can't be resolved. Today only remix registry update takes a ref, and it requires an existing remix.yaml.
  • Verify the default remix init --preset <vanilla|fortal|heroui> with the published CLI in fresh apps, with no handwritten remix.yaml.

Related (could be separate)

  • init and registry call api.github.com without a token (60 req/h per IP), which is a risk in CI and on shared networks. Consider honoring GITHUB_TOKEN.
Dominant language
Dart
Stars
24
Forks
5
Avg merge
15h 29m
Merged PRs (30d)
144

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from btwld/remix

All issues in btwld/remix

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.