| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
windows-2025 will use Windows Server 2025 with Visual Studio 2026 image in June 2026:
We're now almost a week past 15th, so pulling in main to try out ... |
Sorry, something went wrong.
|
Could you explain the motivation? Are they sunsetting this runner label? If not, I don't see why what we have now needs to change. |
Sorry, something went wrong.
|
See the links given in the issue. I don't know whether the label windows-2025-vs2026 will ever be sunset, though. If it stays, then this PR can be closed ofc ... |
Sorry, something went wrong.
|
windows-2025-vs2026 was a preview, if it is now official and kept forever, we can keep it. |
Sorry, something went wrong.
There was a problem hiding this comment.
The announcement made it clear the old windows-2025-vs2026 label is for testing only:
Note: This label is meant for testing only. After the migration, this label will point to the windows-2025 image.
It may or may not go away, but let's use windows-2025 instead of the testing-only windows-2025-vs2026.
Sorry, something went wrong.
|
Thanks @chris-eibl for the PR 🌮🎉.. I'm working now to backport this PR to: 3.15. |
Sorry, something went wrong.
|
GH-151939 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
Alright, then. Though, I'd prefer the specific label if it's kept since it is clearer about the runtime and is probably more likely to be immutable. |
Sorry, something went wrong.
use windows-2025 in GitHub Actions
| Back | FazBrowse Home | New Git URL |
Marking as draft until we really want to switch in mid-June.