update from core:base18 to core:base20 #88
Conversation
|
|
||
| adopt-info: powershell | ||
| base: core18 | ||
| base: core20 |
There was a problem hiding this comment.
As mentioned in https://github.com/PowerShell/PowerShell-Snap/issues/87#issuecomment-1216799996 it might be advisable to skip core20 and jump directly to core22.
There was a problem hiding this comment.
Thanks for the thorough explanation of the benefits of upgrading to core22. I'll discuss this with the team.
There was a problem hiding this comment.
The guidance we've received is that core20 is the recommended version right now as it the most stable release. We'll update to core20 first and then can evaluate core22 as needed.
|
|
||
| adopt-info: powershell-preview | ||
| base: core18 | ||
| base: core20 |
There was a problem hiding this comment.
As mentioned in https://github.com/PowerShell/PowerShell-Snap/issues/87#issuecomment-1216799996 it might be advisable to skip core20 and jump directly to core22.
|
|
||
| adopt-info: powershell | ||
| base: core18 | ||
| base: core20 |
There was a problem hiding this comment.
As mentioned in https://github.com/PowerShell/PowerShell-Snap/issues/87#issuecomment-1216799996 it might be advisable to skip core20 and jump directly to core22.
… build for core20
|
Let's merge this into a new branch and create a test channel before we try to release this. |
|
Imho, it is easier to step bases one at a time; land core18 -> core20 (into a test channel) then do another core20 -> core22 if everything is working as expected. |
4 participants
PR Summary
Upgrade from base:core18 to base:core20, and provide security patches for the libraries that are bundled in the Snap Package that PowerShell is relying upon and minimalize install size.
PR Context
Resolves #87