Open lverns opened 5 years ago
Ah cool, thanks for reporting, we'll see what xsc thinks I guess. I hope it's not causing too many issues for you!
This one will still be around in v2.0.0
I guess since it's probably to do with some deeper issues in dependencies :thinking:
Another example is netty-all
(https://mvnrepository.com/artifact/io.netty/netty-all):
| Dependency | Current | Latest |
|-------------------------------------+--------------+--------------|
| io.netty/netty-all | 4.1.34.Final | 5.0.0.Alpha2 |
Are there any workarounds how to ignore particular versions (like 5.0.0.Alpha2
in case of netty), but still update to latest 4.1.xx.Final
?
io.netty/netty-transport {:mvn/version "4.1.51.Final"} -> {:mvn/version "5.0.0.Alpha2"}
io.netty/netty-transport-native-epoll {:mvn/version "4.1.51.Final"} -> {:mvn/version "5.0.0.Alpha2"}
io.netty/netty-transport-native-kqueue {:mvn/version "4.1.51.Final"} -> {:mvn/version "4.1.52.Final"}
io.netty/netty-codec {:mvn/version "4.1.51.Final"} -> {:mvn/version "5.0.0.Alpha2"}
io.netty/netty-handler {:mvn/version "4.1.51.Final"} -> {:mvn/version "5.0.0.Alpha2"}
I believe this to be an upstream bug.