Skip to content

chore: update content from upstream sources #554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
+230 −261
Open

chore: update content from upstream sources #554

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions public/stream-versions.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
# Stream version information for Bluefin releases
# This file contains the latest version information for each stream
# Data is sourced from the most recent changelogs in ublue-os/bluefin and ublue-os/bluefin-lts repositories
# Last updated: 2026-03-31
# Last updated: 2026-05-02

lts:
base: "CentOS Stream 10"
gnome: "48.4-1"
kernel: "6.12.0-172"
mesa: "25.2.5-3"
nvidia: "590.44.01-1"
hwe: "6.17.8-200.fc42"
gnome: "unknown"
kernel: "unknown"
mesa: "unknown"
nvidia: "unknown"
hwe: "unknown"
Comment on lines +8 to +12
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 2, 2026

Choose a reason for hiding this comment

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

⚠️ 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.

stable:
base: "Fedora 43"
gnome: "49.5-1"
kernel: "6.18.13-200"
gnome: "49.6-1"
kernel: "6.19.12-200"
mesa: "25.3.6-6"
nvidia: "595.58.03-1"
nvidia: "595.71.05-1"
Loading