From d98e1e6833679a0ca0088109b12d451b88af30f9 Mon Sep 17 00:00:00 2001 From: Dongbo Wang Date: Mon, 18 Sep 2023 17:27:11 -0700 Subject: [PATCH] Update the stable version of PSReadLine used in the auto triage messages (#3804) --- tools/issue-mgmt/CloseDupIssues.ps1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/issue-mgmt/CloseDupIssues.ps1 b/tools/issue-mgmt/CloseDupIssues.ps1 index 65587a733..28dad7d02 100644 --- a/tools/issue-mgmt/CloseDupIssues.ps1 +++ b/tools/issue-mgmt/CloseDupIssues.ps1 @@ -11,7 +11,7 @@ class issue $repo_name = "PowerShell/PSReadLine" $root_url = "https://github.com/PowerShell/PSReadLine/issues" $msg_upgrade = @" -Please upgrade to the [2.2.6 version of PSReadLine](https://www.powershellgallery.com/packages/PSReadLine/2.2.6) from PowerShell Gallery. +Please upgrade to the [2.3.3 version of PSReadLine](https://www.powershellgallery.com/packages/PSReadLine/2.3.3) from PowerShell Gallery. See the [upgrading section](https://github.com/PowerShell/PSReadLine#upgrading) for instructions. Please let us know if you run into the same issue with the latest version. "@ @@ -46,7 +46,7 @@ foreach ($item in $issues) $body -match 'PSReadLine: 2\.2\.0-beta[12]') { $comment = @' -This issue was fixed in 2.2.0-beta3 version of PSReadLine. You can fix this by upgrading to the latest [2.2.6 version of PSReadLine](https://www.powershellgallery.com/packages/PSReadLine/2.2.6). +This issue was fixed in 2.2.0-beta3 version of PSReadLine. You can fix this by upgrading to the latest [2.3.3 version of PSReadLine](https://www.powershellgallery.com/packages/PSReadLine/2.3.3). To upgrade, simply run `Install-Module PSReadLine -AllowPrerelease -Force` from your PowerShell console. --------