The reason is due to how zwift has changed the way they set the current version number.
Pre 1.48.0 there was a file Zwift_ver_cur.xml where we could fetch the version number, now however they have two files.
Zwift_ver_cur_filename.txt which points to the actual version file.
Zwift_ver_cur.120544.xml which seems to contain somewhat the same format as Zwift_ver_cur.xml used to contain. The difference being that they now include which seems to be a git hash in the version number. Not sure if we need to handle this, so ignoring for now.
This will however mean that we need to build zwift from scratch again as we need to update the entrypoint script.
A better option would be for the zwift update github action to include the latest entrypoint script if it's different.
The reason is due to how zwift has changed the way they set the current version number.
Pre 1.48.0 there was a file Zwift_ver_cur.xml where we could fetch the version number, now however they have two files.
Zwift_ver_cur_filename.txtwhich points to the actual version file.Zwift_ver_cur.120544.xmlwhich seems to contain somewhat the same format asZwift_ver_cur.xmlused to contain. The difference being that they now include which seems to be a git hash in the version number. Not sure if we need to handle this, so ignoring for now.This will however mean that we need to build zwift from scratch again as we need to update the entrypoint script.
A better option would be for the zwift update github action to include the latest entrypoint script if it's different.