Repository navigation
chore: promote cli 5.12.0 - #299
Merged
Merged
Conversation
* ReleaseAs: 5.8.0 * Release-As: 5.8.0 * Release-As: 5.8.0 * chore(production): release 5.8.0 * chore: pin the 5.9.0 promotion Release-As: 5.9.0 * chore(production): release 5.9.0 * chore: pin the 5.10.0 promotion Release-As: 5.10.0 * chore(production): release 5.10.0 * chore: pin the 5.11.0 promotion Release-As: 5.11.0 * chore(production): release 5.11.0 * chore: pin the 5.11.1 promotion Release-As: 5.11.1 * chore(production): release 5.11.1 --------- Co-authored-by: finalerock44 <ethan@devicecloud.dev> Co-authored-by: finalerock44 <77282157+finalerock44@users.noreply.github.com> Co-authored-by: dcd-release-please[bot] <296541543+dcd-release-please[bot]@users.noreply.github.com> Co-authored-by: Tom Riglar <tom.riglar@moropo.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Both installers now check the version (pinned or from the manifest) before building the download URLs, and stop with a clear message unless it looks like 5.0.0 or 5.0.0-beta.1.
#297) fix(device): a start that got no answer says a session may still have started `dcd device start` printed a bare error when POST /device/sessions got no answer (a network error) or a proxy's 502 in the API's place. The API may have created the session anyway, and it is billed while it runs, so running the command again could leave two. When the outcome is unknown, the error now says so first and lists the open sessions started in the last 2 minutes (the one in the --json envelope's session when there is exactly one), with how to check or stop them, or says it is safe to start again. The API's own errors (its { statusCode, message } envelope) still come through unchanged: those are refusals made before any session exists. The recent-session lookup moves into DeviceGateway.recentlyStarted, shared with the MCP bridge's explanation of a failed start_device.
#298) feat(report): deprecate allure and html-detailed, removed on 7 December 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.
Release-As: 5.12.0
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Type of change
fix— bug fixfeat— new featureperf— performance improvementrefactor— code change that's neither a fix nor a featuredocs— documentation onlychore/ci/build/test— tooling, no user-facing change!or PR notes aBREAKING CHANGE:)Checklist
pnpm lintpassespnpm typecheckpassespnpm buildpassesCHANGELOG.md(release-please handles this)README.md/STYLE_GUIDE.mdupdated if behaviour or output changedHow to test