PharoLauncher uses outdated VM in installer

[astares]

In file CI.yml for the GitHub actions the CI automagically downloads:

http://files.pharo.org/get-files/110/pharo-win-stable-signed.zip
(currently from Pharo 11)

when building the Advanced installer. It is downloaded via PowerShell script:

But this signed VM for Windows was built on 30.03.2023 14:26 and is older than a year now:

But also the one from Pharo 12 is having the same build date if you check the date of pharo-win-stable-signed.zip
in http://files.pharo.org/get-files/120/

Meanwhile there have been new releases of Pharo VM as one can see in
https://github.com/pharo-project/pharo-vm/tags

Could we update it so Pharo Launcher installer comes with a more recent Pharo Windows VM?

[astares]

[demarey]

Thank you for the report @astares .
Indeed, the Windows VM is outdated. The one that is shipped is the latest "signed" VM (manual process) but not the latest stable VM.
I will ask to sign the latest Pharo 11 VM and update it.

[astares]

@demarey Great, thank you!