Gate V1 firmware on pod service versions - #1253
Open
floitsch wants to merge 3 commits into
Open
Conversation
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.
Persist the Artemis service version in compiled pod files and registry manifests, while keeping old pods readable as version-unknown.
Use the major version as the API-generation boundary: pre-V1 builds remain compatible, while V1 CLIs only build and target V1 pods. Firmware, identity files, and initial broker state omit hardware_id for V1 and retain it for pre-V1 compatibility.
Tests cover V1 alpha/beta/RC recognition, old pod and manifest parsing, version round-trips, V1 identity serialization, and service-side parsing of hardware-ID-free update blobs.