Publish Report task fails in v 1.4.8 on MacOS

[darrentaft]

Last known working version was 1.4.6.

We now see the following error when using the Publish Allure Report task on Azure:

2025-07-30T06:05:39.7837900Z ##[section]Starting: Publish Allure Report
2025-07-30T06:05:39.7869430Z ==============================================================================
2025-07-30T06:05:39.7869940Z Task         : Publish Allure Report
2025-07-30T06:05:39.7870170Z Description  : Task for generate and publish Allure Report
2025-07-30T06:05:39.7870450Z Version      : 1.4.8
2025-07-30T06:05:39.7870610Z Author       : Qameta Software Inc.
2025-07-30T06:05:39.7872300Z Help         : Generate and publish Allure Report
2025-07-30T06:05:39.7872600Z ==============================================================================
2025-07-30T06:05:39.7974090Z ##[error]The current operating system is not capable of running this task. That typically means the task was written for Windows only. For example, written for Windows Desktop PowerShell.
2025-07-30T06:05:39.7984150Z ##[section]Finishing: Publish Allure Report

[delatrie]

Hi, @darrentaft
The task now requires Node 20 to run. You should either update your self-hosted runners to a more recent version or stick to 1.4.6.

[darrentaft]

OK thanks - I'll see if we can update the node version on the shared environment,.

Do you know how we can force it to use 1.4.6? We just use the "qameta.allure-azure-pipelines.PublishAllureReport.PublishAllureReport@1" task in Azure Devops, which takes these updates without our control. Given that there was a breaking change, it sounds like this should have been published as a v2 of the task.

[delatrie]

It turns out that's not possible in Azure DevOps unless the extension includes both versions of the task simultaneously, which is not our case.

Sorry for the inconvenience we caused you. Version 1.5.0 introduces backward compatibility with Node 16, which should resolve the issue in your case. However, I strongly recommend updating the agents since older versions use outdated software, which may lead to security vulnerabilities.

[darrentaft]

Thanks. We did try forcing Node 20 on the pipeline but it still failed, however the update to 1.5.0 has sorted it now.