Recaptcha response was not valid. Try again or email support if you need assistance.
after submitting a new message on the Contact Support page. I confirm that all required fields were filled-in, cookies are not disabled; I've tried with Edge, Firefox, Chrome and IE, always the same result.
Txs in advance for your help.
We (the AWS PowerShell Tools team) have hit an issue publishing the AWS modules to the gallery involving a limit of 4000 cmdlets in the CmdletsToExport manifest member. The gallery returns an error when we attempt to publish, which has forced us to revert to using "*-*" in the manifest, which gives a degraded user experience. I inspected the gallery publishing cmdlets and could see no sign of the limit there, so am assuming therefore that this was a gallery-side exception. The limit appears to be isolated to the CmdletsToExport manifest member as we're able to publish the module with the change even though it contains a large number of cmdlets.
We have backlog work queued to break our module into multiple sub-modules. In the meantime we're looking for a fix or workaround that will enable us to re-start publishing our module to the gallery and have all cmdlets listed in the manifest.
Can anyone offer any suggestions or fixes?
A search result list in PowerShell Gallery should have date info on items (last update date, first appearance date).
When an author publishes an update to their module hosted on the gallery it should provide an option to push a notification to their configured social media accounts.
So an author configures Twitter and LinkedIn profiles on their account/profile. A configuration option within the module being published should allow for a setting that will push a notification to their social media, on their behalf, announcing a new release of that module.
We are working to support this, but have no ETA at this time.
PSGallery on the other hand only shows a very small text description and then a bunch of metadata. There is a link "See documentation for more details", but confusingly that doesn't lead to the documentation of the package, it leads to the documentation of the PSGallery in general. To get to the readme on GitHub, you usually have to click the tiny "Project Site" link on the left.
If the package contains a readme.md, that is what should be prominently rendered on the package site. Concerns over embedded content/links can be solved as shown by all the other package registries that do this.
It is currently hard to get notifications when PowerShell modules get updated. It would be nice if there would be an RSS feed for new versions of a package, then my RSS reader could notify me that a new version is available and I could take action.
We are investigating this and have it in our backlog queue.
The priority of the feature will be impacted by the number of votes, which right now is fairly low for this task.
The PowerShell gallery should allow users to create "lists" of modules (think of it as an Amazon wish list).
A user could create a "favorites" list and add modules and scripts to it to keep track of their favorites over time (maybe even "subscribe" to notifications of new releases of things on the list).
But most importantly, users should be able to SHARE those lists, and other users should be able to download and install a list (maybe something like Install-Module -ListName MyPrompt -Author Jaykul).
Additionally, if you could show a count of how many users have added the module to at least one list, and a count of how many lists it's on, these would potentially be useful non-download metrics for popularity.
It would be awesome if there was a way to get additional sorting metrics for the gallery (downloads in the last week, vs. all-time, perhaps), and this would give you several possible additional metrics (users, lists, and the "all time" vs "last month" or "last week" to get hotness).
It would be nice to be able to delete a module that hasn't been downloaded yet and is unlisted. I made a mistake in publishing a module which I unlisted before anyone downloaded it. There is no benefit to me or anyone having it remain in the gallery.
1. Other items may depend on that item. Those items might not necessarily be in this gallery.
2. Ensures that folks using items without committing the same will not be broken.
3. Helps ensure that important community owned items are not mass deleted.
For 1 - nothing depends on this, if someone does download it they're being facetious and just going to be wasting their time.
For 2 - Not sure what this means, but if it has something to do with preventing resubmissions of the same version number, that would actually be good for me since no one has downloaded it yet anyway and I could just publish that version without having to increment it.
For 3 - It's only important if it's been downloaded, but it hasn't yet, so let me delete it.
We understand the ask, & are leaving it as Survey to gauge the interest level.
For now, you can use the Contact Us link to specify the item & version that you want deleted. Specify why you feel that this is something that should not be left in the Gallery, providing more detail is likely to help.
The Gallery operations team will investigate and, if it meets what is actually a very high bar, will delete it.
Specific ask for the voters: If you are willing, please add a note what your expectations are, and how you would see this providing extra value in the Gallery when we display this content.
This type of feature is something we are generally a little bit cautious about.
Rendering active MD content can include links & other items that result in some amount of risk for users of a site.
When posting a link to a GitHub repo on Twitter, the URL is generally replaced with a Twitter summary card. This is not the case, currently, when posting links to items on the Gallery. The display of cards makes these links stand out more and (should) help with social sharing of PowerShell content.
The PowerShell Gallery currently qualifies 'Scripts' by name only. For example, if someone has already published Some-Script, I have no way to publish my own Some-Script, even if the original is related only in name, has major functional differences, etc.
It would be helpful to allow qualifying these. Perhaps resolve by date published first (i.e. compatible with current system), while allowing qualification by username, similar to how GitHub handles this.
Thus, I could install RamblingCookieMonster\Some-Script, even if EvilDoer\Some-Script already existed.
GitHub and npm have badges that can be placed on your repo or elsewhere that can display stats about aspects of your project.
It'd be great to be able to put a badge on a repo showing stats about the published item to PowerShell Gallery, like, number of downloads.
Interesting concept. If you could do us a favor and send a pointer to a specific example, it would be helpful for us.
I would like to know how big a module is before downloading it.
Right now, the UX for enabling / disabling the listing status for PowerShell modules and scripts is a bit challenging, if you have many versions. Could we improve upon this somehow, to enable batch enable / disable of module / script versions?
Thanks for the feedback, understand the request.