Repository navigation
Upgrade shared DSH runtime to 0.2.1-rc.5 - #73
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.
Upgrade the shared Web and Desktop DSH Host, Client, and SDK packages from 0.2.1-rc.2 to 0.2.1-rc.5. Preserve the complete native conversation and the existing two narrowly scoped, checksum-locked workbench frame seams. Regenerate the official Web client roster so the upstream entry-customization menus remain available.
Pin ARM macOS and Windows tooling to the official rc.5 installers. Official Intel tooling is currently rc.4; retain that exact provenance while all npm DSH packages on Intel target rc.5.
Validation:
GitHub CI passed for Web, Windows, macOS ARM, macOS Intel and enterprise plugins. The initial Intel job hit the existing 30-second native-module process timeout; the failed job passed on rerun with exactly the same commit and checks. No timeout or runtime-loading gate was weakened.
No release tag or user data migration is included.