Deprecate BT_FIXED_APPKEY #25414

m-alperen-sener · 2025-11-04T16:10:29Z

Deprecating BT_FIXED_PASSKEY and start using BT_APP_PASSKEY instead.

NordicBuilder · 2025-11-04T16:11:12Z

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
matter	nrfconnect/sdk-connectedhomeip@`4c78bef`	nrfconnect/sdk-connectedhomeip@`c982612` (`master`)	nrfconnect/sdk-connectedhomeip@4c78bef4..c9826122
zephyr	nrfconnect/sdk-zephyr@`0985cce`	nrfconnect/sdk-zephyr@`d54a7f8` (`main`)	nrfconnect/sdk-zephyr@0985cced..d54a7f81

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

NordicBuilder · 2025-11-04T16:14:22Z

CI Information

^{To view the history of this post, click the 'edited' button above}
Build number: 28

Inputs:

Sources:

sdk-nrf: PR head: 8c7d26bc0d6b7a466ba86e95e2ea77f6f643e21b
matter: PR head: c9826122fccab36e7caec9654bd1c0fdd1d27242
zephyr: PR head: d54a7f811327fe9cc3da2dffa7365de96c999c08

more details

sdk-nrf:

PR head: 8c7d26bc0d6b7a466ba86e95e2ea77f6f643e21b
merge base: 04261b7795d9492aec972f9d14e142c8ae9cc15d
target head (main): 5fc5b0e5f152d99a0e877007e8fa346674ddc0e8
Diff

matter:

PR head: c9826122fccab36e7caec9654bd1c0fdd1d27242
merge base: 4c78bef4bfc9b66d8d4ed44813cf7560efe69323
Diff

zephyr:

PR head: d54a7f811327fe9cc3da2dffa7365de96c999c08
merge base: 0985cced399a26c994a0736ba8c00dc852e22ec3
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (26)

doc
│  ├── nrf
│  │  ├── libraries
│  │  │  ├── bluetooth
│  │  │  │  ├── mesh
│  │  │  │  │  ├── vnd
│  │  │  │  │  │  ├── images
│  │  │  │  │  │  │  │ bt_mesh_le_pair_resp.svg
│  │  │  │  │  │  │ le_pair_resp.rst
│  │  ├── releases_and_maturity
│  │  │  ├── migration
│  │  │  │  │ migration_guide_3.2.rst
│  │  │  ├── releases
│  │  │  │  │ release-notes-changelog.rst
include
│  ├── bluetooth
│  │  ├── mesh
│  │  │  ├── vnd
│  │  │  │  │ le_pair_resp.h
modules
│  ├── lib
│  │  ├── matter
│  │  │  ├── .github
│  │  │  │  ├── workflows
│  │  │  │  │  ├── examples-nrfconnect.yaml
│  │  │  │  │  │ nrfconnect-ncs.yaml
│  │  │  ├── config
│  │  │  │  ├── nrfconnect
│  │  │  │  │  ├── chip-module
│  │  │  │  │  │  │ Kconfig.features
│  │  │  ├── third_party
│  │  │  │  ├── openthread
│  │  │  │  │  │ ot-realtek
│  │  │  │  ├── pigweed
│  │  │  │  │  │ repo
samples
│  ├── bluetooth
│  │  ├── mesh
│  │  │  ├── common
│  │  │  │  │ smp_bt_auth.c
│  │  │  ├── dfu
│  │  │  │  ├── distributor
│  │  │  │  │  │ overlay-smp-bt-auth.conf
│  ├── matter
│  │  ├── common
│  │  │  ├── src
│  │  │  │  ├── bt_nus
│  │  │  │  │  ├── bt_nus_service.cpp
│  │  │  │  │  │ bt_nus_service.h
│  │  ├── lock
│  │  │  │ sample.yaml
subsys
│  ├── bluetooth
│  │  ├── mesh
│  │  │  ├── vnd
│  │  │  │  ├── Kconfig
│  │  │  │  │ le_pair_resp.c
west.yml
zephyr
│  ├── doc
│  │  ├── releases
│  │  │  │ migration-guide-4.3.rst
│  ├── include
│  │  ├── zephyr
│  │  │  ├── bluetooth
│  │  │  │  │ conn.h
│  ├── subsys
│  │  ├── bluetooth
│  │  │  ├── host
│  │  │  │  ├── Kconfig
│  │  │  │  ├── shell
│  │  │  │  │  │ bt.c
│  │  │  │  │ smp.c
│  ├── tests
│  │  ├── bluetooth
│  │  │  ├── shell
│  │  │  │  ├── audio.conf
│  │  │  │  ├── log.conf
│  │  │  │  │ prj.conf

