[marifamd]

Motivation

ROCm 10.0 is being cut this month from release/therock-10.0. This opens the next development cycle: it adds the 10.1.0 changelog section and bumps the library minor version to 27.1.0.

While opening the section, the 10.0.0 changelog on develop was audited against the 10.0 release branch. Two entries on develop are not in release/therock-10.0, so they were never going to ship in 10.0 and are moved into 10.1.0.

Technical Details

• Bump AMDSMI_LIB_VERSION_MINOR 0 -> 1 in include/amd_smi/amdsmi.h (27.1.0).
• Add the ## amd_smi_lib for ROCm 10.1.0 section.
• Move the two 10.0.0 entries absent from release/therock-10.0 into 10.1.0:
  • amd-smi set -L/--clk-limit <clk> max cap-enforcement fix -> Resolved Issues
  • UUID -> CUID deprecation note -> Upcoming Changes
• The audit used the release branch's own changelog (25 entries) rather than git blame. Blame mis-attributes 16 entries because the unified-ABI sync commit rewrote those lines; the underlying changes are in 10.0 and correctly stay under 10.0.0. After the move, the 10.0.0 section matches the 10.0 release entry set exactly.
• Two pre-existing 10.0.0 nits found while validating for release are also fixed: the stray ### Fixed heading is folded into ### Resolved Issues, and missing two-space line breaks are added to affected headline bullets.

JIRA ID

N/A

Test Plan

Changelog-only + version-macro change; no runtime behavior change. Validated the 10.1.0 and 10.0.0 sections against the changelog conventions (allowed subsection headings, two-space line breaks on headline bullets, no JIRA IDs in entry text) and confirmed the 10.0.0 entry set matches release/therock-10.0.

Test Result

• Taxonomy check: clean (only allowed subsection headings)
• Format check: clean (headline bullets keep their two-space line breaks)
• JIRA-in-text check: clean
• 10.0.0 vs release/therock-10.0: identical entry set (25 entries)
• pre-commit hooks: passed

Submission Checklist

• Changelog updated (this PR is the changelog change)
• Followed Conventional Commits (chore(amdsmi): ...) and signed off
• Unit tests: N/A (changelog + version-macro bump; the PR-bot unit-test gate does not apply to a release-open chore)

[therock-pr-bot]

❌ PR Check — Action Required

Check	Status	Details
📝 PR Description	❌ Fail	Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword. Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples: • JIRA ID : TESTAUTO-6039 • JIRA ID - #330 • JIRA ID #330 • JIRA ID (on separate line) ROCM-25757 • ISSUE ID : TESTUTO-3334 • ISSUE ID #3334 • ISSUE ID - TESTAUTO-3433 • ISSUE ID (on separate line) AIRUNTIME-2352 • ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234 • Closes #10 • Fixes octo-org/octo-repo#100 • Resolves: #123 • #123 • https://github.com/<org_name>/<repo_name>/issues/123 Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	⚠️ Warning	Error: Source/code files changed without an accompanying unit test. Expected: add at least one test file named like test_<name>.py / test_<name>.cpp (or <name>_test.*). Current: code file(s) changed: projects/amdsmi/include/amd_smi/amdsmi.h; no test file found
🔎 pre-commit	⏳ Pending	⏳ Still running…
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

• ❌ PR Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

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

🙋 Wish to Override Policy?

[therock-pr-bot]

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

• ❌ PR Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.