PowerShell Universal - 5.5.4

PowerShell Universal releases
1

PowerShell Universal - 5.5.4

Release Notes

Features

Bug Fixes

Admin Console

  • Improved editor IntelliSense consistency and Help performance
  • Fixed an issue with the permissions on the module editor page

Apps

  • Fixed an issue preventing New-UDGridLayout from displaying properly
  • Fixed an issue with Invoke-UDJavaScript throwing exceptions in certain scenarios

Automation

  • Fixed configuration issues with scripts and schedules
  • Fixed PSModulePath inheritance for run as sessions in certain configurations

Platform

  • Fixed a database locking issue and improved some slow queries
  • Fixed some issues running PSU on Linux and in Docker

Downloads

1 Like
2

I’m not sure if I’ve asked this before or if anyone else has but, would it be possible to include GitHub issue numbers in release notes so we have context around each item? I know the product isn’t open-sourced and we have no way to see the actual code change(s), but at least context of what the complaint was that led to something being changed may be helpful to see.

3

The Full Changelog has each item, and the docs page has a list of each item. The above is just a summary.

Items without GitHub IDs were either internally sourced or some support cases.

1 Like
4

That’s true. Thanks.

1 Like
5

@adam, I don’t see that New-UDAutocomplete is included in the changelogs but do see it fixed on the issues tracker for this version for the issue I raised using the static option (not New-UDAutocompleOptions). I’m finding populating it now works but is slow on large data loads.

I load about 4000 options and on 5.5.2 this would populate in about 1 second.
When working around the issue in 5.5.3 and using New-UDAutocompleteOptions, it still loaded quickly.

I’m finding it is taking 18 seconds to populate on 5.5.4 using either static options or New-UDAutocompleteOptions.

1 Like
6

@dbytes Bummer. I’ll open an issue for it. Not sure why but likely a larger JSON payload or something causing some bad client side rendering or something.