[pmoutsias-amd]

This 1 CHANGELOG entry sits in release sections, but the code was merged to develop after release/therock-10.2 forked from develop at commit 2a8fffb7d64c (merged 2026-10-14) and is not on that branch. This moves it into ## rocm-dbgapi-0.84.0 for ROCm-X, under the matching subsections.

• Unit & feature tests infrastructure #12199 (merged 2026-10-28, after the 2026-10-14 fork commit, and its merge commit is not on release/therock-10.2), moved from the rocm-dbgapi-0.82.1 for ROCm-10.2 section:

  • A CMake based GoogleTest and GMock unit test suite under test/, controlled
    by the new ENABLE_TESTS and ENABLE_UNIT_TESTS options (both off by
    default). Building the suite requires GoogleTest and GMock, provided by
    either a GTest::* providing parent project or a system install. Pass
    -DENABLE_TESTS=ON to opt in. See test/README.md for details.

Only the CHANGELOG is changed. Version macros are left to the component owners.

JIRA ID : AIROCDOC-4467

[therock-pr-bot]

✅ All Policy Checks Passed

Check	Status	Details
📝 PR Description	✅ Pass	—
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	PR does not contain code files — Unit Test auto-passed
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

🎉 All policy checks passed!

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

🙋 Wish to Override Policy?

[lumachad]

@pmoutsias-amd The RTD Docs Sync job seems to be failing. Could you please check what's going on?

[lumachad]

The change itself is OK. Thanks for fixing it.

[alexxu-amd]

@pmoutsias-amd The RTD Docs Sync job seems to be failing. Could you please check what's going on?

Shouldn't worry about it, the pipeline is meant to triggered by live docs branches, which is identified by docs/ prefix. The feature branch coincidentally has the same prefix and since it's not live docs, sync pipeline reported a branch not found error.

[lumachad]

@pmoutsias-amd The RTD Docs Sync job seems to be failing. Could you please check what's going on?

Shouldn't worry about it, the pipeline is meant to triggered by live docs branches, which is identified by docs/ prefix. The feature branch coincidentally has the same prefix and since it's not live docs, sync pipeline reported a branch not found error.

Thanks for the input. Should we skip this job in rocm-systems then or at least make it so it doesn't cause a misleading failure?