Native package reference nuget: can I avoid changing all my csprojs on every package update?

I've created a "storehouse of the gods" (let's call it G) that concentrates the key functionality used by other parts of my application.

Since this repo is critical and is split across several other components, I want to keep it isolated.

This repository builds a nuget package that is referenced by other solutions (in other repositories X, Y, Z) and which version is automatically incremented on my build server.

Since G is still in its early stages of development (not fully stable), it changes a lot.

My problem: . In this case, I have to update dozens of .csprojs in X, Y, Z every time a patch is placed in G.

My question is: Is there a way to avoid changing csprojs (and packages.config) to update the link? (for example, to tell nuget that I want to reference the "latest" version of this package) ... I guess this will result in a HintPath that doesn't include the package version.

Has anyone experienced a scenario like this? Any workaround?