A0226750 tag v2026 01 00

[nsaulnier-ti]

No description provided.

[qodo-code-review]

Review Summary by Qodo

OpenPRU v2026.01.00 release with CCS improvements

✨ Enhancement 📝 Documentation

Walkthroughs

Description

• Release v2026.01.00 with major CCS example.projectspec overhaul
• Remove MCU+ SDK dependencies from PRU-only CCS projects
• Add AM62x CCS support and standardize project configurations
• Update release notes with supported processors and SDK compatibility
• Update tagging checklist with new metadata version process

Diagram

flowchart LR
  A["OpenPRU v2026.01.00"] --> B["Update .metadata version"]
  A --> C["CCS Improvements"]
  C --> D["Remove MCU+ SDK dependencies"]
  C --> E["Standardize project configs"]
  C --> F["Add AM62x support"]
  A --> G["Documentation Updates"]
  G --> H["Release notes"]
  G --> I["Tagging checklist"]

Loading

File Changes

1. .metadata/.tirex/package.tirex.json ⚙️ Configuration changes +1/-1

Update OpenPRU version to 2026.01.00

• Update OpenPRU version from 01.00.00.00 to 2026.01.00
• Align metadata with new release tag format

.metadata/.tirex/package.tirex.json

---

2. docs/release_notes.md 📝 Documentation +69/-2

Add v2026.01.00 release notes with major updates

• Add comprehensive v2026.01.00 release notes section
• Document major CCS example.projectspec overhaul and MCU+ SDK dependency removal
• List supported processors (AM243x, AM261x, AM263Px, AM263x, AM62x, AM64x)
• Include SDK compatibility matrix for different device families
• Document additional updates, bugfixes, and GitHub CI improvements
• Add links to PRU Academy resources for multiple device families

docs/release_notes.md

---

3. docs/tagging_checklist.md 📝 Documentation +20/-3

Add metadata and CI workflow update steps

• Add new section for updating CI matrix SDK versions in GitHub workflows
• Add new section for updating .metadata version in package.tirex.json
• Update table of contents to reflect new checklist items
• Clarify the metadata update process for release tagging

docs/tagging_checklist.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2)   📘 Rule violations (2)   📎 Requirement gaps (0)   🎨 UX Issues (0)

🐞\ ≡ Correctness (1) ⚙ Maintainability (1)

📘\ ⚙ Maintainability (2)

1. Long Academy links exceed limits 📘 ⚙

Description

New Markdown lines contain very long inline URLs that likely exceed the 129-column hard limit and
reduce render stability/readability. This violates the repo formatting and documentation readability
requirements.

Code

docs/release_notes.md[R78-81]

+[PRU Academy for AM26x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AA63DGBS9m5Kf5FElQrpyQ__AM26X-ACADEMY__t0CaxbG__LATEST)
+[PRU Academy for AM243x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM24X-ACADEMY__ZPSnq-h__LATEST)
+[PRU Academy for AM62x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AEIJm0rwIeU.2P1OBWwlaA__AM62-ACADEMY__uiYMDcq__LATEST)
+[PRU Academy for AM64x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM64-ACADEMY__WI1KRXP__LATEST)

Evidence

PR Compliance requires source lines to stay within the configured length limits and documentation to
remain render-stable/readable. The newly added Academy links are long single-line inline URLs, which
exceed these limits.

docs/release_notes.md[78-81]
Best Practice: Repository guidelines
Best Practice: Learned patterns

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
New documentation lines include very long inline URLs, likely exceeding the 129-column hard limit and harming markdown readability.

## Issue Context
Release notes add several Academy links as single-line inline URLs.

## Fix Focus Areas
- docs/release_notes.md[78-81]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. e.g. used in docs 📘 ⚙

Description

New documentation text uses the Latin abbreviation e.g. instead of writing out for example. This
violates the documentation wording standard.

Code

docs/tagging_checklist.md[87]

+Update the OpenPRU version field to the new release tag (e.g. `2026.01.00`) in

Evidence

The checklist explicitly bans e.g. and requires using standard words such as for example. The
added sentence contains e.g..

docs/tagging_checklist.md[87-87]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The updated checklist uses `e.g.` which is disallowed.

## Issue Context
Documentation should use `for example` instead of `e.g.`.

## Fix Focus Areas
- docs/tagging_checklist.md[87-87]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

3. Broken checklist TOC link 🐞 ≡

Description

In docs/tagging_checklist.md, the TOC links to #update-ci-matrix-sdk-versions, but the actual
section header is “Update SDK versions in Github workflows”, so the TOC entry won’t navigate to the
intended section.

Code

docs/tagging_checklist.md[7]

+[Update CI matrix SDK versions](#update-ci-matrix-sdk-versions)

Evidence

The TOC anchor points to a fragment that does not match the auto-generated anchor from the actual
section header, so the link will be broken when rendered on GitHub.

docs/tagging_checklist.md[6-10]
docs/tagging_checklist.md[77-84]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The TOC entry in `docs/tagging_checklist.md` points to `#update-ci-matrix-sdk-versions`, but the section header is `## Update SDK versions in Github workflows`, which will not generate that anchor on GitHub.

## Issue Context
GitHub Markdown auto-generates header anchors from the header text (lowercased, spaces to hyphens, punctuation removed).

## Fix Focus Areas
- docs/tagging_checklist.md[6-10]
- docs/tagging_checklist.md[77-84]

## Suggested fix
Choose one:
1) Update the TOC link target to `#update-sdk-versions-in-github-workflows`.
2) Rename the section header to `## Update CI matrix SDK versions` so the generated anchor matches the TOC.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

4. TOC links run together 🐞 ⚙

Description

In docs/release_notes.md, the newly added TOC links don’t use a list or hard line breaks, so
multiple links will render on the same line and reduce TOC readability.

Code

docs/release_notes.md[R12-14]

+[v2026.01.00](#v20260100)
+[v2026.00.00](#v20260000)
+[v2025.00.00](#v20250000)

Evidence

The existing TOC lines end with Markdown hard-break spacing, but the new lines do not; in Markdown,
newlines inside a paragraph without hard breaks are rendered as spaces, so consecutive links will
appear on one line.

docs/release_notes.md[9-15]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The release-note TOC entries for v2026.01.00/v2026.00.00/v2025.00.00 are plain lines without list markers or hard line breaks, so they will render as a single line of links.

## Issue Context
In Markdown, a newline inside a paragraph is treated as a space unless you use a list (`- ...`) or a hard line break (two trailing spaces) or blank lines.

## Fix Focus Areas
- docs/release_notes.md[9-15]

## Suggested fix
Convert the TOC block to a proper bullet list (preferred), or add `  ` to the end of each TOC link line for consistent hard line breaks.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[pratheesh-ti]

Will need to fix broken links in #133 before merging this and tagging @dhavaljk @manojKoppolu