Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

find-changed-drivers

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, tj-actions/changed-files@v41. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

upload-driver (drivers/SmartThings/matter-lock)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

1 out of 3 runs failed: Handle driverSwitched event: /#L0

tests/matter-lock_test_output.xml

2 out of 7 runs failed: Handle received refresh.: /#L0

tests/matter-lock_test_output.xml

1 out of 6 runs failed: Component-capability update without profile ID update should cause re-subscribe in infoChanged handler: /#L0

tests/matter-lock_test_output.xml

1 out of 6 runs failed: No component-capability update and no profile ID update should not cause a re-subscribe in infoChanged handler: /#L0

tests/matter-lock_test_output.xml

Test modular lock profile change when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test modular lock profile change when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-unlatch profile change with unlatch when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test modular lock profile change with unlatch when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

All 2 runs failed: Test lock-user-pin profile change when BatChargeLevel and BatPercentRemaining attributes are available: /#L0

tests/matter-lock_test_output.xml

Test modular lock profile change with user, pin. schedule, and unlatch supported when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

Test modular lock profile update (modular to modular) with user, pin. schedule, and unlatch supported. Ensure infoChanged updates subscription failed: /#L0

tests/matter-lock_test_output.xml

All 2 runs failed: Handle received OperatingMode(Normal, Vacation) from Matter device.: /#L0

tests/matter-lock_test_output.xml

All 2 runs failed: Handle received OperatingMode(Privacy, No Remote Lock UnLock, Passage) from Matter device.: /#L0

tests/matter-lock_test_output.xml

3 out of 4 runs failed: Handle Lock command received from SmartThings.: /#L0

tests/matter-lock_test_output.xml

3 out of 4 runs failed: Handle Unlock command received from SmartThings.: /#L0

tests/matter-lock_test_output.xml

Handle Unlatch command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

3 out of 4 runs failed: Handle received LockState.LOCKED from Matter device.: /#L0

tests/matter-lock_test_output.xml

3 out of 4 runs failed: Handle received LockState.UNLOCKED from Matter device.: /#L0

tests/matter-lock_test_output.xml

1 out of 2 runs failed: Handle received LockState.UNLATCHED from Matter device.: /#L0

tests/matter-lock_test_output.xml

Handle Unlatch Operation event from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

All 2 runs failed: Handle received AliroReaderVerificationKey from Matter device.: /#L0

tests/matter-lock_test_output.xml

Handle received AliroReaderGroupIdentifier from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received AliroExpeditedTransactionSupportedProtocolVersions from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received AliroSupportedBLEUWBProtocolVersions from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received AliroGroupResolvingKey from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received AliroBLEAdvertisingVersion from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received NumberOfAliroEndpointKeysSupported from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle Set Card Id command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Handle Set Reader Config command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Handle Set Endpoint Key command and Clear Endpoint Key command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Handle Set Issuer Key command and Clear Issuer Key command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Handle received NumberOfTotalUsersSupported from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received NumberOfPINUsersSupported from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received MinPINCodeLength from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received MaxPINCodeLength from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received NumberOfWeekDaySchedulesSupportedPerUser from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received NumberOfYearDaySchedulesSupportedPerUser from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle received RequirePINforRemoteOperation(true) from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

Handle for duplicated pincode during COTA setting failed: /#L0

tests/matter-lock_test_output.xml

Handle received RequirePINforRemoteOperation(false) from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

1 out of 2 runs failed: UnlockDoor uses cota cred when present: /#L0

tests/matter-lock_test_output.xml

1 out of 2 runs failed: LockDoor uses cota cred when present: /#L0

tests/matter-lock_test_output.xml

2 out of 3 runs failed: Handle received LockState.NOT_FULLY_LOCKED from Matter device.: /#L0

tests/matter-lock_test_output.xml

2 out of 3 runs failed: Handle DoorLockAlarm event from Matter device.: /#L0

