ADO Marketplace extension update to 2.0.0 has broken our report display in the pipeline

[bedazbedaz]

This morning we are unable to load any Allure Reports from the tab in the pipeline results in ADO.

The update went in at 3:27am local time. I have confirmation that it was working at 1am, and it has stopped rendering anything from first attempts this morning around 9am. Seems likely the update is the cause. Happening across all our pipelines, the reports render fine if you download the allure-report folder and run locally, just don't render in pipeline.

Sits on this screen indefinitely. Have confirmed it affects reports well under the size limit (15mb), so not a size issue.

The report that displayed correctly at 1am now does not display after the update.

[ymouhat]

HI @bedazbedaz
I confirm we encounter the same issue
a new version has been published today

In our azure devops enviroment, the extension has been updated during the day and since then we can't verify the allure report results anymore.

The allure tab is looping idefinitely without succeeding to render the allure report

hHe report is properly generated and even very small report are not rendered Past reports of previous builds are not rendered anymore either.

[iry-hor-code]

Same issue here at our org (this is my personal GitHub account as we don't use GitHub). It's basically stuck in an infinite loop of making a GET request that returns 200OK but nothing in the response but an empty array. Was working fine before this latest update. Please advise on how to proceed. Would re-installing the plug-in help?

Thanks! 🙏

[dexter444sz]

Good day. Same issue. Also, when I try to use version 2, I've got this error

_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\index.js:50
const core_1 = require("@allurereport/core");
^

Error [ERR_REQUIRE_ESM]: require() of ES Module C:\agent1_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\node_modules@allurereport\core\dist\index.js from C:\agent1_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\index.js not supported.
Instead change the require of C:\agent1c_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\node_modules@allurereport\core\dist\index.js in C:\agent1_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\index.js to a dynamic import() which is available in all CommonJS modules.
at Object. (C:\agent1_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.0\index.js:50:16) {
code: 'ERR_REQUIRE_ESM'
}

[ZehL]

Also the same in my org. The moment it auto updated to v2.0.0 all reports started to loop on loading

[jyothish-aveva]

I am also facing same issue. It was working fine till last night.

[Milos-Milicevic-QA]

Also, facing the same issue, need fix asap!

[epszaw]

Hello there! Sorry, for inconveniences!
The fix is ready and will be available in version 2.0.1.
The new version supports new reports and already generated ones.
The version will be available once passed validation on the marketplace.

[ymouhat]

Hi @epszaw
Thank you for your reactivity , it is back and running :)

[Milos-Milicevic-QA]

still same issue:

025-12-18T15:01:23.3615028Z Task : Publish Allure Report
2025-12-18T15:01:23.3615112Z Description : Task for generate and publish Allure Report
2025-12-18T15:01:23.3615215Z Version : 2.0.1
2025-12-18T15:01:23.3615280Z Author : Qameta Software Inc.
2025-12-18T15:01:23.3615840Z Help : Generate and publish Allure Report
2025-12-18T15:01:23.3615942Z ==============================================================================
2025-12-18T15:01:23.5316685Z ##[debug]Using node path: B:\build_agent\externals\node20_1\bin\node.exe
2025-12-18T15:01:23.7781676Z B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\index.js:50
2025-12-18T15:01:23.7783011Z const core_1 = require("@allurereport/core");
2025-12-18T15:01:23.7783197Z ^
2025-12-18T15:01:23.7783253Z
2025-12-18T15:01:23.7783682Z Error [ERR_REQUIRE_ESM]: require() of ES Module B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\node_modules@allurereport\core\dist\index.js from B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\index.js not supported.
2025-12-18T15:01:23.7784522Z Instead change the require of B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\node_modules@allurereport\core\dist\index.js in B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\index.js to a dynamic import() which is available in all CommonJS modules.
2025-12-18T15:01:23.7785157Z at Object. (B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\index.js:50:16) {
2025-12-18T15:01:23.7785460Z code: 'ERR_REQUIRE_ESM'
2025-12-18T15:01:23.7785591Z }
2025-12-18T15:01:23.7785637Z
2025-12-18T15:01:23.7785773Z Node.js v20.11.1
2025-12-18T15:01:23.8493046Z ##[error]Exit code 1 returned from process: file name 'B:\build_agent\externals\node20_1\bin\node.exe', arguments '"B:\build_agent_work_tasks\PublishAllureReport_867c4cd2-7a10-11ed-a1eb-0242ac120189\2.0.1\index.js"'.