Skip to content

Packages not following Major.Minor.Revision versioning cannot be pinned to an exact revision #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
oniskanen opened this issue Jul 30, 2019 · 0 comments · Fixed by #478
Labels

Comments

@oniskanen
Copy link

I'm trying to include some data models from the AndroidPublisher package found at https://www.nuget.org/packages/Google.Apis.AndroidPublisher.v3/

Their versioning scheme seems to have four parts, which means the caching in the dependency resolver fails. Here's the line I'm using to introduce the dependency:

#r "nuget: Google.Apis.AndroidPublisher.v3, 1.40.2.1648"

Here's the resulting error:

The script (myscript.csx) is not cacheable. For caching and optimal performance, ensure that the script only contains NuGet references with pinned/exact versions.

Removing the last part of the version (#r "nuget: Google.Apis.AndroidPublisher.v3, 1.40.2") allows me to cache, but my assumption is that this will ignore any later package releases with version 1.40.2.xxxx as soon as it has cached something.

This is probably a minor issue affecting only a handful of packages overall, but I thought that it might be worthwhile bringing to your attention. Enabling a way to force caching for non-standard package versions would be my suggestion for working around the issue. Is there a way to do it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants