Validate compatibility-major-2 server packages - #23
Merged
Merged
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.
The server runtime redesign advances the behavioral compatibility major to 2. The installer already accepts schema-3 manifests with a positive major; its real-package validation script was hard-coded to major 1.
Add an explicit expected-major parameter (default 1), cover major 2 in the manifest-registration fixture, and document the coordinated client/server boundary. No installer engine, package format, SDK registration procedure, or published release changes are required.
Validation: locked Release restore/build with no warnings; 178 core/CLI tests; hidden WPF smoke; signed disposable-catalog installation of both actual unpublished
0.9.0-dev.2server ZIPs from sourceaa0c7ae1a2c5529033a2772ef9aad7b37321c58c, including receipts, coexistence, verification, and exact-package repair. Their SHA-256 values arecfe116a5ca0aa3b8b9e496726eee15305cd162aa37f9abd5e74fcc9721b72688for SA 2024 and30ca84516e814acbba58556af7eedd96e73744c96b067c73a1b69f5516da3e84for SA 2026. No server or SDK was launched by the installer check; test installation records were cleaned up.git diff --checkpassed.Refs #22. Refs spatialanalyzer/briosa#221 and spatialanalyzer/briosa#226. Candidate validation only; no release has been published.