Feature Request: Publish Module Package-Only

https://github.com/PowerShell/PowerShellGet/blob/e669ac1af1ced7ff33a2cba294cbd859e1c6ba12/srcOld/code/PublishPSResource.cs#L477

The remaining publish to repository after this line should be gated in a switch parameter e.g. -BuildOnly, that if specified instead emits the path to the built .nupkg file rather than publishing to a repository. This is useful if you want to use the nupkg in a different manner, say uploading to Github Artifacts, caching the build result, or other CI/CD driven activities.

Currently with PSGetv2 a workaround has to be done which is publish to a local file repository, this would be much faster and more explicit.

[SydneyhSmith]

Thanks @JustinGrote for Publish-PSResource we plan to add a -DestinationPath parameter (https://github.com/PowerShell/PowerShellGet/blob/0cae3522fae8f723bd9cd01bdeccfaf4f23ab09b/Docs/PublishPSResource.md#-destinationpath) which allows you to publish a nupkg to a local path…would this cover your scenario?

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.