Publish an item as unlisted about powershellgallery

[RStadlmair]

Like this as all items are stored forever on the gallery and there should be some programmatic way to show/hide them from the public.
Thx/R.

[SydneyhSmith]

This seems like a very similar ask to https://github.com/PowerShell/PowerShellGallery/issues/17

[seanmcne]

Sort of similar I suppose - it's important to have a way to "pre-deploy" a package that the public can't see so we can do a full test prior to opening it up to the pubic.

A flow of:

• Develop Code / Changes
• Test locally
• Package
• Deploy to ps gallery
• Download
• Test
• Confirm/verify
• Then 'release' so the public can upgrade their module that's been published

This would allow me to fully script & automate the dev / build process right up to publishing as 'hidden' so I can do a final test and push a button to 'release' it to the public.

Hope this makes sense - thanks!

[SydneyhSmith]

Yes, that explanation helps, thanks @seanmcne !

[JustinGrote]

Doesn't deploying modules as prerelease meet this need? I don't see the need for a net-new function.

Typical flow:

1. Publish Module as prerelease
2. If Prerelease module is broken, hide it
3. Publish Release Module
4. If broken release module, "fix forward" by hiding the existing module, publish a hotfix with a 0.0.x version bump, and publish the fixed module.

And before anything gets to the "publish" stage for any of the above, it's passed all your pester tests.

[SteveL-MSFT]

A customer recently brought this up. Basically they publish a set of modules to PSGallery all with the same version. They don't want users to download mixed versions of the modules. Ideally, they would want to publish them unlisted and have a way to flip a set of modules to be listed at once to make them public.