chore: update content from upstream sources

[github-actions]

🤖 Automated Content Update

This PR contains automated updates from upstream data sources:

Growth Chart

• Updated src/assets/svg/growth_bluefins.svg with latest data from ublue-os/countme
• Chart shows Bluefin installation growth metrics
• Colors adjusted for dark theme compatibility

Stream Versions

• Updated public/stream-versions.yml with latest version information
• Data sourced from the most recent release changelogs:
  • ublue-os/bluefin (for GTS and Stable streams)
  • ublue-os/bluefin-lts (for LTS stream)

Dakota Versions

• Updated public/dakota-versions.json release metadata
• Data sourced from latest projectbluefin/dakota release tag

Review Notes

• This is an automated daily update
• Please verify the data looks correct before merging
• Both files are used by the website to display current information

---

This PR was automatically created by the update-content workflow.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Updated YAML manifest public/stream-versions.yml: comment timestamp set to 2026-05-06. In lts several version fields (gnome, kernel, mesa, nvidia, hwe) were set to "unknown" while lts.base remains CentOS Stream 10. In stable, gnome, kernel, and nvidia version strings were bumped; stable.base and stable.mesa unchanged.

Changes

Version Manifest Update

Layer / File(s)	Summary
Metadata public/stream-versions.yml	# Last updated comment changed to 2026-05-06.
LTS stream content public/stream-versions.yml	lts.gnome, lts.kernel, lts.mesa, lts.nvidia, and lts.hwe set to "unknown"; lts.base remains CentOS Stream 10.
Stable stream content public/stream-versions.yml	stable.gnome updated to 49.6-1; stable.kernel updated to 6.19.12-200; stable.nvidia updated to 595.71.05-1; stable.base (Fedora 43) and stable.mesa (25.3.6-6) unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I hop through YAML, gentle and spry,
Timestamps nudged under an open sky.
LTS goes dark, stable steps ahead,
A tiny change where versions tread. 🐇✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update content from upstream sources' is vague and overly generic, using non-descriptive language that does not convey specific information about the actual changes being made.	Consider using a more specific title like 'chore: update stream versions and growth chart from upstream sources' to better reflect the actual file changes and improvements made.

✅ Passed checks (4 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch automated/update-content

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@public/stream-versions.yml`:
- Around line 8-12: The stream-versions.yml shows LTS package versions set to
"unknown" because the changelog parser expects a `### Major packages` table that
bluefin-lts release notes lack; update the generator (the changelog parsing
logic) so that when the `Major packages` section/table is missing it either (a)
falls back to parsing alternative headings/rows commonly used in bluefin-lts
(e.g., plain lists or other headers), or (b) returns null/empty values and emits
a clear warning instead of the literal "unknown" so the UI can handle it
gracefully; locate and update the changelog parser code path that looks for the
`Major packages` header and adjust its detection and fallback behavior
accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 28cdc696-34fb-467c-bcb4-f0b132bad12b

📥 Commits

Reviewing files that changed from the base of the PR and between 3e445ab and 0057c4a.

⛔ Files ignored due to path filters (1)

• src/assets/svg/growth_bluefins.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• public/stream-versions.yml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

for repo in ublue-os/bluefin-lts ublue-os/bluefin; do
  echo "=== ${repo} latest release ==="
  json="$(curl -fsSL "https://api.github.com/repos/${repo}/releases?per_page=1")"

  echo "$json" | jq -r '.[0] | "tag: \(.tag_name)\npublished_at: \(.published_at)"'
  body="$(echo "$json" | jq -r '.[0].body // ""')"

  echo "--- Parsed package rows present in release notes ---"
  printf '%s\n' "$body" | grep -nE '^### Major packages|^### Major GDX packages|^\| \*\*(Kernel|Gnome|Mesa|Nvidia|HWE Kernel)\*\* \|' || true
  echo
done

Repository: projectbluefin/website

Length of output: 533

---

LTS package versions are "unknown" because the release notes lack the required package table; update release notes or generator before merge.

Lines 8-12 show all LTS fields set to "unknown". The generator's changelog parser expects a structured package table in release notes (like ### Major packages with formatted rows), but the bluefin-lts release notes don't contain this section. This causes the fallback to trigger, exposing unknown values in the UI for LTS users. Either update the LTS release notes with the expected package table format, or adjust the generator to handle this release notes structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@public/stream-versions.yml` around lines 8 - 12, The stream-versions.yml
shows LTS package versions set to "unknown" because the changelog parser expects
a `### Major packages` table that bluefin-lts release notes lack; update the
generator (the changelog parsing logic) so that when the `Major packages`
section/table is missing it either (a) falls back to parsing alternative
headings/rows commonly used in bluefin-lts (e.g., plain lists or other headers),
or (b) returns null/empty values and emits a clear warning instead of the
literal "unknown" so the UI can handle it gracefully; locate and update the
changelog parser code path that looks for the `Major packages` header and adjust
its detection and fallback behavior accordingly.