Skip to content

Separate trait response handling logic from refresh logic and merge #2711

Separate trait response handling logic from refresh logic and merge

Separate trait response handling logic from refresh logic and merge #2711

Triggered via pull request March 16, 2026 04:53
Status Failure
Total duration 1m 10s
Artifacts

ci.yml

on: pull_request
Matrix: test
Lint Commit Messages
14s
Lint Commit Messages
lint
19s
lint
Build Package
10s
Build Package
Test Semantic Release
1m 6s
Test Semantic Release
release
release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Lint Commit Messages
You have commit messages with errors ⧗ input: Draft to set trait values ✖ subject may not be empty [subject-empty] ✖ type may not be empty [type-empty] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: refactor: remove trait update listeners and centralize data conversion into dedicated converter classes ✖ header must not be longer than 100 characters, current length is 103 [header-max-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: chore: Remove unused `typing.Self` import. ✖ subject may not end with full stop [subject-full-stop] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: refactor: Standardize trait data merging to `merge_trait_values` and remove direct `_parse_response` methods from traits. ✖ header must not be longer than 100 characters, current length is 121 [header-max-length] ✖ subject may not end with full stop [subject-full-stop] ✖ found 2 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs: clarify internal usage of V1TraitDataConverter and V1TraitMixin attributes. ✖ subject may not end with full stop [subject-full-stop] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: style: Remove trailing whitespace from a blank line in `common.py` docstring. ✖ subject may not end with full stop [subject-full-stop] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: refactor: Make V1TraitDataConverter an abstract base class, use a dedicated LedStatusConverter, and fix a typo in Rooms. ✖ header must not be longer than 100 characters, current length is 120 [header-max-length] ✖ subject may not end with full stop [subject-full-stop] ✖ 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/
test (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
test (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/