Windows image version changes every run

[BotellaA]

Description

Between my builds, the windows-2022 image does not have a consistent version number.

My cache with cmake and python is always broken because we keep changing versions... Can you stabilize this? This issue is here for over a week now.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

Sometimes it is the latest: https://github.com/Geode-solutions/OpenGeode/actions/runs/15838001853/job/44645420430#step:1:9
Sometimes the old one: https://github.com/Geode-solutions/OpenGeode/actions/runs/15855272643/job/44700361779#step:1:15

Is it regression?

Previous version was ok 20250602.1.0

Expected behavior

Always having the latest image for every runs

Actual behavior

Switching between latest and previous image.

Repro steps

Run a build with windows-2022 image

[vidyasagarnimmagaddi]

Hi @BotellaA ,Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.

[BotellaA]

@vidyasagarnimmagaddi any update? We cannot build any code now...

[Prabhatkumar59]

Hi @BotellaA - Thanks for follow up!
Once this week’s deployment is complete, the latest image version will begin rolling out. We will update you when the new version is available, after which you can update your sync process accordingly and try using it.

In meantime, Could you please share the repro steps or workflow links where you are facing the issue. It will help us debug the problem more effectively. Thanks!

[Prabhatkumar59]

Hi @BotellaA - The latest Windows image version has been rolled out. Please update your sync process, recheck your code and try using the new version. Let us know if you encounter any further issues. Thanks!

[Prabhatkumar59]

Hi @BotellaA - Since we haven't heard back, we'll assume your issue is resolved with latest roll out version and will close this issue for now. Feel free to reach out to us for any other queries.
Thanks!