Repository navigation
ci(release): publish stable.zip only from a release - #31
Merged
Merged
Conversation
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.
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
Same model
maingot in #28: branch pushes publish a preview zip, only a release writes the file clients download.src/package.jsongoes1.0.1→2.0.0, so the first dispatch withpatchtagsv2.0.1.Evidence
scripts/stable.zip, which is how the A220 fix shipped unannounced.After: YAML parses (
js-yaml). Tag pushes made by the release job useGITHUB_TOKEN, so they do not retrigger the push workflow;stable.zipis written once per release. Not exercised; first real run is the PMDG release after fix(pmdg): read FSUIPC light switches as bytes #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.0with a bump. Nothing changes for clients until then.