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
|`cache-key`| The cache key from `create-and-cache`| Yes |
72
72
73
73
> [!NOTE]
74
74
> The cache key includes the current date, so the lock file is regenerated daily.
@@ -83,6 +83,7 @@ When developing and testing _library_ code, we don't want our environments to st
83
83
The _easiest_ way to test against the latest versions of packages - and avoid the noisy commit history (and additional overhead) of regularly updating a lock file in git - is instead to ignore the lock file and rely on developers and CI to generate their own lock files. This much simpler setup forgoes perfect reprodubility between developer machines, and with CI machines - which may be a worthwhile tradeoff for your project.
84
84
85
85
See the following threads for more detailed discussion:
86
+
86
87
-[prefix.dev Discord: Should you commit the lockfile](https://discord.com/channels/1082332781146800168/1462778624212996209)
87
88
-[Scientific Python Discord: lock files for libraries](https://discord.com/channels/786703927705862175/1450619697224487083)
0 commit comments