-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Revert manifest to actual version number Microsoft.Office 16.0.17425.20176 #150300
Revert manifest to actual version number Microsoft.Office 16.0.17425.20176 #150300
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
I think that this is because it's the highest number version for this |
So am I supposed to change the other package? |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Possible duplicate package entry. Similar installer SHA256 hash found in manifest:
|
de00b39
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Checklist for Pull Requests
Manifests
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.The previous update to the manifest contains the wrong version number. That version number is just for the Deployment Tool.
The current version for Microsoft 365 is still 16.0.17425.20176, also as per the official version information page:
https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
The Office Deployment Tool uses a similar but separate versioning:
https://learn.microsoft.com/en-us/officeupdates/odt-release-history
Microsoft Reviewers: Open in CodeFlow