[doc] Updating Windows-2025 image as windows-latest#12925
Merged
Merged
Conversation
kishorekumar-anchala
marked this pull request as ready for review
September 3, 2025 09:19
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the GitHub Actions runner image documentation to reflect that windows-latest now points to Windows Server 2025 instead of Windows Server 2022, aligning with the runner image updates described in the related GitHub issue.
- Updated Windows Server 2025 entry to include
windows-latestalias - Removed
windows-latestalias from Windows Server 2022 entry
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
erik-bershel
previously approved these changes
Oct 1, 2025
Alexey-Ayupov
approved these changes
Oct 1, 2025
EliahKagan
added a commit
to GitoxideLabs/gitoxide
that referenced
this pull request
Jan 3, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in #1515. See #1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this pull request
Jan 3, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in GitoxideLabs#1515. See GitoxideLabs#1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to GitoxideLabs/gitoxide
that referenced
this pull request
Jan 3, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in #1515. See #1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this pull request
Jan 4, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in GitoxideLabs#1515. See GitoxideLabs#1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this pull request
Jan 4, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in GitoxideLabs#1515. See GitoxideLabs#1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this pull request
Jan 4, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in GitoxideLabs#1515. See GitoxideLabs#1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to EliahKagan/gitoxide
that referenced
this pull request
Jan 4, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in GitoxideLabs#1515. See GitoxideLabs#1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
EliahKagan
added a commit
to GitoxideLabs/gitoxide
that referenced
this pull request
Jan 4, 2026
Having recently edited the MSRV workflow, this is as good a time as any to make this change, which is arguably overdue since 2025 has been `windows-latest` for months now: - actions/runner-images#12677 - actions/runner-images#12925 We last updated this in #1515. See #1514 on why we're not using the `windows-latest` label itself in the `msrv` job.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Updating Windows-2025 image as windows-latest
Related issue:
#12677
Check list