Skip to content

Conversation

@rm-dmiri
Copy link
Contributor

Context

We updated common library with regression fix for MSAL library issues.
See for reference: #21585


Task Name

AzureRmWebAppDeploymentV3
AzureRmWebAppDeploymentV4
AzureRmWebAppDeploymentV5


Description

Upgraded azure-pipelines-tasks-azure-arm-rest dependency from various versions (3.254.0, 3.263.1, 3.267.0) to version 3.267.1 across all tasks that use this package to fix MSAL library dependency issues.

This PR affects part 2 of tasks (owned by RM). They have heavy CI builds which tent to timeout, there fore they are separated.


Risk Assessment (Low / Medium / High)

Low - This is a patch version update of a common dependency package with backward compatible changes and no breaking API modifications.


Change Behind Feature Flag (Yes / No)

No - This is a dependency version update that applies globally and doesn't require feature flagging as it maintains backward compatibility.


Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

No - Dependency version updates don't require user-facing documentation changes.


Unit Tests Added or Updated (Yes / No)

No - Existing unit tests cover the functionality; no behavioral changes were made.


Additional Testing Performed

Built and verified successful compilation of sample tasks including AzurePowerShellV5, JavaToolInstallerV1, and AzureRmWebAppDeploymentV5 using the updated dependency.


Logging Added/Updated (Yes/No)

No log updates except one from new package dependency. They are safe and don't log sensitive data.


Telemetry Added/Updated (Yes/No)

No.


Rollback Scenario and Process (Yes/No)

Task version downgrade, or changes revert and published with new task version.


Dependency Impact Assessed and Regression Tested (Yes/No)

Yes. Tested with CI.


Checklist

  • Related issue linked (if applicable)
  • Task version was bumped — see versioning guide
  • Verified the task behaves as expected

@rm-dmiri
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@rm-dmiri rm-dmiri enabled auto-merge (squash) January 22, 2026 08:24
@rm-dmiri
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@rm-dmiri
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

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.

2 participants