-
Notifications
You must be signed in to change notification settings - Fork 5.2k
ktsu.blastmerge v1.0.11 #262069
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
ktsu.blastmerge v1.0.11 #262069
Conversation
Validation Pipeline Run WinGetSvc-Validation-61-262069-20250531-1 |
Automatic Validation ended with:
(Automated response - build 1061.) |
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.
There is no need to remove the metadata/yaml language server comments
manifests/k/ktsu/BlastMerge/1.0.11/ktsu.BlastMerge.installer.yaml
Outdated
Show resolved
Hide resolved
manifests/k/ktsu/BlastMerge/1.0.11/ktsu.BlastMerge.locale.en-US.yaml
Outdated
Show resolved
Hide resolved
FYI: If you want to link a PR to an issue you need to prepend the issue id with a valid keyword in the PR's description |
Co-authored-by: Dvd-Znf <101937630+Dvd-Znf@users.noreply.github.com>
Co-authored-by: Dvd-Znf <101937630+Dvd-Znf@users.noreply.github.com>
Validation Pipeline Run WinGetSvc-Validation-61-262069-20250531-2 |
Co-authored-by: Dvd-Znf <101937630+Dvd-Znf@users.noreply.github.com>
Validation Pipeline Run WinGetSvc-Validation-61-262069-20250531-3 |
Validation Pipeline Run WinGetSvc-Validation-61-262069-20250531-4 |
Attempted fix in HistoryInput.cs: ktsu-dev/BlastMerge@62289c0#diff-e05ca5db961f61bd2ea10956147d1b97935e4ec8f57e0ece7bdaca55c4a08401
Attempted fix in Program.cs: ktsu-dev/BlastMerge@62289c0#diff-e05ca5db961f61bd2ea10956147d1b97935e4ec8f57e0ece7bdaca55c4a08401 Tested with SandboxTest.ps1. |
Fixes "attempted" because I am unable to reproduce in both development and sandbox environment. |
Hi @matt-edmondson, 👋🏼 Tip It's recommended linking this PR to the issue using "close keywords". Take care of those keywords because they're ONLY valid in your commit messages or PR descriptions. Editing your description is required. ❤️ |
Manual Validation ended with:
(Automated response - build 1061.) Edit:
Does this package happen to use a .NET 9.0 framework/runtime? The message
I'm testing these in a Hyper-V VM downloaded with Quick Create. I believe the sandbox might leverage the host OS frameworks and runtimes, but I'm not sure. (I don't actually have the sandbox set up on my laptop, and instead run everything through my VM automation amd orchestration system.) |
@wingetbot run |
Validation Pipeline Run WinGetSvc-Validation-63-262069-20250604-1 |
Yes it uses .NET 9. is there anything the other application had to change, or is it a validation issue? |
Apologies - I didn't notice that it's already listed as a dependency. Are you seeing this error locally? If not, it might be an artifact of the validation environment. |
@stephengillie I havent seen this error in my testing in my dev environment, my spare pcs, or windows sandbox. |
088690a
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 directory's name containing the manifest you're submitting.#262068
Microsoft Reviewers: Open in CodeFlow