Commit c5d3793
committed
Use runner-provided Git for Windows now that it's 2.49.0
Because GitoxideLabs#1849 (git-for-windows/git#5436)
caused some incorrect test failures in `test-fixtures-windows`, we
have been upgrading Git for Windows on the runner for that job:
- We starting doing that in of 4237e5a (GitoxideLabs#1870). At that time, we
upgraded it to the most recent tag, to select the latest release
even though it was a release candiate, because Git for Windows
2.49.0 had not yet had a stable release.
- Then Git for Windows 2.49.0 got a stable release, and starting in
ddef6d3 (GitoxideLabs#1892) we have upgraded to the release marked "latest"
(which in Git for Windows is always the latest stable release).
More recently, the Windows Server 2022 runner image (which the
`windows-latest` label we use currently selects) has upgraded its
Git for Windows installation from 2.48.1 to 2.49.0:
https://github.com/actions/runner-images/releases/tag/win22%2F20250330.1
It is therefore no longer necessary for the `test-fixtures-windows`
job to upgrade Git for Windows on the runner. This removes the step
that did that. (Either version of the step could be brought back
from the history if ever needed again.)
This closes GitoxideLabs#1849, per the plan in:
GitoxideLabs#1849 (comment)1 parent 420e730 commit c5d3793
1 file changed
+0
-29
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
191 | 191 | | |
192 | 192 | | |
193 | 193 | | |
194 | | - | |
195 | | - | |
196 | | - | |
197 | | - | |
198 | | - | |
199 | | - | |
200 | | - | |
201 | | - | |
202 | | - | |
203 | | - | |
204 | | - | |
205 | | - | |
206 | | - | |
207 | | - | |
208 | | - | |
209 | | - | |
210 | | - | |
211 | | - | |
212 | | - | |
213 | | - | |
214 | | - | |
215 | | - | |
216 | | - | |
217 | | - | |
218 | | - | |
219 | | - | |
220 | | - | |
221 | | - | |
222 | | - | |
223 | 194 | | |
224 | 195 | | |
225 | 196 | | |
| |||
0 commit comments