Updates from: 02/17/2021 05:02:57
Service Microsoft Docs article Related commit history on GitHub Change details
PSReadLine https://docs.microsoft.com/en-us/powershell/module/PSReadLine/Set-PSReadLineKeyHandler?view=powershell-5.1 https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/PSReadLine/Set-PSReadLineKeyHandler.md
@@ -3,7 +3,7 @@ external help file: Microsoft.PowerShell.PSReadLine2.dll-Help.xml
keywords: powershell,cmdlet Locale: en-US Module Name: PSReadline Previously updated : 12/07/2018 Last updated : 02/16/2021 online version: https://docs.microsoft.com/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Set-PSReadLineKeyHandler
@@ -86,6 +86,10 @@ the following example:
`Ctrl+X,Ctrl+L`
+> [!NOTE]
+> As of PSReadLine 2.0.0, the **Chord** parameter is **case-sensitive**. Meaning, `Ctrl+X` and
+> `Ctrl+x` will create different bindings.
+ This parameter accepts an array of strings. Each string is a separate binding, not a sequence of keys for a single binding.
PSReadLine https://docs.microsoft.com/en-us/powershell/module/PSReadLine/Set-PSReadLineKeyHandler?view=powershell-7.0 https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/PSReadLine/Set-PSReadLineKeyHandler.md
@@ -3,7 +3,7 @@ external help file: Microsoft.PowerShell.PSReadLine2.dll-Help.xml
keywords: powershell,cmdlet Locale: en-US Module Name: PSReadLine Previously updated : 12/07/2018 Last updated : 02/16/2021 online version: https://docs.microsoft.com/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Set-PSReadLineKeyHandler
@@ -86,6 +86,10 @@ the following example:
`Ctrl+X,Ctrl+L`
+> [!NOTE]
+> As of PSReadLine 2.0.0, the **Chord** parameter is **case-sensitive**. Meaning, `Ctrl+X` and
+> `Ctrl+x` will create different bindings.
+ This parameter accepts an array of strings. Each string is a separate binding, not a sequence of keys for a single binding.
PSReadLine https://docs.microsoft.com/en-us/powershell/module/PSReadLine/Set-PSReadLineKeyHandler?view=powershell-7.1 https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/PSReadLine/Set-PSReadLineKeyHandler.md
@@ -3,7 +3,7 @@ external help file: Microsoft.PowerShell.PSReadLine2.dll-Help.xml
keywords: powershell,cmdlet Locale: en-US Module Name: PSReadLine Previously updated : 12/07/2018 Last updated : 02/16/2021 online version: https://docs.microsoft.com/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Set-PSReadLineKeyHandler
@@ -86,6 +86,10 @@ the following example:
`Ctrl+X,Ctrl+L`
+> [!NOTE]
+> As of PSReadLine 2.0.0, the **Chord** parameter is **case-sensitive**. Meaning, `Ctrl+X` and
+> `Ctrl+x` will create different bindings.
+ This parameter accepts an array of strings. Each string is a separate binding, not a sequence of keys for a single binding.
PSReadLine https://docs.microsoft.com/en-us/powershell/module/PSReadLine/Set-PSReadLineKeyHandler?view=powershell-7.2 https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/PSReadLine/Set-PSReadLineKeyHandler.md
@@ -2,7 +2,7 @@
external help file: Microsoft.PowerShell.PSReadLine2.dll-Help.xml Locale: en-US Module Name: PSReadLine Previously updated : 12/07/2018 Last updated : 02/16/2021 online version: https://docs.microsoft.com/powershell/module/psreadline/set-psreadlinekeyhandler?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: Set-PSReadLineKeyHandler
@@ -85,6 +85,10 @@ the following example:
`Ctrl+X,Ctrl+L`
+> [!NOTE]
+> As of PSReadLine 2.0.0, the **Chord** parameter is **case-sensitive**. Meaning, `Ctrl+X` and
+> `Ctrl+x` will create different bindings.
+ This parameter accepts an array of strings. Each string is a separate binding, not a sequence of keys for a single binding.
developer https://docs.microsoft.com/en-us/powershell/scripting/developer/module/how-to-write-a-powershell-module-manifest https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/developer/module/how-to-write-a-powershell-module-manifest.md
@@ -91,7 +91,7 @@ The following table describes the elements you can include in a module manifest.
|Element|Default|Description| |-|-|--| |**RootModule**<br /> Type: `String`|`<empty string>`|Script module or binary module file associated with this manifest. Previous versions of PowerShell called this element the **ModuleToProcess**.<br /> Possible types for the root module can be empty, which creates a **Manifest** module, the name of a script module (`.psm1`), or the name of a binary module (`.exe` or `.dll`). Placing the name of a module manifest (`.psd1`) or a script file (`.ps1`) in this element causes an error. <br /> Example: `RootModule = 'ScriptModule.psm1'`|
-|**ModuleVersion**<br /> Type: `Version`|`'0.0.1'`|Version number of this module. If a value isn't specified, `New-ModuleManifest` uses the default. The string must be able to convert to the type `Version` for example `#.#.#.#.#`. `Import-Module` loads the first module it finds on the **$PSModulePath** that matches the name, and has at least as high a **ModuleVersion**, as the **MinimumVersion** parameter. To import a specific version, use the `Import-Module` cmdlet's **RequiredVersion** parameter.<br /> Example: `ModuleVersion = '1.0'`|
+|**ModuleVersion**<br /> Type: `Version`|`'0.0.1'`|Version number of this module. If a value isn't specified, `New-ModuleManifest` uses the default. The string must be able to convert to the type `Version` for example `#.#.#.#`. `Import-Module` loads the first module it finds on the **$PSModulePath** that matches the name, and has at least as high a **ModuleVersion**, as the **MinimumVersion** parameter. To import a specific version, use the `Import-Module` cmdlet's **RequiredVersion** parameter.<br /> Example: `ModuleVersion = '1.0'`|
|**GUID**<br /> Type: `GUID`|`'<GUID>'`|ID used to uniquely identify this module. If a value isn't specified, `New-ModuleManifest` autogenerates the value. You can't currently import a module by **GUID**. <br /> Example: `GUID = 'cfc45206-1e49-459d-a8ad-5b571ef94857'`| |**Author**<br /> Type: `String`|`'<Current user>'`|Author of this module. If a value isn't specified, `New-ModuleManifest` uses the current user. <br /> Example: `Author = 'AuthorNameHere'`| |**CompanyName**<br /> Type: `String`|`'Unknown'`|Company or vendor of this module. If a value isn't specified, `New-ModuleManifest` uses the default.<br /> Example: `CompanyName = 'Fabrikam'`|
install https://docs.microsoft.com/en-us/powershell/scripting/install/Installing-PowerShell-Core-on-Linux https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-Core-on-Linux.md
@@ -96,13 +96,13 @@ PowerShell with `sudo apt-get install powershell`.
### Installation via Direct Download - Ubuntu 16.04
-Download the Debian package `powershell_7.1.1-1.ubuntu.16.04_amd64.deb` from the [releases][] page
+Download the Debian package `powershell_7.1.2-1.ubuntu.16.04_amd64.deb` from the [releases][] page
onto the Ubuntu machine. Then, in the terminal, execute the following commands: ```sh
-sudo dpkg -i powershell_7.1.1-1.ubuntu.16.04_amd64.deb
+sudo dpkg -i powershell_7.1.2-1.ubuntu.16.04_amd64.deb
sudo apt-get install -f ```
@@ -148,13 +148,13 @@ PowerShell with `sudo apt-get install powershell`.
### Installation via Direct Download - Ubuntu 18.04
-Download the Debian package `powershell_7.1.1-1.ubuntu.18.04_amd64.deb` from the [releases][] page
+Download the Debian package `powershell_7.1.2-1.ubuntu.18.04_amd64.deb` from the [releases][] page
onto the Ubuntu machine. Then, in the terminal, execute the following commands: ```sh
-sudo dpkg -i powershell_7.1.1-1.ubuntu.18.04_amd64.deb
+sudo dpkg -i powershell_7.1.2-1.ubuntu.18.04_amd64.deb
sudo apt-get install -f ```
@@ -200,13 +200,13 @@ PowerShell with `sudo apt-get install powershell`.
### Installation via Direct Download - Ubuntu 20.04
-Download the Debian package `powershell_7.1.1-1.ubuntu.20.04_amd64.deb` from the [releases][] page
+Download the Debian package `powershell_7.1.2-1.ubuntu.20.04_amd64.deb` from the [releases][] page
onto the Ubuntu machine. Then, in the terminal, execute the following commands: ```sh
-sudo dpkg -i powershell_7.1.1-1.ubuntu.20.04_amd64.deb
+sudo dpkg -i powershell_7.1.2-1.ubuntu.20.04_amd64.deb
sudo apt-get install -f ```
@@ -302,13 +302,13 @@ with `sudo apt-get install powershell`.
### Installation via Direct Download - Debian 9
-Download the Debian package `powershell_7.1.1-1.debian.9_amd64.deb` from the [releases][] page
+Download the Debian package `powershell_7.1.2-1.debian.9_amd64.deb` from the [releases][] page
onto the Debian machine. Then, in the terminal, execute the following commands: ```sh
-sudo dpkg -i powershell_7.1.1-1.debian.9_amd64.deb
+sudo dpkg -i powershell_7.1.2-1.debian.9_amd64.deb
sudo apt-get install -f ```
@@ -348,7 +348,7 @@ pwsh
### Installation via Direct Download - Debian 10
-Download the tar.gz package `powershell-7.1.1-linux-x64.tar.gz` from the [releases][] page
+Download the tar.gz package `powershell-7.1.2-linux-x64.tar.gz` from the [releases][] page
onto the Debian machine. Then, in the terminal, execute the following commands:
@@ -371,7 +371,7 @@ sudo apt-get install -y \
curl # Download the powershell '.tar.gz' archive
-curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-x64.tar.gz -o /tmp/powershell.tar.gz
+curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-x64.tar.gz -o /tmp/powershell.tar.gz
# Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7
@@ -396,7 +396,7 @@ pwsh
### Installation via Direct Download - Alpine 3.9 and 3.10
-Download the tar.gz package `powershell-7.1.1-linux-alpine-x64.tar.gz` from the [releases][] page onto
+Download the tar.gz package `powershell-7.1.2-linux-alpine-x64.tar.gz` from the [releases][] page onto
the Alpine machine. Then, in the terminal, execute the following commands:
@@ -422,7 +422,7 @@ sudo apk -X https://dl-cdn.alpinelinux.org/alpine/edge/main add --no-cache \
lttng-ust # Download the powershell '.tar.gz' archive
-curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-alpine-x64.tar.gz -o /tmp/powershell.tar.gz
+curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-alpine-x64.tar.gz -o /tmp/powershell.tar.gz
# Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7
@@ -466,19 +466,19 @@ with `sudo yum update powershell`.
### Installation via Direct Download - CentOS 7
-Using [CentOS 7][], download the RPM package `powershell-7.1.1-1.rhel.7.x86_64.rpm` from the [releases][]
+Using [CentOS 7][], download the RPM package `powershell-7.1.2-1.rhel.7.x86_64.rpm` from the [releases][]
page onto the CentOS machine. Then, in the terminal, execute the following commands: ```sh
-sudo yum install powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo yum install powershell-7.1.2-1.rhel.7.x86_64.rpm
``` You can install the RPM without the intermediate step of downloading it: ```sh
-sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-1.rhel.7.x86_64.rpm
``` ### Uninstallation - CentOS 7
@@ -512,19 +512,19 @@ with `sudo yum update powershell`.
### Installation via Direct Download - Red Hat Enterprise Linux (RHEL) 7
-Download the RPM package `powershell-7.1.1-1.rhel.7.x86_64.rpm` from the [releases][] page onto
+Download the RPM package `powershell-7.1.2-1.rhel.7.x86_64.rpm` from the [releases][] page onto
the Red Hat Enterprise Linux machine. Then, in the terminal, execute the following commands: ```sh
-sudo yum install powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo yum install powershell-7.1.2-1.rhel.7.x86_64.rpm
``` You can install the RPM without the intermediate step of downloading it: ```sh
-sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo yum install https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-1.rhel.7.x86_64.rpm
``` ### Uninstallation - Red Hat Enterprise Linux (RHEL) 7
@@ -542,7 +542,7 @@ sudo yum remove powershell
zypper update && zypper --non-interactive install curl tar libicu52_1 # Download the powershell '.tar.gz' archive
-curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-x64.tar.gz -o /tmp/powershell.tar.gz
+curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-x64.tar.gz -o /tmp/powershell.tar.gz
# Create the target folder where powershell will be placed mkdir -p /opt/microsoft/powershell/7
@@ -567,7 +567,7 @@ pwsh
zypper update && zypper --non-interactive install curl tar gzip libopenssl1_0_0 libicu60_2 # Download the powershell '.tar.gz' archive
-curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-x64.tar.gz -o /tmp/powershell.tar.gz
+curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-x64.tar.gz -o /tmp/powershell.tar.gz
# Create the target folder where powershell will be placed mkdir -p /opt/microsoft/powershell/7
@@ -626,21 +626,21 @@ pwsh
### Installation via Direct Download - Fedora 28, 29, and 30
-Download the RPM package `powershell-7.1.1-1.rhel.7.x86_64.rpm` from the [releases][] page onto the
+Download the RPM package `powershell-7.1.2-1.rhel.7.x86_64.rpm` from the [releases][] page onto the
Fedora machine. Then, in the terminal, execute the following commands: ```sh sudo dnf install compat-openssl10
-sudo dnf install powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo dnf install powershell-7.1.2-1.rhel.7.x86_64.rpm
``` You can install the RPM without the intermediate step of downloading it: ```sh sudo dnf install compat-openssl10
-sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-1.rhel.7.x86_64.rpm
+sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-1.rhel.7.x86_64.rpm
``` ### Uninstallation - Fedora 28, 29, and 30
@@ -771,13 +771,13 @@ sudo apt-get install '^libssl1.0.[0-9]$' libunwind8 -y
# Download and extract PowerShell # Grab the latest tar.gz
-wget https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-arm32.tar.gz
+wget https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-arm32.tar.gz
# Make folder to put powershell mkdir ~/powershell # Unpack the tar.gz file
-tar -xvf ./powershell-7.1.1-linux-arm32.tar.gz -C ~/powershell
+tar -xvf ./powershell-7.1.2-linux-arm32.tar.gz -C ~/powershell
# Start PowerShell ~/powershell/pwsh
@@ -869,7 +869,7 @@ Linux `tar.gz` archive.
```sh # Download the powershell '.tar.gz' archive
-curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-linux-x64.tar.gz
+curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-linux-x64.tar.gz
# Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7
install https://docs.microsoft.com/en-us/powershell/scripting/install/Installing-PowerShell-Core-on-Windows https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-Core-on-Windows.md
@@ -29,8 +29,8 @@ find the latest [preview][] version. Scroll down to the **Assets** section of th
The MSI file looks like `PowerShell-<version>-win-<os-arch>.msi`. For example: -- `PowerShell-7.1.1-win-x64.msi`-- `PowerShell-7.1.1-win-x86.msi`
+- `PowerShell-7.1.2-win-x64.msi`
+- `PowerShell-7.1.2-win-x86.msi`
Once downloaded, double-click the installer and follow the prompts.
@@ -68,7 +68,7 @@ installation options:
The following example shows how to silently install PowerShell with all the install options enabled. ```powershell
-msiexec.exe /package PowerShell-7.1.1-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1
+msiexec.exe /package PowerShell-7.1.2-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1
``` For a full list of command-line options for `Msiexec.exe`, see
@@ -97,10 +97,10 @@ values are changed for each major release.
PowerShell binary ZIP archives are provided to enable advanced deployment scenarios. Download one of the following ZIP archives from the [releases][releases] page. -- PowerShell-7.1.1-win-x64.zip-- PowerShell-7.1.1-win-x86.zip-- PowerShell-7.1.1-win-arm64.zip-- PowerShell-7.1.1-win-arm32.zip
+- PowerShell-7.1.2-win-x64.zip
+- PowerShell-7.1.2-win-x86.zip
+- PowerShell-7.1.2-win-arm64.zip
+- PowerShell-7.1.2-win-arm32.zip
Depending on how you download the file you may need to unblock the file using the `Unblock-File` cmdlet. Unzip the contents to the location of your choice and run `pwsh.exe` from there. Unlike
@@ -261,8 +261,8 @@ The following commands can be used to install PowerShell using the published `wi
```Output Name Id Version
- PowerShell Microsoft.PowerShell 7.1.1
- PowerShell-Preview Microsoft.PowerShell-Preview 7.1.1-preview.5
+ PowerShell Microsoft.PowerShell 7.1.2
+ PowerShell-Preview Microsoft.PowerShell-Preview 7.1.2-preview.5
``` 1. Install a version of PowerShell using the `--exact` parameter
install https://docs.microsoft.com/en-us/powershell/scripting/install/Installing-PowerShell-Core-on-macOS https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-Core-on-macOS.md
@@ -118,13 +118,13 @@ brew upgrade powershell
## Installation via Direct Download
-Download the PKG package `powershell-7.1.1-osx-x64.pkg` from the [releases][] page onto your
+Download the PKG package `powershell-7.1.2-osx-x64.pkg` from the [releases][] page onto your
macOS machine. You can double-click the file and follow the prompts, or install it from the terminal: ```sh
-sudo installer -pkg powershell-7.1.1-osx-x64.pkg -target /
+sudo installer -pkg powershell-7.1.2-osx-x64.pkg -target /
``` Install [OpenSSL](#installing-dependencies). OpenSSL is needed for PowerShell remoting and CIM
@@ -159,19 +159,19 @@ operations.
```sh # Download the powershell '.tar.gz' archive
-curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.1.1/powershell-7.1.1-osx-x64.tar.gz
+curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.1.2/powershell-7.1.2-osx-x64.tar.gz
# Create the target folder where powershell will be placed
-sudo mkdir -p /usr/local/microsoft/powershell/7.1.1
+sudo mkdir -p /usr/local/microsoft/powershell/7.1.2
# Expand powershell to the target folder
-sudo tar zxf /tmp/powershell.tar.gz -C /usr/local/microsoft/powershell/7.1.1
+sudo tar zxf /tmp/powershell.tar.gz -C /usr/local/microsoft/powershell/7.1.2
# Set execute permissions
-sudo chmod +x /usr/local/microsoft/powershell/7.1.1/pwsh
+sudo chmod +x /usr/local/microsoft/powershell/7.1.2/pwsh
# Create the symbolic link that points to pwsh
-sudo ln -s /usr/local/microsoft/powershell/7.1.1/pwsh /usr/local/bin/pwsh
+sudo ln -s /usr/local/microsoft/powershell/7.1.2/pwsh /usr/local/bin/pwsh
``` ## Installing dependencies
@@ -224,7 +224,7 @@ and remove the paths using `sudo rm`.
## Paths -- `$PSHOME` is `/usr/local/microsoft/powershell/7.1.1/`
+- `$PSHOME` is `/usr/local/microsoft/powershell/7.1.2/`
- User profiles will be read from `~/.config/powershell/profile.ps1` - Default profiles will be read from `$PSHOME/profile.ps1` - User modules will be read from `~/.local/share/powershell/Modules`
@@ -238,7 +238,7 @@ exists at `Microsoft.PowerShell_profile.ps1` in the same locations.
PowerShell respects the [XDG Base Directory Specification][xdg-bds] on macOS. Because macOS is a derivation of BSD, the prefix `/usr/local` is used instead of `/opt`. So,
-`$PSHOME` is `/usr/local/microsoft/powershell/7.1.1/`, and the symbolic link is placed at
+`$PSHOME` is `/usr/local/microsoft/powershell/7.1.2/`, and the symbolic link is placed at
`/usr/local/bin/pwsh`. ## Installation support