Skip to content

ci(release): publish stable.zip only from a release - #31

Merged
nabeelio merged 1 commit into
releases/2.0from
ci/releases-2.0-publish-on-release
Nov 16, 2026
Merged

nabeelio merged 1 commit into
releases/2.0from
ci/releases-2.0-publish-on-release

Conversation

@nabeelio

Copy link
Copy Markdown
Member

Summary

Same model main got in #28: branch pushes publish a preview zip, only a release writes the file clients download.

 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

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.

Mirror main: a push to releases/2.0 now writes scripts/releases-2.0.zip,
a preview Replane can point a 2.x channel at. Only the release job
(workflow_dispatch: bump, tag, GitHub release) writes scripts/stable.zip,
the file every 2.x client downloads.

Start the package version at 2.0.0 so releases tag as v2.0.x.
@nabeelio
nabeelio merged commit 506ce47 into releases/2.0 Nov 16, 2026
3 checks passed
@nabeelio
nabeelio deleted the ci/releases-2.0-publish-on-release branch November 16, 2026 19:10
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