Delete legacy decoder stages - #159
Merged
Merged
Conversation
…s default The runtime-overlay path (02-install-runtime-overlay) has soaked on dev and is the proven default. Drop the in-chroot decoder/tar1090/graphs1090 stages, the AIRPLANES_USE_LEGACY_DECODER_STAGES selector, the prerun.sh SKIP-file gating, and the dual-shape fallback in manifest-generator. runtime-manifest.json is now the unconditional source for the five overlay-shipped component SHAs.
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
1 participant
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.
The runtime-overlay path has soaked on dev — the post-merge build-image.yml run on dev built the image, booted it under QEMU, and passed the webconfig upgrade soak end-to-end against the new path. The in-chroot decoder, tar1090, and graphs1090 stages are no longer referenced by the dev build, so they go, along with the runtime-flag that used to pick between them, the prerun.sh SKIP-file gating, and the dual-shape fallback in scripts/manifest-generator.sh. runtime-manifest.json is now the unconditional source for the five overlay-shipped component SHAs that land in the build manifest.
The first stable image build after this lands will require a real
runtime-vX.Y.Ztag — config-stable still carries theruntime-v0.0.0-unreleasedplaceholder for AIRPLANES_RUNTIME_OVERLAY_TAG and the stable image build will fail to download until a concrete stable runtime release exists.