You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 13, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/PowerShellGet/PowerShellGet.psd1
+80-80Lines changed: 80 additions & 80 deletions
Original file line number
Diff line number
Diff line change
@@ -1,60 +1,60 @@
1
1
@{
2
-
RootModule='PSModule.psm1'
3
-
ModuleVersion='2.2.5'
4
-
GUID='1d73a601-4a6c-43c5-ba3f-619b18bbb404'
5
-
Author='Microsoft Corporation'
6
-
CompanyName='Microsoft Corporation'
7
-
Copyright='(c) Microsoft Corporation. All rights reserved.'
8
-
Description='PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts.'
Copyright='(c) Microsoft Corporation. All rights reserved.'
8
+
Description='PowerShell module with commands for discovering, installing, updating and publishing the PowerShell artifacts like Modules, DSC Resources, Role Capabilities and Scripts.'
- Default installation scope for Update-Module and Update-Script has changed to match Install-Module and Install-Script. For Windows PowerShell (version 5.1 or below), the default scope is AllUsers when running in an elevated session, and CurrentUser at all other times.
122
-
For PowerShell version 6.0.0 and above, the default installation scope is always CurrentUser. (#421)
122
+
For PowerShell version 6.0.0 and above, the default installation scope is always CurrentUser. (#421)
123
123
124
124
Bug Fixes
125
125
@@ -163,7 +163,7 @@ Bug fixes
163
163
164
164
Breaking Change
165
165
- Default installation scope for Install-Module, Install-Script, and Install-Package has changed. For Windows PowerShell (version 5.1 or below), the default scope is AllUsers when running in an elevated session, and CurrentUser at all other times.
166
-
For PowerShell version 6.0.0 and above, the default installation scope is always CurrentUser.
166
+
For PowerShell version 6.0.0 and above, the default installation scope is always CurrentUser.
167
167
168
168
## 1.6.7
169
169
@@ -190,18 +190,18 @@ Bug fixes
190
190
191
191
New features
192
192
* Allow Pester/PSReadline installation when signed by non-Microsoft certificate (#258)
193
-
- Whitelist installation of non-Microsoft signed Pester and PSReadline over Microsoft signed Pester and PSReadline.
193
+
- Whitelist installation of non-Microsoft signed Pester and PSReadline over Microsoft signed Pester and PSReadline.
194
194
195
195
Build and Code Cleanup Improvements
196
196
* Splitting of functions (#229) (Thanks @Benny1007)
197
-
- Moves private functions into respective private folder.
198
-
- Moves public functions as defined in PSModule.psd1 into respective public folder.
199
-
- Removes all functions from PSModule.psm1 file.
200
-
- Dot sources the functions from PSModule.psm1 file.
201
-
- Uses Export-ModuleMember to export the public functions from PSModule.psm1 file.
197
+
- Moves private functions into respective private folder.
198
+
- Moves public functions as defined in PSModule.psd1 into respective public folder.
199
+
- Removes all functions from PSModule.psm1 file.
200
+
- Dot sources the functions from PSModule.psm1 file.
201
+
- Uses Export-ModuleMember to export the public functions from PSModule.psm1 file.
202
202
203
203
* Add build step to construct a single .psm1 file (#242) (Thanks @Benny1007)
204
-
- Merged public and private functions into one .psm1 file to increase load time performance.
204
+
- Merged public and private functions into one .psm1 file to increase load time performance.
205
205
206
206
Bug fixes
207
207
- Fix null parameter error caused by MinimumVersion in Publish-PackageUtility (#201)
@@ -217,15 +217,15 @@ Bug fixes
217
217
218
218
New features
219
219
* Prerelease Version Support (#185)
220
-
- Implemented prerelease versions functionality in PowerShellGet cmdlets.
221
-
- Enables publishing, discovering, and installing the prerelease versions of modules and scripts from the PowerShell Gallery.
* Enabled publish cmdlets on PWSH and Nano Server (#196)
225
-
- Dotnet command version 2.0.0 or newer should be installed by the user prior to using the publish cmdlets on PWSH and Windows Nano Server.
226
-
- Users can install the dotnet command by following the instructions specified at https://aka.ms/dotnet-install-script.
227
-
- On Windows, users can install the dotnet command by running *Invoke-WebRequest -Uri 'https://dot.net/v1/dotnet-install.ps1' -OutFile '.\dotnet-install.ps1'; & '.\dotnet-install.ps1' -Channel Current -Version '2.0.0'*
228
-
- Publish cmdlets on Windows PowerShell supports using the dotnet command for publishing operations.
225
+
- Dotnet command version 2.0.0 or newer should be installed by the user prior to using the publish cmdlets on PWSH and Windows Nano Server.
226
+
- Users can install the dotnet command by following the instructions specified at https://aka.ms/dotnet-install-script.
227
+
- On Windows, users can install the dotnet command by running *Invoke-WebRequest -Uri 'https://dot.net/v1/dotnet-install.ps1' -OutFile '.\dotnet-install.ps1'; & '.\dotnet-install.ps1' -Channel Current -Version '2.0.0'*
228
+
- Publish cmdlets on Windows PowerShell supports using the dotnet command for publishing operations.
229
229
230
230
Breaking Change
231
231
- PWSH: Changed the installation location of AllUsers scope to the parent of $PSHOME instead of $PSHOME. It is the SHARED_MODULES folder on PWSH.
@@ -239,14 +239,14 @@ Bug fixes
239
239
240
240
New features
241
241
* Added support for modules requiring license acceptance (#150)
0 commit comments