Skip to content

Bump azure-pipelines-task-lib to ^5.2.10 for AzureKeyVaultV2, AzurePowerShellV4, AzurePowerShellV5#22219

Open
v-abhishera wants to merge 3 commits into
masterfrom
users/v-abhishera/tasklibfix-v2
Open

Bump azure-pipelines-task-lib to ^5.2.10 for AzureKeyVaultV2, AzurePowerShellV4, AzurePowerShellV5#22219
v-abhishera wants to merge 3 commits into
masterfrom
users/v-abhishera/tasklibfix-v2

Conversation

@v-abhishera
Copy link
Copy Markdown
Contributor

Problem

azure-pipelines-task-lib versions prior to 5.2.10 have a bug where cp() treats @ characters in file/directory names as glob patterns, causing infinite recursion and stack overflow when copying paths containing @ (e.g., node_modules/@azure/...).

Changes

Task Version (Default) Version (Node24)
AzureKeyVaultV2 2.275.0 2.275.1
AzurePowerShellV4 4.275.6 4.275.7
AzurePowerShellV5 5.275.8 5.275.9
  • Updated package.json → azure-pipelines-task-lib: ^5.2.10
  • Updated package-lock.json to resolve task-lib 5.2.10 (both Default and Node24 variants)
  • Bumped task versions in task.json / task.loc.json
  • Regenerated _generated files via BuildConfigGen

Testing

  • L0 tests pass for all 3 tasks (Node20 and Node24 variants)
  • Local build with node make.js build succeeds for all tasks

…werShellV4, AzurePowerShellV5

Update task-lib from ^5.2.8 to ^5.2.10 to fix cp() treating @ as glob
causing infinite recursion. Also updates Node24 lockfiles to resolve
to 5.2.10.
@v-abhishera v-abhishera requested review from a team and manolerazvan as code owners May 29, 2026 06:29
@v-abhishera
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

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.

1 participant