Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specifying "5.0" should not resolve "5.2.4"

See original GitHub issue

It should resolve 5.0.3 IMO.

If I wanted to get 5.2.4 I would specify 5 not 5.0

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

mxclcommented, Jul 26, 2020

Yeah that makes sense.

0reactions

fwalcommented, Jul 26, 2020

I see, please beware that unquoted version numbers with a single decimal will be interpreted by yaml as a float e.g. “5”

Top Results From Across the Web

.NET Core: Could not load file or assembly 'System.Runtime ...

This seems very similar to Issue 150 and Issue 139 but I could not solve the problem by removing dependencies to my shared...

NuGet Warning NU1605 - Microsoft Learn

Issue. A dependency package specified a version constraint on a higher version of a package than restore ultimately resolved. That is because of ......

Module compiled with Swift 5.1 cannot be imported by the ...

If I build the framework using Xcode 11.2 then it does compile on Xcode 11.2 but it will not compile on 11.1 or...

Part 5 - Publicizing Contract Actions | Acquisition.GOV

(b) The contracting officer must establish a solicitation response time that will afford potential offerors a reasonable opportunity to respond ...

Addressed Issues in GlobalProtect App 5.2 - Palo Alto Networks

Fixed an issue where the GlobalProtect app could not connect to the Prisma Access gateway when a FQDN was used instead of an...