-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Swift.Toolchain 5.5.3 #46123
Swift.Toolchain 5.5.3 #46123
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @wingetbot! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
The check-in policies require a moderator to approve PRs from the community. Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ohhnooo this installer writes the wrong version to the registry 🤦♂️
Name : Swift
Publisher : dt.compnerd.org
Version : 0.0.0.0
ProductCode : {51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}
Uninstall : winget uninstall --id "{51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}"
Hmm, this is a Burn installer, would this be something one of you guys fix? @jedieaston @Trenly
# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.1.0.schema.json | ||
|
||
PackageIdentifier: Swift.Toolchain | ||
PackageVersion: 5.5.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PackageVersion: 5.5.3 | |
PackageVersion: 0.0.0.0 |
# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.1.0.schema.json | ||
|
||
PackageIdentifier: Swift.Toolchain | ||
PackageVersion: 5.5.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PackageVersion: 5.5.3 | |
PackageVersion: 0.0.0.0 |
# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.1.0.schema.json | ||
|
||
PackageIdentifier: Swift.Toolchain | ||
PackageVersion: 5.5.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PackageVersion: 5.5.3 | |
PackageVersion: 0.0.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May I ask what exactly this does? I assume it's a workaround, and not the value we actually want here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, or is this a version number exposed by the installer (I'm not the maintainer of this installer), as explained here: #28544 (comment)
I looked into it last week. I spent like an hour trying to figure out how the heck the build scripts work but didn't get anywhere (it's like three repos, one of which is private so I can't see if they expose the version number to msbuild anywhere). If someone could drop something in the mailing list I bet they'd fix it. |
If I may also ask for some advice: Am I following the correct procedure here for patch version upgrades? That is: Should I create them as new versions with new manifests? Or should I edit the existing 5.5 manifest to point to 5.5.3? I'm not sure how the updater works, so I figured it may be best to create a new manifest for each version. |
You should create a new Manifest for each version yes, if it Auto updates you CAN delete and create a new manifest for the new version in the same PR (will be counted as Move and Modify as long as its in the same Software folder) But we only do that for urls that don't contain versions like Spotify |
It looks like we have 5.5 as the latest version in the repository currently. Unfortunately, without the package properly reporting the version to Windows Apps & Features, the Windows Package Manager would not be able to recognize this as an upgrade. @OfficialEsco what are your thoughts about PRs like this where the package doesn't report the correct version, or doesn't report one at all? Should we block on the related issue below? It's the feature where the client begins to understand the "AppsAndFeatures" entry in the manifest. What additional label would make sense in that case? "Version" or "Apps-and-Features"? or something like that? Related to: |
Yeah that makes sense, |
Sorry for the noise to come. I'm testing some additional automation. |
svanimpe, This package does not report a version in Windows Apps & Features, or it reports an incorrect version. This PR is blocked until support for correlation between values in Windows Apps & Features is supported: |
This package does not report a version in Windows Apps & Features, or it reports an incorrect version. This PR is blocked until support for correlation between values in Windows Apps & Features is supported: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this PR still needed?
Developers of the Swift Toolchain have fixed their MSI version in latest releases: #57288
I was unaware this had been fixed. So yes, we can close this! |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.I've generated these using
YamlCreate
and the manifest version is 1.1.0 instead of 1.0. I assume that's OK?Microsoft Reviewers: Open in CodeFlow