Open daxian-dbw opened 1 year ago
This is perhaps more work than I would expect is needed as a module author to do when renaming a module.
Personally my plan for this would have been
Warning - This module has been renamed to Microsoft.PowerShell.ThreadJob and future enhancements will come under that new module. Please update accordingly as this module will not be available as part of PowerShell 7.6 onwards
ThreadJob
Module on the Gallery (would still allow it to be returned from PowerShellGet
`PSResourceGetas this would then show the
Microsoft.PowerShell.ThreadJobmodule more prominantly. Also discuss can that module be prioritised in search results for
ThreadJob` which I don't think it can be right now. Microsoft.PowerShell.ThreadJob
ProxyModules are great but I personally think use of one in this instance is perhaps more work than needed, though as shown above there is also need for additional work in the gallery and other tooling too (which I'll raise about now)
Prerequisites
Steps to reproduce
Given that the Microsoft.PowerShell.ThreadJob is going to replace the ThreadJob going forward, a proxy module of
ThreadJob
should be released to PowerShell Gallery to point toMicrosoft.PowerShell.ThreadJob
and to warn about deprecation ofThreadJob
.Here is the decision from PowerShell Committe:
Expected behavior
Actual behavior
Error details
No response
Environment data
Version
N/A
Visuals
No response