You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version as specified in go-version is used verbatim in the cache key. If I specify 1.18.x it may first resolve to 1.18.6 and later to 1.18.7. However, if I store a build cache on 1.18.6 it is not usable for 1.18.7.
Action version:
v3
Platform:
Ubuntu
macOS
Windows
Runner type:
Hosted
Self-hosted
Tools version:
1.18.x
Repro steps:
Run a nightly action with 1.18.x and observe the build times go up once a new patch version of Go is released.
Expected behavior:
I would expect the cache key to change and a new build to upload a new cache entry.
Actual behavior:
The cache key interpolates 1.18.x and the cache isn't used when a new patch version is released.
The text was updated successfully, but these errors were encountered:
Description:
The version as specified in
go-version
is used verbatim in the cache key. If I specify1.18.x
it may first resolve to1.18.6
and later to1.18.7
. However, if I store a build cache on1.18.6
it is not usable for1.18.7
.Action version:
v3
Platform:
Runner type:
Tools version:
1.18.x
Repro steps:
Run a nightly action with
1.18.x
and observe the build times go up once a new patch version of Go is released.Expected behavior:
I would expect the cache key to change and a new build to upload a new cache entry.
Actual behavior:
The cache key interpolates
1.18.x
and the cache isn't used when a new patch version is released.The text was updated successfully, but these errors were encountered: