Since (about) October 2024 all builds in the 'Available builds' dropdown show as 'Unavailable':
If you attempt an update, there is an immediate error message:
After investigation, it appears that builds are now labelled with a different pattern.
Instead of being called things like '...windows-tiles-x64...' they are now '...windows-with-graphics-and-sounds-x64...' (and similarly for the x32 builds). This change means that the regular expression used to locate the correct build within each release fails.
It turns out these patterns are conveniently parameterized in 'constants.py', so we just need to update that.
Testing
After the change, the builds are now available.
The update process also works again.
Alternative solutions
There are also '...windows-with-graphics-x64...' (ie no sounds) builds.
I don't use sounds so I don't know if they get addressed separately - presumably the no sounds build is a smaller download so would be preferred if the sounds are not required.
Since (about) October 2024 all builds in the 'Available builds' dropdown show as 'Unavailable':
If you attempt an update, there is an immediate error message:
After investigation, it appears that builds are now labelled with a different pattern. Instead of being called things like '...windows-tiles-x64...' they are now '...windows-with-graphics-and-sounds-x64...' (and similarly for the x32 builds). This change means that the regular expression used to locate the correct build within each release fails.
It turns out these patterns are conveniently parameterized in 'constants.py', so we just need to update that.
Testing
After the change, the builds are now available.
The update process also works again.
Alternative solutions
There are also '...windows-with-graphics-x64...' (ie no sounds) builds. I don't use sounds so I don't know if they get addressed separately - presumably the no sounds build is a smaller download so would be preferred if the sounds are not required.