Repository navigation
chore(release): Email20 admits the local demo App upgrade - #11
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
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 demo has App
1.9.0-preview.14-local.20261018. Under SemVer its14-localidentifier sorts above numeric15, so Host127 rejects the published Email19/App preview.15 upgrade with HTTP409APP_INVALID_PACKAGE. No App activation occurred.Prepare bundle preview.20 with App
1.9.1-preview.1, which sorts above both the demo version and published App preview.15. Preserve Email19 assets unchanged; Host127, Runtime18, Kit39/35 and all behavior remain unchanged. Document the version-ordering boundary and update release metadata/links.Validation: 7 App package tests, 45 UI tests, sealed Kit hashes and all57 Runtime provenance modules passed locally. The actual Host127 version comparator rejects the old target and admits the new target for both installed predecessors. CI covers focused Runtime contracts and standalone artifact startup.
Publishing and deploying this corrective release is awaiting the user's decision.