Do we control the PSReadLine psd1? I noticed trying it with my compatibility checking prototype that it also doesn't have this field 😱

@rjmholt That needs to be addressed in the PSReadLine repo. However, since PSReadLine supports PSv3 and higher which doesn't understand the CompatiblePSEditions property, we can't add it.

Also, given that the modules have been changing in sync with PowerShell and that PowerShell is now version 6.1, should the PowerShellVersion field be 6.1?

It's unlikely that someone would even manage to get to the point where loading old PowerShell modules into a newer version is possible, but it's conceivable, and in principle should be protected against maybe?

@SteveL-MSFT New PSReadLine will only support v5+ right? So that can have the field? But I'm assuming that until then, or in cases using older PSReadLine versions, we take advantage of implicit compatibility due to path location?

@rjmholt regarding PowerShellVersion, yes it would be more accurate to set it to 6.1. As for PSReadLine, I think even 2.0.0 still supports v3, not sure. I would suggest following up on the PSReadLine repo.

@rjmholt @SteveL-MSFT Your comments were addressed, please take another look when you have time. Thanks!

@SteveL-MSFT Looks like PSReadLine 2.0 is now v5+: https://github.com/lzybkr/PSReadLine/blob/46960b1fe442024923381eedd1c9100ded30d123/PSReadLine/Changes.txt#L32

I'll open an issue to update the PSD1