-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New version: Geeks3D.FurMark.2 version 2.8.1.0 #259585
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: Geeks3D.FurMark.2 version 2.8.1.0 #259585
Conversation
|
Validation Pipeline Run WinGetSvc-Validation-61-259585-20250524-1 |
|
@microsoft-github-policy-service agree |
|
Validation Pipeline Run WinGetSvc-Validation-61-259585-20250524-2 |
|
Validation Pipeline Run WinGetSvc-Validation-61-259585-20250524-3 |
|
=== manifests\g\Geeks3D\FurMark\2\2.8.1.0 ===
|
|
Validation Pipeline Run WinGetSvc-Validation-61-259585-20250524-4 |
|
Hi @GlaserTools, 👋🏼 Tip It's recommended linking the pull request to the issue using "close keywords". "Close keywords" are ONLY valid in commit messages and pull request descriptions. Editing your description is required. Checklist for Pull Requests
- [x] Have you signed the [Contributor License Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs)?
- [x] Is there a linked Issue? Resolve #259587 |
|
Thank you, I didnt know that, there's always a first time. |
|
Merging failed with:
(Automated response - build 1058.) |
|
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.Microsoft Reviewers: Open in CodeFlow