Skip to content

Conversation

@lbonsey1
Copy link
Contributor

As mentioned in open issue #319, the restore-keys specified within action.yaml leads to some unpredictable behaviour; a pub get cache-miss could result in a different hashed lock cache to be returned instead. In our experience, this has caused pipelines to fail, as the codebase is relying on packages which are not present in the pub cache. As @rolandmosimann recommends, I feel this behaviour should be removed, to fix this problem.

As a result, this PR removes the misleading restore-key on pub get caching, as well as the unnecessary declaration of a restore-key matching exactly the key. Let me know if you've got any questions 😄

@lbonsey1 lbonsey1 changed the title fix: remove restore keys Remove misleading restore-keys from caching Feb 20, 2025
@lbonsey1 lbonsey1 changed the title Remove misleading restore-keys from caching Remove restore-keys from caching Feb 20, 2025
@alexdempster44
Copy link

@bartekpacia could you have a look at this please? It would be nice to get it merged in.

sophie-maney added a commit to FurryApp/flutter-action that referenced this pull request Mar 13, 2025
@bartekpacia bartekpacia merged commit 1177d93 into subosito:main Mar 24, 2025
81 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants