fix(sbom): restore usesLatestTag:true for Dakota specs

[castrojo]

PR #837 changed the Dakota specs from usesLatestTag:true to streamPrefix:\"latest\". This caused processStream() to call findRecentTagsForStream() which returns 0 tags because Dakota stopped using latest.YYYYMMDD date tags in February 2026.\n\nRestores usesLatestTag:true so processLatestTagStream() is called — which (after PR #838) now fetches :latest plus the 10 most recent commit-SHA image tags for history.\n\nWithout this: dakota-latest: found 0 recent tagged releases in every SBOM cache run."

Summary by CodeRabbit

• Chores
  • Internal script optimization for stream processing logic (no user-visible changes).

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 91d40c64-b115-4e3d-a7e8-a72279cea33e

📥 Commits

Reviewing files that changed from the base of the PR and between 644b405 and 4b8ddb1.

📒 Files selected for processing (1)

• scripts/fetch-github-sbom.js

---

📝 Walkthrough

Walkthrough

The PR updates the Dakota SBOM stream configuration in scripts/fetch-github-sbom.js to use a new :latest-tag-based processing approach. The dakota-latest and dakota-nvidia-latest stream specs now set usesLatestTag: true, routing them through dedicated latest-tag handling instead of date-stamped stream prefixes.

Changes

SBOM Dakota Latest Stream Configuration

Layer / File(s)	Summary
Dakota latest stream spec update scripts/fetch-github-sbom.js	dakota-latest and dakota-nvidia-latest entries now use usesLatestTag: true to route through processLatestTagStream, replacing the previous date-stamped streamPrefix approach with inline comments updated to document :latest tag routing behavior.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• projectbluefin/documentation#795: Introduces the usesLatestTag flow and processLatestTagStream delegation that this PR now activates for the Dakota stream specs.
• projectbluefin/documentation#837: Modifies processLatestTagStream() cache and release-seeding behavior for the same latest-tag-routed streams this PR now configures.
• projectbluefin/documentation#838: Updates processLatestTagStream() to backfill and cache multiple historical :latest-backed tags, directly supporting the routing this PR enables.

Poem

🐰 A latest tag awakens, swift and clean,
Dakota's newest builds now convene.
No more date-stamps clutter the flow,
:latest points where release winds blow.
Configuration springs forth, precise and lean! 🌱

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately describes the main change: restoring usesLatestTag:true for Dakota specs in the SBOM script.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}