When a client request a binary, k6build returns the version of the dependencies in the artifact's metadata. These versions are determined when resolving the dependencies and are not saved along the artifact in the cache.
After the changes introduced in https://github.com/grafana/k6build/pull/47 the k6 version reported for a pre-release version are inconsistent across multiple request for building a binary.
The first time, when the artifact is created it is reported using a full semantic version
When a client request a binary,
k6build
returns the version of the dependencies in the artifact's metadata. These versions are determined when resolving the dependencies and are not saved along the artifact in the cache.After the changes introduced in https://github.com/grafana/k6build/pull/47 the k6 version reported for a pre-release version are inconsistent across multiple request for building a binary.
The first time, when the artifact is created it is reported using a full semantic version
In subsequent requests, when the pre-build artifact is returned only the hash is reported: