Skip to content

docs(miopen): add ROCm 10.0.0 changelog section - #10208

Merged
JonathanLichtnerAMD merged 3 commits into
developfrom
users/jlichtne/ALMIOPEN-2364-update-miopen-changelog-7.15
Aug 13, 2026
Merged

JonathanLichtnerAMD merged 3 commits into
developfrom
users/jlichtne/ALMIOPEN-2364-update-miopen-changelog-7.15

Conversation

@JonathanLichtnerAMD

@JonathanLichtnerAMD JonathanLichtnerAMD commented Jul 31, 2026 •

Copy link
Copy Markdown
Contributor

JIRA ID: ALMIOPEN-2364

Motivation

ROCm 7.15 has been renamed to ROCm 10.0, and MIOpen 3.6.0 is the corresponding
release. projects/miopen/CHANGELOG.md needs a new version section documenting
what changed for downstream users, release-notes tooling, and packagers between
MIOpen 3.5.2 (ROCm 7.14.0) and MIOpen 3.6.0 (ROCm 10.0.0), consistent with the
changelog's existing per-release format.

Technical Details

Risk Assessment

Single file (projects/miopen/CHANGELOG.md), 17 lines added, 0 removed, no code
or build-system changes.

Risk Level: 🟢 Low

Impacted Components

  • projects/miopen/CHANGELOG.md only — no source, kernel, solver, build, or test
    files are touched.

Potential Side Effects

  • None functionally. The only observable effect is the new changelog text itself;
    no build artifacts, APIs, or runtime behavior change.
  • Cosmetic risk only: if any release-notes/packaging tooling parses this file
    programmatically, it should be checked for compatibility with the new section,
    though the added section strictly follows the existing heading/bullet
    conventions used by all prior sections in the file.

Mitigation Steps

Test Plan

No functional tests apply — this is a documentation-only change to a Markdown
changelog file. Verification consisted of manually reviewing the diff against the
existing file's structure and confirming the new section's heading hierarchy and
bullet formatting match every other version section in CHANGELOG.md.

Test Result

  • git diff origin/develop...HEAD --stat confirms the change is scoped to exactly
    one file (projects/miopen/CHANGELOG.md, +17/-0).
  • Visual/manual review confirms the new ## MIOpen 3.6.0 for ROCm 10.0.0 section
    renders as valid Markdown consistent with surrounding sections. No build or CI
    run is applicable to a docs-only change.

Add a MIOpen 3.6.0 for ROCm 10.0.0 section documenting the
changelog-worthy changes present in release/therock-10.0 that are not in
release/therock-7.14.

JIRA ID: ALMIOPEN-2364

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@therock-pr-bot

therock-pr-bot Bot commented Jul 31, 2026 •

Copy link
Copy Markdown

✅ All Checks Passed — Ready for Review

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

🎉 All checks passed! This PR is ready for review.

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

🙋 Wish to Override Policy?

@therock-pr-bot

Copy link
Copy Markdown

🎉 All checks passed! This PR is ready for review.

An additional MIOpen fix (#10188, cherry-picked as #10359) landed on
release/therock-10.0 after the 3.6.0 changelog section was first
written. It is not present on release/therock-7.14, so it belongs in
the 7.14->10.0 delta this section documents.

JIRA ID: ALMIOPEN-2364

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@SreecharanGundaboluAMD SreecharanGundaboluAMD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@JonathanLichtnerAMD
JonathanLichtnerAMD merged commit baf3e19 into develop Aug 13, 2026
48 checks passed
@JonathanLichtnerAMD
JonathanLichtnerAMD deleted the users/jlichtne/ALMIOPEN-2364-update-miopen-changelog-7.15 branch August 13, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants