Am 05.12.2024 um 14:04 schrieb Guillermo Polito <guillermopolito@gmail.com>:
Le 5 déc. 2024 à 1:49â¯PM, Guillermo Polito <guillermopolito@gmail.com> a écrit :
Just to be sure. In that case it would be nice to have a way to download precisely 10.3.1 in order to stay safe and we have time to plan countermeasure.
If you want to control what you download, right now the safest way is to go to files.pharo.org <http://files.pharo.org/>, more precisely to https://files.pharo.org/vm/pharo-spur64/, and look for your architecture.
There you will find the archives with the binaries we built. Details about naming conventions are found here: https://github.com/pharo-project/pharo-vm/wiki/About-Build-and-Artifacts
That file server stores both released artifacts and intermediate build results. The released artifact is the first artifact with the corresponding version tag (e.g., 10.3.1, 10.2.0). This is generally the oldest in timestime, but you can confirm with the tags on github.
Also, we improved the artifact naming to include also: - suffixes (alpha, RC, SNAPSHOT) - the distance to the released tag in the format [+x] where x is the commits.
perfect. We use git describe | sed -e 's/\-\([0-9][0-9]*\)\-.*/.\1/' for that.
https://github.com/pharo-project/pharo-vm/pull/870
We have tested this in the dev branch, Iâll backport this in the stable branch. This will allow us to clearly identify the release commit (the one without the +x tag in the name).
super! Thank you for the good work!! Norbert
G