auth: Revert "Allow getting session and access token with custom scope (#1643)" and bump version to 2.3.0 #1646
Conversation
This file contains 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
|
Figured out #1643 is causing some issues with sovereign clouds microsoft/vscode-azureresourcegroups#768 (comment). And of course this also breaks zip deploy. |
bwateratmsft
approved these changes
Dec 14, 2023
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.
I had to manually release the auth package yesterday to release Azure Resources, and while doing that I messed up the release and these changes were actually included in the 2.1.0 release. This is causing critical bugs in the Azure Resources 0.8.2 release and needs to be fixed ASAP.
I will manually release this again locally but I'll double check the contents this time.