-
Notifications
You must be signed in to change notification settings - Fork 235
WIP: Test cherry picks #882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Test cherry picks #882
Conversation
* Prep 1.11 release with Changelog * spaces
…owerShell#866) The 7 exceptions that are caught now are doc'd in: https://docs.microsoft.com/en-us/dotnet/api/system.io.filestream.-ctor?view=netframework-4.7.2#System_IO_FileStream__ctor_System_String_System_IO_FileMode_System_IO_FileAccess_
* Added `AsNewFile` switch, plus, if a file is not open, it creates a new one * Update module/PowerShellEditorServices/Commands/Public/Out-CurrentFile.ps1 Co-Authored-By: dfinke <[email protected]>
* Return the start line number for Describe block Supports PR 1776 in vscode-powershell * Null check pesterSymbol.ScriptRegion * Update comment to cause new build to kick off * Whitespace change to kick off a new build
* Add attach to local runspace. * Remove comment. * Use single runspaceId property. * Remove unnecessary processId check. * Factored if. * Update src/PowerShellEditorServices.Protocol/Server/DebugAdapter.cs It's neat that we can just commit a suggestion. Co-Authored-By: adamdriscoll <[email protected]> * Use runspace rather than dynamic. * Accept process ID for GetRunspaceRequest. * Clean up.
@@ -12,7 +12,7 @@ | |||
RootModule = 'PowerShellEditorServices.psm1' | |||
|
|||
# Version number of this module. | |||
ModuleVersion = '1.10.3' | |||
ModuleVersion = '1.11.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will get bumped to 1.11.1
before the release, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it will be 1.12.0 because weve got features!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo the merge conflicts being fixed.
Yeah this will be closed and I will do it to the branch directly so we keep the full history. |
this should go into legacy |
I am waiting on #881 to be merged in before merging this in.
This should probably go in before #880