Skip to content
CI

feat: Implement v1 streaming data updates #2798

Sign in to view logs

feat: Implement v1 streaming data updates

feat: Implement v1 streaming data updates #2798

Triggered via pull request March 23, 2026 01:08
@allenporterallenporter
synchronize #799
allenporter:v1-streaming-updates
Status Failure
Total duration 1m 4s
Artifacts –

ci.yml

on: pull_request
Matrix: test
Lint Commit Messages
12s
Lint Commit Messages
lint
19s
lint
Build Package
12s
Build Package
Test Semantic Release
1m 1s
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: feat: Implement direct device trait updates from data protocol messages using `dps` metadata and add corresponding update listeners. This uses the same dps converter patern used by q10, but does not share code explicitly. ✖ 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
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/