Skip to content

feat(report): deprecate allure and html-detailed, removed on 7 Decemb… - #298

Merged
finalerock44 merged 1 commit into
devfrom
feat/deprecate-report-allure-html-detailed
Nov 5, 2026
Merged

finalerock44 merged 1 commit into
devfrom
feat/deprecate-report-allure-html-detailed

Conversation

@finalerock44

Copy link
Copy Markdown
Contributor

…er 2026

The allure and html-detailed report formats are deprecated and will be removed on 7 December 2026. Both values stay valid after that date. A run that asks for html-detailed gets the standard HTML report, and a run that asks for allure gets no report, but neither run fails.

  • dcd cloud adds report to the notice context, so the server-side deprecation notices can be shown to runs that ask for either format. Older CLIs leave it out and evaluate the gate as false.
  • dcd artifacts --report allure|html-detailed prints a deprecation line on stderr, because that command fetches no notices.
  • The help for --report and --allure-path, and the MCP download tool's description, give the date. The old advice to use allure for a complete HTML report is gone.

What & why

Type of change

  • fix — bug fix
  • feat — new feature
  • perf — performance improvement
  • refactor — code change that's neither a fix nor a feature
  • docs — documentation only
  • chore / ci / build / test — tooling, no user-facing change
  • Breaking change (title has ! or PR notes a BREAKING CHANGE:)

Checklist

  • PR title follows the Conventional Commits format (see comment above)
  • pnpm lint passes
  • pnpm typecheck passes
  • pnpm build passes
  • I have not bumped the version or edited CHANGELOG.md (release-please handles this)
  • I have signed the CLA (the bot will prompt on first contribution)
  • Docs / README.md / STYLE_GUIDE.md updated if behaviour or output changed

How to test

…er 2026

The allure and html-detailed report formats are deprecated and will be
removed on 7 December 2026. Both values stay valid after that date. A run
that asks for html-detailed gets the standard HTML report, and a run that
asks for allure gets no report, but neither run fails.

- `dcd cloud` adds `report` to the notice context, so the server-side
  deprecation notices can be shown to runs that ask for either format.
  Older CLIs leave it out and evaluate the gate as false.
- `dcd artifacts --report allure|html-detailed` prints a deprecation line
  on stderr, because that command fetches no notices.
- The help for --report and --allure-path, and the MCP download tool's
  description, give the date. The old advice to use allure for a complete
  HTML report is gone.
@finalerock44 finalerock44 self-assigned this Nov 5, 2026
@claude

claude Bot commented Nov 5, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

🤖 Generated with Claude Code

@finalerock44
finalerock44 merged commit 9bfcdb9 into dev Nov 5, 2026
9 checks passed
@finalerock44
finalerock44 deleted the feat/deprecate-report-allure-html-detailed branch November 5, 2026 14:59
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