Skip to content

ci: stable/main config aliases - #29

Merged
nabeelio merged 1 commit into
mainfrom
ci/main-config-aliases
Nov 13, 2026
Merged

nabeelio merged 1 commit into
mainfrom
ci/main-config-aliases

Conversation

@nabeelio

@nabeelio nabeelio commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Summary

Follow-up to #28. Config aliases now match the scripts zip: a release tag publishes aircraft-stable.json and settings-stable.json, and a merge to main publishes aircraft-main.json and settings-main.json.

 publish
-  aircraft-latest.json, settings-latest.json on every publish
+  tag v*  → aircraft-stable.json, settings-stable.json (+ legacy -latest)
+  main    → aircraft-main.json,   settings-main.json
 release (manual)
-  aircraft-latest.json, settings-latest.json
+  aircraft-stable.json, settings-stable.json (+ legacy -latest)

Releases still refresh -latest. Shipped clients fall back to the -latest URLs when Replane is unreachable. Versioned copies (aircraft-<sha|version>.json) are unchanged.

Merge Danger

Door: two-way

Blast Radius: small

-stable files do not exist until the first v* tag after this merges. Cut a release before Replane points at them, or clients get a 404 and keep their cached configs.

Only a release tag moves aircraft-latest.json and settings-latest.json, so stable clients stop picking up unreleased configs.
@nabeelio
nabeelio merged commit 147aa99 into main Nov 13, 2026
4 checks passed
@nabeelio
nabeelio deleted the ci/main-config-aliases branch November 13, 2026 04:44
@nabeelio nabeelio changed the title ci: publish -main config aliases from main merges ci: stable/main config aliases Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant