New
#1
General Cmdlet Updates and Fixes
- Revert "Adjust PUT method behavior to POST one for default content type in WebCmdlets" (#21049)
- Fix regression with Get-Content when -Tail 0 and -Wait are both used (#20734) (Thanks @CarloToso!)
- Fix Get-Error serialization of array values (#21085) (Thanks @jborean93!)
- Fix a regression in Format-Table when header label is empty (#21156)
Engine Updates and Fixes
- Revert the PR #17856 (Do not preserve temporary results when no need to do so) (#21368)
- Make sure the assembly/library resolvers are registered at early stage (#21361)
- Handle the case that Runspace.DefaultRunspace is null when logging for WDAC Audit (#21344)
- Fix PowerShell class to support deriving from an abstract class with abstract properties (#21331)
- Fix the regression when doing type inference for $_ (#21223) (Thanks @MartinGC94!)
Build and Packaging Improvements
Bump to .NET 8.0.4
- Revert analyzer package back to stable
- Update SDK, deps and cgmanifest for 7.4.2
- Revert changes to packaging.psm1
- Update PSResourceGet version from 1.0.2 to 1.0.4.1 (#21439)
- Verify environment variable for OneBranch before we try to copy (#21441)
- Remove surrogateFile setting of APIScan (#21238)
- Add dotenv install as latest version does not work with current Ruby version (#21239)
- Multiple fixes in official build pipeline (#21408)
- Add back 2 transitive dependency packages (#21415)
- Update PSReadLine to v2.3.5 for the next v7.4.x servicing release (#21414)
- PowerShell co-ordinated build OneBranch pipeline (#21364)
Source: https://github.com/PowerShell/PowerS...ses/tag/v7.4.2
Build and Packaging Improvements
Bump to .NET 7.0.18
- Update SDK, dependencies and cgmanifest for 7.3.12
- Revert changes to packaging.psm1
- Verify environment variable for OneBranch before we try to copy (#21441)
- Multiple fixes in official build pipeline (#21408)
- PowerShell co-ordinated build OneBranch pipeline (#21364)
- Add dotenv install as latest version does not work with current Ruby version (#21239)
- Remove surrogateFile setting of APIScan (#21238)
Source: https://github.com/PowerShell/PowerS...es/tag/v7.3.12
Build and Packaging Improvements
Bump to .NET 6.0.29
- Allow artifacts produced by partially successful builds to be consumed by release pipeline
- Update SDK, dependencies and cgmanifest for 7.2.19
- Revert changes to packaging.psm1
- Verify environment variable for OneBranch before we try to copy (#21441)
- Multiple fixes in official build pipeline (#21408)
- Add dotenv install as latest version does not work with current Ruby version (#21239)
- PowerShell co-ordinated build OneBranch pipeline (#21364)
- Remove surrogateFile setting of APIScan (#21238)
Source: https://github.com/PowerShell/PowerS...es/tag/v7.2.19
I think what we need are far more versions of PowerShell to muddy the waters even further.
I noticed something odd after downloading and installing this version last night. In yesterday's (04/12/2024) version of the PowerShell 7.4.2 release notes, they said that PSReadLine (the module that gives bash-like command-line editing) had been updated to 2.3.5. But when I did a Get-InstalledModule command, it told me the version was 2.3.4. So I went to the PowerShell Gallery and found the command to install it was
I did this from an admin-level PowerShell instance. But it refused to install, saying that 2.3.5 was already installed (even though it reported 2.3.4 being the installed version). The error message suggested to use the -Force parameter. I tried that, but it gave me a different error message and still didn't install.Code:Install-Module -Name PSReadLine -RequiredVersion 2.3.5
So I went to this Microsoft page, and found the command:
That worked! I guess the -AllowClobber did the trick.Code:Install-Module -Name PSReadLine -AllowClobber -Force
But here's a weird thing. I just now went to the PowerShell 7.4.2 release notes again, and all references to PSReadLine 2.3.5 had been removed, with no notice I could find that anything had changed.
Very strange all the way around.
- - - Updated - - -
My bad on that one. I just now looked at the GitHub release notes again, and under "Build and Packaging Improvements" there is a triangle I had to click to show the hidden text expanded under it. It says:
It still doesn't explain why Get-InstalledModule originally showed PSReadLine 2.3.4 after the install. Also, when I installed PowerShell 7.4.2 on my laptop, PSReadLine showed as 2.2.6.Update PSReadLine to v2.3.5 for the next v7.4.x servicing release
All three of my machines are updated to PowerShell 7.4.2 now, including PSReadLine 2.3.5, thanks to the command from Microsoft:
Code:Install-Module -Name PSReadLine -AllowClobber -Force
Last edited by andyc56; 4 Weeks Ago at 16:02.