Skip to content

ci: publish main merges to main.zip instead of stable.zip - #28

Merged
nabeelio merged 1 commit into
mainfrom
ci/main-zip
Nov 12, 2026
Merged

nabeelio merged 1 commit into
mainfrom
ci/main-zip

Conversation

@nabeelio

@nabeelio nabeelio commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Summary

Merges to main now upload scripts/v8/main.zip. Only a release tag replaces stable.zip. Point a Replane channel at main.zip to test unreleased scripts.

 publish (push to main, or a v* tag)
-  stable.zip → s3://acars/scripts/v8/stable.zip
+  tag v*  → s3://acars/scripts/v8/stable.zip
+  main    → s3://acars/scripts/v8/main.zip

The manual release job still uploads stable.zip. Aircraft and settings uploads are unchanged: the versioned file plus -latest.

Evidence

  • Before: every merge to main overwrote stable.zip and the -latest configs.
    After: the ZIP_NAME branch in the publish step: refs/tags/v* uploads stable.zip, anything else uploads main.zip; ALIAS does the same for -latest / -main. The YAML parses (js-yaml).

Merge Danger

Door: two-way

Blast Radius: small

stable.zip, aircraft-latest.json and settings-latest.json stop tracking main until the next release. A client on those will not get changes merged after this until a v* tag ships them.

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
nabeelio merged commit 117cb0d into main Nov 12, 2026
4 checks passed
@nabeelio
nabeelio deleted the ci/main-zip branch November 12, 2026 22:41
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.
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