What's changed in 2.21.0
🐞 Bug Fixes
- Avoid .allure startup failures in restricted home directories (see below)
- Prevent job-run env from overwriting CI run URLs (see below)
Avoid .allure startup failures in restricted home directories
allurectl no longer tries to create $HOME/.allure during command startup. Commands such as watch, upload, and --help can now run in containers or CI environments where the detected home directory resolves to / or another unwritable location.
auth login still creates and writes the config file when credentials are saved, but now fails clearly if the configured path cannot be written and only prints the success message after the config is stored. This also refreshes the repository’s Allure agent workflow guide so future test work uses confirmed local capabilities, CI dump/report conventions, and reviewable evidence expectations.
Prevent job-run env from overwriting CI run URLs
allurectl job-run env now exposes the Allure TestOps job-run link as ALLURE_TESTOPS_JOB_RUN_URL instead of ALLURE_JOB_RUN_URL. This keeps ALLURE_JOB_RUN_URL reserved for the external CI run URL, so workflows that export job-run env before running watch no longer send an Allure TestOps job-run page back to TestOps as the CI URL.
This fixes the case where launches created after export $(./allurectl job-run env) showed links to the TestOps job run itself instead of the original CI job-run URL.