Skip to content

feat(api)!: Again rename YXDeviceState enum members to have consistency with V1 state values #2768

feat(api)!: Again rename YXDeviceState enum members to have consistency with V1 state values

feat(api)!: Again rename YXDeviceState enum members to have consistency with V1 state values #2768

Triggered via pull request March 22, 2026 16:04
Status Failure
Total duration 52s
Artifacts

ci.yml

on: pull_request
Matrix: test
Lint Commit Messages
17s
Lint Commit Messages
lint
17s
lint
Build Package
8s
Build Package
Test Semantic Release
50s
Test Semantic Release
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Lint Commit Messages
You have commit messages with errors ⧗ input: BREAKING: Again rename `YXDeviceState` enum members to have consistency with V1 state values The motivation is to not have entirely different state values for the same concept to make it easier to write systems that can handle each device. ✖ type must be lower-case [type-case] ✖ type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/