Problem while checking for existing npm releases using private Github npm registry

[vladucu]

In a pnpm mono-repository using private Github npm registry, unless the .npmrc file with the registry & auth config is inside the actual package release-plan will get a 403 trying to check for the latest release and ultimately result in the Github action reporting a failure.
NOTE publishing does go through.

Not really sure if this should be considered a bug or just better documented. I guess, I expected for this to behave like pnpm treats .npmrc file and packages in the workspace to inherit root-level one.