Repository navigation
ci: publish main merges to main.zip instead of stable.zip - #28
Merged
Merged
Conversation
stable.zip now changes only on a release tag. A merge to main uploads main.zip, so a Replane channel can point at unreleased scripts.
nabeelio
added a commit
that referenced
this pull request
Nov 13, 2026
## Summary Follow-up to #28: merges to `main` now publish `aircraft-main.json` and `settings-main.json`. Only a release tag moves the `-latest` aliases. Stable clients stop picking up configs that haven't been released. ```diff publish - aircraft-latest.json, settings-latest.json on every publish + tag v* → aircraft-latest.json, settings-latest.json + main → aircraft-main.json, settings-main.json ``` Versioned copies (`aircraft-<sha|version>.json`) and the manual `release` job are unchanged. ## Merge Danger **Door:** two-way **Blast Radius:** small `aircraft-latest.json` and `settings-latest.json` stop tracking `main` until the next `v*` tag. Point the Replane test channel at the `-main` files.
nabeelio
added a commit
that referenced
this pull request
Nov 16, 2026
## Summary Same model `main` got in #28: branch pushes publish a preview zip, only a release writes the file clients download. ```diff push to releases/2.0 artifacts publish - scripts/stable.zip # every 2.x client, on every merge + scripts/releases-2.0.zip # preview; point a Replane 2.x channel at it purge acars.cdn.vmslabs.net/* workflow_dispatch (bump: patch|minor|major) release bump src/package.json, tag vX.Y.Z, push + scripts/stable.zip # the only writer now purge GitHub release ``` `src/package.json` goes `1.0.1` → `2.0.0`, so the first dispatch with `patch` tags `v2.0.1`. ## Evidence - **Before:** merging #22 on 11-09 pushed straight to `scripts/stable.zip`, which is how the A220 fix shipped unannounced. **After:** YAML parses (`js-yaml`). Tag pushes made by the release job use `GITHUB_TOKEN`, so they do not retrigger the push workflow; `stable.zip` is written once per release. Not exercised; first real run is the PMDG release after #30. ## Merge Danger **Door:** two-way Revert restores publish-on-push. **Blast Radius:** release-process Merging #30 after this no longer ships the PMDG fix by itself; you must run the Build workflow on `releases/2.0` with a bump. Nothing changes for clients until then.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Merges to
mainnow uploadscripts/v8/main.zip. Only a release tag replacesstable.zip. Point a Replane channel atmain.zipto test unreleased scripts.The manual
releasejob still uploadsstable.zip. Aircraft and settings uploads are unchanged: the versioned file plus-latest.Evidence
mainoverwrotestable.zipand the-latestconfigs.After: the
ZIP_NAMEbranch in the publish step:refs/tags/v*uploadsstable.zip, anything else uploadsmain.zip;ALIASdoes the same for-latest/-main. The YAML parses (js-yaml).Merge Danger
Door: two-way
Blast Radius: small
stable.zip,aircraft-latest.jsonandsettings-latest.jsonstop trackingmainuntil the next release. A client on those will not get changes merged after this until av*tag ships them.