Skip to content

deps: bump azext-azureappservice to 5.0.2 for #5073 audience-consent fix#5102

Closed
alexweininger wants to merge 4 commits into
mainfrom
deps/azext-appservice-5.0.2
Closed

deps: bump azext-azureappservice to 5.0.2 for #5073 audience-consent fix#5102
alexweininger wants to merge 4 commits into
mainfrom
deps/azext-appservice-5.0.2

Conversation

@alexweininger

@alexweininger alexweininger commented Jun 8, 2026

Copy link
Copy Markdown
Member

Picks up the App Service audience eager-consent fix (microsoft/vscode-azuretools#2315): getAppServiceCredentials now prompts for one-time consent to the App Service audience before silent token acquisition, fixing 'You are not signed in to an Azure account' on deploy/log-stream/tunnel.

  • @microsoft/vscode-azext-azureappservice ^5.0.1 -> ^5.0.2
  • @microsoft/vscode-azext-azureutils ^4.0.1 -> ^4.3.0 (parseClientContext
    now preserves the subscription authentication object)
  • @microsoft/vscode-azext-utils ^4.1.0 -> ^4.1.1 (dedupes on the
    utils version that types ISubscriptionContext.authentication)
  • engines.vscode ^1.104.0 -> ^1.106.0 (aligns with
    the highest VS Code engine version required by updated transitive dependencies)
  • @types/vscode ^1.104.0 -> 1.106.0 (pinned to exact
    version; VS Code does not follow semver so a range would resolve to a higher
    version than the declared engine)

Addresses #5073

Picks up the App Service audience eager-consent fix
(microsoft/vscode-azuretools#2315): getAppServiceCredentials now prompts for
one-time consent to the App Service audience before silent token acquisition,
fixing 'You are not signed in to an Azure account' on deploy/log-stream/tunnel.

- @microsoft/vscode-azext-azureappservice ^5.0.1 -> ^5.0.2
- @microsoft/vscode-azext-azureutils      ^4.0.1 -> ^4.2.1 (parseClientContext
  now preserves the subscription authentication object)
- @microsoft/vscode-azext-utils           ^4.1.0 -> ^4.1.1 (dedupes on the
  utils version that types ISubscriptionContext.authentication)

Addresses #5073

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 8, 2026 20:05
@alexweininger alexweininger requested a review from a team as a code owner June 8, 2026 20:05

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates Azure extension dependencies to pick up the App Service “audience eager-consent” fix intended to resolve Azure sign-in failures during deploy/log-stream/tunnel scenarios.

Changes:

  • Bump @microsoft/vscode-azext-azureappservice to ^5.0.2.
  • Bump @microsoft/vscode-azext-azureutils to ^4.2.1 and @microsoft/vscode-azext-utils to ^4.1.1.
  • Regenerate package-lock.json to reflect updated transitive dependency graph.
Show a summary per file
File Description
package.json Updates direct dependency versions to consume the upstream audience-consent/auth-related fixes.
package-lock.json Updates resolved versions and introduces new transitive deps required by the bumped packages.

Copilot's findings

  • Files reviewed: 1/2 changed files
  • Comments generated: 1

Comment thread package.json
Aligns with vscode-azureresourcegroups by consuming
@microsoft/vscode-azext-azureutils 4.3.0, which widens its azext-azureauth
range and migrates to @azure/arm-resources-subscriptions v3. The
dependency tree stays a single copy of each, now resolving to
azext-azureauth 6.1.0-alpha.2 and arm-resources-subscriptions 3.0.0-beta.1.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@alexweininger

Copy link
Copy Markdown
Member Author

@copilot resolve the merge conflicts

Copilot AI commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts

Resolved — merged main into the branch, fixed the package.json and package-lock.json conflicts, and regenerated the lockfile in 8d93a7b.

Comment thread package-lock.json Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants