-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Update RM tasks to use [email protected] #21588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ivanduplenskikh
wants to merge
11
commits into
master
Choose a base branch
from
users/iduplenskikh/2342595
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
346f6ba to
1049c7a
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
b7ef8d8 to
e56684c
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
e56684c to
7936745
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
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
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.
Context
This PR updates 47 Azure Pipelines tasks to use the latest version of
azure-pipelines-task-lib(v5.2.3)📌 Related Work Item: AB#2342595
Task Name
Description
This PR updates the
azure-pipelines-task-libdependency from v4.x versions to v5.2.3 across 47 pipeline tasks.The update includes:
azure-pipelines-task-libfrom v4.x → v5.2.3 in package.json filesRisk Assessment
TBD
Change Behind Feature Flag - No
This is a dependency update that affects the runtime behavior of tasks and cannot be covered by a feature flag
Tech Design / Approach
N/A
Documentation Changes Required - No
No user-facing functionality changes. This is an internal dependency update that does not affect task inputs, outputs, or behavior from a user perspective.
Unit Tests Added or Updated - No
Existing unit tests remain valid as task functionality is unchanged
Additional Testing Performed
Logging Added/Updated - No
No changes to logging implementation
Telemetry Added/Updated - No
No custom telemetry changes in this PR
Rollback Scenario and Process - Yes
Rollback Plan:
[email protected]instead of@1.267)Dependency Impact Assessed and Regression Tested - Yes
Dependency Analysis:
Checklist