Address issues for v1.1.0 release #145
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PaulHigin
changed the title
SydneyhSmith
approved these changes
May 11, 2021
PaulHigin
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR has a number of changes that have been marked for v1.1.0 (preview) release.
Also, how extension vaults are hosted has changed. Previously, extension vault modules were hosted in the current user session. Now, to accommodate CL mode, they are hosted in a separate dedicated PowerShell runspace session. This means extension vault modules an not share session state with the current user session, which is a possible breaking change. Consequently this release will be v1.1.0 and will begin with a preview release.