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 first restore-key has the same value as the actual key and could therefore be removed. The second value find the lastest created, but considering the pubspec.lock files.
The cache with the most recent creation date would be used.
When using the default configuration for
pub-cache-key: "flutter-pub:os:-:channel:-:version:-:arch:-:hash:"
that action returns unexpected old caches.The setup of the actions/cache@v4 enables this with:
the first
restore-key
has the same value as the actualkey
and could therefore be removed. The second value find the lastest created, but considering thepubspec.lock
files.according to: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#matching-a-cache-key
My suggestion is to remove those
restore-keys
to make the caching behaviour more predictable.The text was updated successfully, but these errors were encountered: