Update vcpkg-scripts SHA to 2025-07-15. (#1725)

BillyONeal · web-flow · commit d6c019e723df · 2025-07-15T14:14:25.000-07:00
diff --git a/docs/vcpkg_tool_release_process.md b/docs/vcpkg_tool_release_process.md
@@ -3,8 +3,8 @@
 This document describes the acceptance criteria / process we use when doing a vcpkg-tool update,
 such as https://github.com/microsoft/vcpkg/pull/23757
 
-1. Update `$/vcpkg-init/vcpkg-scripts-sha.txt` to the current `master` branch SHA in the registry
-  repo.
+1. Run `$/vcpkg-init/update-scripts-sha.ps1` to update `$/vcpkg-init/vcpkg-scripts-sha.txt` to the
+  current `master` branch SHA in the registry repo.
 1. Verify that all tests etc. are passing in the vcpkg-tool repo's `main` branch, and that the
   contents therein are acceptable for release. (Steps after this will sign code there, so this
   review is responsible gating what has access to code signing.)
diff --git a/vcpkg-init/update-scripts-sha.ps1 b/vcpkg-init/update-scripts-sha.ps1
@@ -0,0 +1,3 @@
+git ls-remote https://github.com/microsoft/vcpkg master | `
+    ForEach-Object { $x = [regex]::Match($_, '^[0-9a-f]+').Value; "$x`n" } | `
+    Out-File -LiteralPath "$PSScriptRoot/vcpkg-scripts-sha.txt" -Encoding Ascii -NoNewline
diff --git a/vcpkg-init/vcpkg-scripts-sha.txt b/vcpkg-init/vcpkg-scripts-sha.txt
@@ -1 +1 @@
-f6729a3ac3bfdefc999aa8e3664f8014370886b8
+bdd229e13c66fa11acdc0bc8fed8e7474cd24aa5

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	+git ls-remote https://github.com/microsoft/vcpkg master \| `
	`2`	+ ForEach-Object { $x = [regex]::Match($_, '^[0-9a-f]+').Value; "$x`n" } \| `
	`3`	`+ Out-File -LiteralPath "$PSScriptRoot/vcpkg-scripts-sha.txt" -Encoding Ascii -NoNewline`