Outputs:

Toolchain

Version:
Build docker image:

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

◻️ Toolchain
◻️ Build twister
◻️ Integration tests
- ◻️ test-sdk-audio
- ◻️ desktop52_verification
- ◻️ test_ble_nrf_config
- ◻️ test-fw-nrfconnect-ble_mesh
- ◻️ test-fw-nrfconnect-ble_samples
- ◻️ test-fw-nrfconnect-chip
- ◻️ test-fw-nrfconnect-nfc
- ◻️ test-fw-nrfconnect-nrf-iot_thingy91
- ◻️ test-sdk-find-my
- ◻️ test-low-level
- ◻️ test-sdk-dfu

Disabled integration tests

- test-fw-nrfconnect-nrf_lrcs_positioning
- test-fw-nrfconnect-apps
- test-fw-nrfconnect-fem
- test-fw-nrfconnect-nrf-iot_libmodem-nrf
- test-fw-nrfconnect-nrf-iot_lwm2m
- test-fw-nrfconnect-nrf-iot_samples
- test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
- test-fw-nrfconnect-nrf_crypto
- test-fw-nrfconnect-ps-main
- test-fw-nrfconnect-rpc
- test-fw-nrfconnect-rs
- test-fw-nrfconnect-tfm
- test-fw-nrfconnect-thread-main
- test-sdk-mcuboot
- test-sdk-wifi
- test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

github-actions · 2025-11-04T16:54:32Z

You can find the documentation preview for this PR here.

Preview links for modified nRF Connect SDK documents:

https://ncsdoc.z6.web.core.windows.net/PR-25414/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.html
https://ncsdoc.z6.web.core.windows.net/PR-25414/nrf/releases_and_maturity/migration/migration_guide_3.2.html
https://ncsdoc.z6.web.core.windows.net/PR-25414/nrf/releases_and_maturity/releases/release-notes-changelog.html

subsys/bluetooth/mesh/vnd/Kconfig

PavelVPV

I think smp_bt_auth.c for sure should not use the deprecated API and should only be compiled with CONFIG_BT_APP_PASSKEY.

But also I think that since the LE Pairing Responder model is experimental, it is OK to change it is behavior and API without deprecation period. But we need to mention this change in the release notes.

Also, remember to update documentation of the model: https://github.com/nrfconnect/sdk-nrf/blob/main/doc/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.rst.

include/bluetooth/mesh/vnd/le_pair_resp.h

subsys/bluetooth/mesh/vnd/le_pair_resp.c

m-alperen-sener

Updated the documentation and added release notes for DFU distributer sample and LE Pair Responder model.

Remove all dependency on deprecated FIXED_PASSKEY, solely it depends on APP_PASSKEY now.

Removed immediate invalidation of passkey.

Update the Documentation diagram.

added commit to update matter door lock sample.

include/bluetooth/mesh/vnd/le_pair_resp.h

doc/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.rst

doc/nrf/libraries/bluetooth/mesh/vnd/images/bt_mesh_le_pair_resp.svg

ArekBalysNordic

Some changes are required in the Matter Lock sample.

samples/matter/common/src/bt_nus/bt_nus_service.cpp

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

doc/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.rst

include/bluetooth/mesh/vnd/le_pair_resp.h

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

doc/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.rst

divipillai · 2025-11-06T11:37:21Z

doc/nrf/libraries/bluetooth/mesh/vnd/le_pair_resp.rst

-This function can be called from callbacks :c:member:`bt_conn_auth_info_cb.pairing_complete` and :c:member:`bt_conn_auth_info_cb.pairing_failed`.
-See the :file:`samples/bluetooth/mesh/common/smp_bt_auth.c` file for the reference.
+This model requires an application to only enable the display capability for the LE pairing by setting the :c:member:`bt_conn_auth_cb.pairing_display` callback. The application must also set the :c:member:`bt_conn_auth_cb.app_passkey` callback to use the passkey generated by LE Pairing Responder model.
+After every pairing request, the application must invalidate the previously used passkey by calling the :c:func:`bt_mesh_le_pair_resp_passkey_invalidate` function or calling :c:func:`bt_mesh_le_pair_resp_passkey_set` with :ref:`BT_PASSKEY_RAND` value.


