-
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
New version: Mozilla.Firefox version 122.0 #136015
New version: Mozilla.Firefox version 122.0 #136015
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wingetbot run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
@stephengillie can you please kick this one off again? |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @krystofkrticka,
Is this intentional? (Automated response - build 661) |
Edit: Sorry for duplicate - forgot to unfold the installer file, and had to stop my automation and re-run so it would catch any Apps and Features and not add that message too.. |
@stephengillie thank you for your message I'll look into this once I'm at my computer. |
@stephengillie I just kept version number same as previous version number similar as was for previous version which is that version 121.0 had in manifest 121.0 and version 121.0.1 had in manifest 121.0.1 so unless something changed in manifest schema it is intentional. |
I'll add it to my list of exceptions for this check. |
bb08408
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
winget validate --manifest <path>
?winget install --manifest <path>
?Resolves: #135907