PublishAllureReport@2 v2.2.0 fails on Node 20: uuid/v4 is not exported #3459
Replies: 4 comments 3 replies
|
Same to me. Failing everywhere with Node 24 in my case. |
0 replies
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
After updating the Allure Report Azure DevOps extension to version
2.2.0,PublishAllureReport@2fails before processing Allure results.The Azure Pipelines task runs with its Node 20 handler and throws:
It appears the bundled Azure Pipelines tool library still imports uuid/v4, which is incompatible with the installed modern uuid package. The task
should use the supported root import (require("uuid").v4 / import { v4 } from "uuid") or align the bundled dependency versions accordingly.
Pipeline step
displayName: "Publish Allure Report"
inputs:
testResultsDir: "reports/allure-results"
reportName: "AppName Allure Report"
Expected behavior
The task loads successfully and generates/publishes the Allure report.
Actual behavior
The task terminates during startup, before reading task inputs or generating the report.
Environment
Changing the task’s allureVersion input does not help, because the failure occurs while the task is loading.
All reactions