Backport upstream versioning and Chocolatey fixes to Classic - #14
Merged
Conversation
Upstream-Commit: 6f9b1d8 Upstream-PR: Devolutions#5296
Upstream-Commit: 67322ff Upstream-PR: Devolutions#5306
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.
Summary
Carries the next selective upstream maintenance batch onto Classic after #13.
Included upstream backports
ChocolateyInstallstate before manager initialization.Classic-specific adaptation
HighestChangedVersionComponent/ configurable skip-level API is newer than Classic. Classic keeps its existingIsUpdateMinor()surface and translates the fix by comparing the full normalized version after confirming the major/minor components match. This preserves Classic behavior while recognizing differences in extra version segments.Provenance
Both entries are recorded in
maintenance/backports.yml, and downstream commits retainUpstream-CommitandUpstream-PRtrailers.Scope
No Avalonia UI feature work and no release/patch-stack regeneration is included. This batch is only reducing the outstanding upstream backend/shared maintenance delta.
Upstream Devolutions#5311 was reviewed but intentionally left out of this batch: its package-list icon restoration primarily lives in the Avalonia frontend, while the shared cache pieces should be assessed against Classic WinUI's icon loading/reset path before taking a partial semantic backport.