Suggested change

After every pairing request, the application must invalidate the previously used passkey by calling the :c:func:`bt_mesh_le_pair_resp_passkey_invalidate` function or calling :c:func:`bt_mesh_le_pair_resp_passkey_set` with :ref:`BT_PASSKEY_RAND` value.

After every pairing request, the application must invalidate the previously used passkey by calling the :c:func:`bt_mesh_le_pair_resp_passkey_invalidate` function or calling :c:func:`bt_mesh_le_pair_resp_passkey_set` with the ``BT_PASSKEY_RAND`` value.

Any specific reason for using ref for a value?

Perhaps it should be :c:macro:BT_PASSKEY_RAND?

I am not able to check this locally, does :c:macro: works with zephyr defined ones? I mean can doc pick up from zephyr?

We do use it at least here and it works:

sdk-nrf/doc/nrf/protocols/bt/bt_mesh/vendor_model/dev_overview.rst

Line 106 in cc348c5

The last element in the opcode list is always the :c:macro:`BT_MESH_MODEL_OP_END` macro:

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/bt/bt_mesh/vendor_model/dev_overview.html#adding_the_model_to_the_node_composition_data

nice, we can do that then 👍

alxelax · 2025-11-07T10:57:58Z

Hi @m-alperen-sener, before merging could you check these things to be sure these changes still work:

