Bump azureutils and appservice packages #3968
Closed
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
Consume downstream changes microsoft/vscode-azuretools#1677, microsoft/vscode-azuretools#1676, that prevent microsoft/vscode-azuretools#1669 from breaking kudu calls
|
Converted to draft because I'm still seeing issues today. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Consume downstream changes microsoft/vscode-azuretools#1677, microsoft/vscode-azuretools#1676, that prevent microsoft/vscode-azuretools#1669 from breaking kudu calls
Also added this to the change log. We should try updating the change log as we make the changes this time around and see how it goes. I want to do a better job of reflecting the changes we are consuming from the shared packages in the change log too, as I often find myself having to search for when changes from the shared package made it into the extensions.
We can error on the side of too much detail, and then pare it down at release time as needed.