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.

csq pack package name not same as provided version

See original GitHub issue

Using:

Clowd.Squirrel v3.0.210-g5f9f594 csq v3.0.210-g5f9f594

To reproduce:

When calling: dotnet csq.dll pack --packId My.App --packVersion 0.1.0-myFeature.1+29 --packDirectory <publishFolder> --csq-sln=<solutionPath> Output package name will be My.App-0.1.0-myFeature.1-full.nupkg

Issue/Question:

EDIT: I believe there is a bug excluding the build number part of the semantic version +29 (version inside the package is the same as provided: 0.1.0-myFeature.1+29)

Issue Analytics

State:
Created 9 months ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

caesaycommented, Jan 4, 2023

I will have a look at this and see what I can come up with. The kind of compatibility I’m looking to preserve is when an installed app is updating from Squirrel.Windows to Clowd.Squirrel, so the packages that Clowd.Squirrel produce need to still be mostly compatible, and new features will ideally be ignored by Squirrel.Windows (and even older versions of Clowd.Squirrel)

1reaction

caesaycommented, Jan 3, 2023

Thanks for the feedback, I’ll have a look