Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
First configuration to resolve determines effective dynamic version cache policy #3019
When a dynamic version is first resolved, that version list cached for the duration of the build. However, if the first configuration to resolve doesn't carry the desired
The individual cache TTL is honored.
The cache TTL of the first configuration to resolve determines the staleness of dynamic dependencies.
When we update dependency locks, we set changing/dynamic caching to
Steps to Reproduce (for bugs)
Note that the first dynamic version lookup indicates
Thanks @DanielThomas for tracking this down.
This is a pretty nasty issue, caused by our in-memory resolution cache not respecting the different cache expiry settings for different configurations.
I hope to have a fix ready for 4.5.