Skip to content

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

Closed
@oniskanen

Description

@oniskanen

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions