Wrong dependency on CacheTower 1.0.0
See original GitHub issueWhat does the bug do?
Prevents installation of CacheTower.Providers.Redis
(and maybe others).
How can it be reproduced?
Install CacheTower.Providers.Redis
version 0.10.0
. It has declared dependency on CacheTower
version 1.0.0
which doesn’t exist. So, it fails with error:
error NU1102: Unable to find package CacheTower with version (>= 1.0.0)
Environment
- NuGet Package Version: 0.10.0
- .NET Runtime Version: .NET 5.0.302
- Operating System: Windows
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
caching node_modules and wrong dependency version
Seems like an odd issue with npm's dependency resolution. It's probably best to just remove the existing cache and create a new one....
Read more >Maven: Incorrect (and flaky) transitive dependency version
Dependency mediation - this determines what version of a dependency will be used when multiple versions of an artifact are encountered.
Read more >Tell gradle not to cache snapshot dependencies ...
Hi gradle team and users, I'm running Gradle 3.0 with JFrog Artifactory. I use the ArtifactoryPlugin and DependencyManagement plugin, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Version 0.11.0 released that has the package reference issue fixed! Sorry for the hassle with that!
Interestingly the 0.9.0 packages such as redis provider etc, seem to be tightly bound to the 0.9.0 core package of CacheTower.
I have tried to get 0.10.0 core working with the 0.9.0 provider/extensions providers, and everything looks right in the deps.json but I get a runtime failure when the provider package is loaded.
I will await your next release, as it is probably easier, but I have tried the various tricks to force bindings to a specific version (obvs binding redirects are a .NET Framework only thing), but I haven’t managed to get it to load