tests/matter-lock_test_output.xml

Handle Lock Operation event from Matter device. failed: /#L0

tests/matter-lock_test_output.xml

All 2 runs failed: Added lifecycle event lock nocodes nobattery: /#L0

tests/matter-lock_test_output.xml

Handle Add User command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Add User command received from SmartThings and commandResult is busy failed: /#L0

tests/matter-lock_test_output.xml

Handle Add User command received from SmartThings and commandResult is resourceExhausted failed: /#L0

tests/matter-lock_test_output.xml

Handle Update User command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Update User command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Delete User command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Delete User command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Delete All Users command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Delete All Users command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Add Credential command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Add Credential command received from SmartThings and commandResult is busy failed: /#L0

tests/matter-lock_test_output.xml

Add Credential command received from SmartThings and commandResult is invalidCommand failed: /#L0

tests/matter-lock_test_output.xml

Add Credential command received from SmartThings and user_index is occupied failed: /#L0

tests/matter-lock_test_output.xml

Add Credential command received from SmartThings and commandResult is resourceExhausted failed: /#L0

tests/matter-lock_test_output.xml

Handle Update Credential command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Update Credential command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Delete Credential command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Delete Credential command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Delete all Credentials command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Delete all Credentials command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Add Week Day Schedule command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Add Week Day Schedule command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Handle Clear Week Day Schedule command received from SmartThings. failed: /#L0

tests/matter-lock_test_output.xml

Clear Week Day Schedule command received from SmartThings and send busy state failed: /#L0

tests/matter-lock_test_output.xml

Add Guest User and failure response failed: /#L0

tests/matter-lock_test_output.xml

Add Guest User and failure response, and ClearUser command fails as well failed: /#L0

tests/matter-lock_test_output.xml

Test lock profile change when attributes related to BAT feature is not available. failed: /#L0

tests/matter-lock_test_output.xml

Test lock profile change when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test lock profile change when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-unlatch profile change when attributes related to BAT feature is not available. failed: /#L0

tests/matter-lock_test_output.xml

Test lock-unlatch profile change when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-unlatch profile change when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-user-pin profile change when attributes related to BAT feature is not available. failed: /#L0

tests/matter-lock_test_output.xml

Test lock-user-pin profile change when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-user-pin-schedule-unlatch profile change when attributes related to BAT feature is not available. failed: /#L0

tests/matter-lock_test_output.xml

Test lock-user-pin-schedule-unlatch profile change when BatChargeLevel attribute is available failed: /#L0

tests/matter-lock_test_output.xml

Test lock-user-pin-schedule-unlatch profile change when BatChargeLevel and BatPercentRemaining attributes are available failed: /#L0

tests/matter-lock_test_output.xml

2904 tests found (test 1 to 1006)

There are 2904 tests, see "Raw output" for the list of tests 1 to 1006.

2904 tests found (test 1007 to 1957)

There are 2904 tests, see "Raw output" for the list of tests 1007 to 1957.

2904 tests found (test 1958 to 2902)

There are 2904 tests, see "Raw output" for the list of tests 1958 to 2902.

2904 tests found (test 2903 to 2904)

There are 2904 tests, see "Raw output" for the list of tests 2903 to 2904.

Artifacts

Produced during runtime

Name	Size	Digest
head_ref	166 Bytes	`sha256:338381407c3865eee3ddbc44b006c0de4feafae3160d5647c5efe37442f20df3`
matter-lock	103 KB	`sha256:0941f5e3ec2849827eb289c68f238d8ba48621fdce8240ea716a1c26718938c7`
pr_number	147 Bytes	`sha256:b2690b7199d216c11853ab28073d5c4b91310bb4145670346c8b39617f449235`

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WWSTCERT-12180 Schlage Sense Pro #8975

Summary

WWSTCERT-12180 Schlage Sense Pro #8975

Uh oh!

upload-driver-packages.yml

Annotations

Artifacts