mesh le pairing system test (https://projecttools.nordicsemi.no/bitbucket/projects/NCS-TEST/repos/test-sdk-mesh/browse/tests/mesh/samples/le_pairing)
nRF Mesh DFU mobile app manages with pairing (IOS)
Device Manager mobile app manages with pairing (IOS)

mobile app is possible to check with mesh dfu distributor sample

divipillai · 2025-11-07T11:15:50Z

doc/nrf/releases_and_maturity/migration/migration_guide_3.2.rst

+      * The :kconfig:option:`CONFIG_BT_FIXED_PASSKEY` kconfig option has been deprecated, replace it with the :kconfig:option:`CONFIG_BT_APP_PASSKEY` kconfig option.
+        Now, if you want to use a fixed passkey for the Matter Lock NUS service, register the ``app_passkey`` callback in the ``bt_conn_auth_cb`` structure.


Suggested change

* The :kconfig:option:`CONFIG_BT_FIXED_PASSKEY` kconfig option has been deprecated, replace it with the :kconfig:option:`CONFIG_BT_APP_PASSKEY` kconfig option.

Now, if you want to use a fixed passkey for the Matter Lock NUS service, register the ``app_passkey`` callback in the ``bt_conn_auth_cb`` structure.

* The :kconfig:option:`CONFIG_BT_FIXED_PASSKEY` Kconfig option has been deprecated, replace it with the :kconfig:option:`CONFIG_BT_APP_PASSKEY` Kconfig option.

Now, if you want to use a fixed passkey for the Matter Lock NUS service, register the :c:member:`bt_conn_auth_cb.app_passkey` callback in the :c:struct:`bt_conn_auth_cb` structure.

@m-alperen-sener could you please add these changes to my PR, or add a new one with the changes?

umapraseeda · 2025-11-07T12:23:14Z

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

@@ -166,6 +166,10 @@ Bluetooth Mesh
  * Deprecated the :kconfig:option:`CONFIG_BT_MESH_NLC_PERF_CONF` and :kconfig:option:`CONFIG_BT_MESH_NLC_PERF_DEFAULT` Kconfig options.
    Existing configurations continue to work but you should migrate to individual profile options.

+* Update the LE Pairing Responder model:


Suggested change

* Update the LE Pairing Responder model:

* Updated the LE Pairing Responder model:

doc/nrf/libraries/bluetooth/mesh/vnd/images/bt_mesh_le_pair_resp.svg

m-alperen-sener

DOC fix
Rebased on sdk-nrf main

m-alperen-sener · 2025-11-07T13:58:54Z

Hi @m-alperen-sener, before merging could you check these things to be sure these changes still work:

mesh le pairing system test (https://projecttools.nordicsemi.no/bitbucket/projects/NCS-TEST/repos/test-sdk-mesh/browse/tests/mesh/samples/le_pairing)

nRF Mesh DFU mobile app manages with pairing (IOS)

Device Manager mobile app manages with pairing (IOS)

mobile app is possible to check with mesh dfu distributor sample

Tried the IOS app; it triggers pairing succesfully with le pair responder. And SMP is functional.

divipillai · 2025-11-07T14:49:40Z

include/bluetooth/mesh/vnd/le_pair_resp.h

@@ -43,11 +43,24 @@ void bt_mesh_le_pair_resp_passkey_invalidate(void);
 * By default, passkeys will be randomly generated on every new request. This function allows to use
 * pre-defined passkey instead.
 *
- * @params passkey Passkey to use for the pairing, or @ref BT_PASSKEY_INVALID to use randomly
+ * @params passkey Passkey to use for the pairing, or @ref BT_PASSKEY_RAND to use randomly


The doc build error is because of reference to this macro. The macro is defined in the Zephyr PR. This will work only after the Zephyr PR - https://github.com/nrfconnect/sdk-zephyr/pull/3466/files#diff-4538e90f4e61dd34802aa1c0a5382dc89d4df6032ec6a3dbbf4eef746ebdd488 is merged.

good to know, then I can request merge for zephyr PR in spite of error.

I have removed @ref completely

m-alperen-sener · 2025-11-10T08:21:41Z

Updated the image to fix doc fails, rebased to fix downstream failing tests.

nordicjm · 2025-11-21T09:29:22Z

include/bluetooth/mesh/vnd/le_pair_resp.h

@@ -32,22 +32,35 @@ extern "C" {
 			     _bt_mesh_le_pair_resp_op, NULL, NULL,                                 \
 			     &_bt_mesh_le_pair_resp_cb)

-/* @brief Invalidate previously used passkey.
+/** @brief Invalidate previously used passkey.


this is wrong, the top line of a multiline comment should be empty e.g. /** then the text begins on the second line, will allow as this is not adding it just changing the indent but take note for future

that was request from Carles I am confused.

https://www.doxygen.nl/manual/docblocks.html

It sound like @brief is allowed to be in the first line, if it is a base text it should start on the second line. I have check other documentation and it is aligned with that.

Manifest update to depracate and replace BT_FIXED_PADDKEY Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

BT_FIXED_PASSKEY is depracated so wee need to aling the le pair responder model with the new Kconfig BT_APP_PASSKEY usage. Adding bt_mesh_le_pair_resp_passkey_get to be able to retreive the passkey set randomly or by app. Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

BT_FIXED_PASSKEY is deprecated, thus we start using BT_APP_PASSKEY Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

CONFIG_BT_FIXED_PASSKEY has been deprecated. We switched to CONFIG_BT_APP_PASSKEY and added a migration guide entry. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>

m-alperen-sener requested review from a team as code owners November 4, 2025 16:10

NordicBuilder added manifest changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Nov 4, 2025

m-alperen-sener mentioned this pull request Nov 4, 2025

manifest: sdk-zephyr: Fixed passkey deprecation #25404

Closed

NordicBuilder requested a review from a team November 4, 2025 16:10

NordicBuilder added manifest-zephyr DNM labels Nov 4, 2025

nordicjm reviewed Nov 5, 2025

View reviewed changes

subsys/bluetooth/mesh/vnd/Kconfig Outdated Show resolved Hide resolved

PavelVPV requested changes Nov 5, 2025

View reviewed changes

include/bluetooth/mesh/vnd/le_pair_resp.h Outdated Show resolved Hide resolved

include/bluetooth/mesh/vnd/le_pair_resp.h Outdated Show resolved Hide resolved

subsys/bluetooth/mesh/vnd/le_pair_resp.c Outdated Show resolved Hide resolved

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from 2999999 to 0d6a557 Compare November 5, 2025 15:56

m-alperen-sener requested review from a team as code owners November 5, 2025 15:56

NordicBuilder added doc-required PR must not be merged without tech writer approval. and removed changelog-entry-required Update changelog before merge. Remove label if entry is not needed or already added. labels Nov 5, 2025

NordicBuilder requested review from a team November 5, 2025 15:56

m-alperen-sener commented Nov 5, 2025

View reviewed changes

PavelVPV reviewed Nov 5, 2025

View reviewed changes

ArekBalysNordic requested changes Nov 6, 2025

View reviewed changes

samples/matter/common/src/bt_nus/bt_nus_service.cpp Show resolved Hide resolved

samples/matter/common/src/bt_nus/bt_nus_service.cpp Show resolved Hide resolved

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst Outdated Show resolved Hide resolved

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from 0d6a557 to d30f085 Compare November 6, 2025 08:49

divipillai reviewed Nov 6, 2025

View reviewed changes

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from d30f085 to 27124bd Compare November 6, 2025 13:49

divipillai reviewed Nov 7, 2025

View reviewed changes

umapraseeda requested changes Nov 7, 2025

View reviewed changes

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from bfe6ea8 to 215f1ea Compare November 7, 2025 13:29

m-alperen-sener commented Nov 7, 2025

View reviewed changes

PavelVPV approved these changes Nov 7, 2025

View reviewed changes

divipillai reviewed Nov 7, 2025

View reviewed changes

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from 215f1ea to 7b54a0f Compare November 10, 2025 08:20

omkar3141 approved these changes Nov 10, 2025

View reviewed changes

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch 4 times, most recently from 12fca63 to 0d56114 Compare November 13, 2025 13:26

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch 2 times, most recently from 8308681 to 8ecddc4 Compare November 19, 2025 12:05

umapraseeda approved these changes Nov 19, 2025

View reviewed changes

divipillai approved these changes Nov 19, 2025

View reviewed changes

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch 3 times, most recently from 810b80f to 1c0d944 Compare November 20, 2025 15:28

nordicjm approved these changes Nov 21, 2025

View reviewed changes

m-alperen-sener and others added 4 commits November 21, 2025 12:30

manifest: sdk-zephyr: deprecate fixed passkey

eedc347

Manifest update to depracate and replace BT_FIXED_PADDKEY Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

sample: bluetooth: mesh: start using BT_APP_PASSKEY

c9db990

BT_FIXED_PASSKEY is deprecated, thus we start using BT_APP_PASSKEY Signed-off-by: alperen sener <alperen.sener@nordicsemi.no>

samples: matter: Align Matter NUS to APP_PASSKEY

8c7d26b

CONFIG_BT_FIXED_PASSKEY has been deprecated. We switched to CONFIG_BT_APP_PASSKEY and added a migration guide entry. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>

m-alperen-sener force-pushed the deprace_bt_fixed_appkey branch from 1c0d944 to 8c7d26b Compare November 21, 2025 11:34

NordicBuilder removed the DNM label Nov 21, 2025

rlubos merged commit 3bbf571 into nrfconnect:main Nov 21, 2025
20 of 21 checks passed

	After every pairing request, the application must invalidate the previously used passkey by calling the :c:func:`bt_mesh_le_pair_resp_passkey_invalidate` function or calling :c:func:`bt_mesh_le_pair_resp_passkey_set` with :ref:`BT_PASSKEY_RAND` value.
	After every pairing request, the application must invalidate the previously used passkey by calling the :c:func:`bt_mesh_le_pair_resp_passkey_invalidate` function or calling :c:func:`bt_mesh_le_pair_resp_passkey_set` with the ``BT_PASSKEY_RAND`` value.

		* The :kconfig:option:`CONFIG_BT_FIXED_PASSKEY` kconfig option has been deprecated, replace it with the :kconfig:option:`CONFIG_BT_APP_PASSKEY` kconfig option.
		Now, if you want to use a fixed passkey for the Matter Lock NUS service, register the ``app_passkey`` callback in the ``bt_conn_auth_cb`` structure.

	* Update the LE Pairing Responder model:
	* Updated the LE Pairing Responder model:

Deprecate BT_FIXED_APPKEY #25414

Deprecate BT_FIXED_APPKEY #25414

Uh oh!

Conversation

m-alperen-sener commented Nov 4, 2025

Uh oh!

NordicBuilder commented Nov 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NordicBuilder commented Nov 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CI Information

Inputs:

Sources:

Github labels

Outputs:

Toolchain

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

Uh oh!

github-actions bot commented Nov 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

PavelVPV left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

m-alperen-sener left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

ArekBalysNordic left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

m-alperen-sener Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alxelax commented Nov 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

m-alperen-sener left a comment

Choose a reason for hiding this comment

Uh oh!

m-alperen-sener commented Nov 7, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

NordicBuilder commented Nov 4, 2025 •

edited

Loading

NordicBuilder commented Nov 4, 2025 •

edited

Loading

github-actions bot commented Nov 4, 2025 •

edited

Loading

m-alperen-sener Nov 6, 2025 •

edited

Loading

alxelax commented Nov 7, 2025 •

edited

Loading