[gtest] Update version to 1.13.0

[horenmar]

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• The "supports" clause reflects platforms that may be fixed by this new version
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory. -- I actually believe that the clang-tidy patch goes against vcpkg rules about only modifying upstream when necessary for packaging, but upstream has not changed to make it obsolete 🤷 .
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[github-actions]

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

All manifest files must be formatted

./vcpkg format-manifest ports/*/vcpkg.json

Diff

diff --git a/ports/gtest/vcpkg.json b/ports/gtest/vcpkg.json
index cfa5053..8f9d4ce 100644
--- a/ports/gtest/vcpkg.json
+++ b/ports/gtest/vcpkg.json
@@ -1,7 +1,6 @@
 {
   "name": "gtest",
   "version-semver": "1.13.0",
-  "port-version": 0,
   "description": "GoogleTest and GoogleMock testing frameworks",
   "homepage": "https://github.com/google/googletest",
   "license": "BSD-3-Clause",

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

error: checked-in files for gtest have changed but the version was not updated
version: 1.13.0
old SHA: 88117ddab2092390b69f75ef14bcf4d180c07823
new SHA: d388d021abdf1562032aed1587f8bc201a480918
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***

[horenmar]

How do I get the failed build logs out of the CI?

[autoantwort]

2022-12-23_15-25-11.mp4

[jimwang118]

Tested usage successfully by the gtest:x64-windows triplet.

n/a