renovate: get openSUSE Tumbleweed package versions from file list

[amezin]

Even though there is an "updates" repository:

https://download.opensuse.org/update/tumbleweed/x86_64/

it seems to be unused.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 820e5357-65e5-4cc3-b602-398198c65955

📥 Commits

Reviewing files that changed from the base of the PR and between bdfc7c8 and f36e994.

📒 Files selected for processing (2)

• opensuse-tumbleweed.dockerfile
• renovate.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

🧰 Additional context used

🪛 Checkov (3.3.16)

opensuse-tumbleweed.dockerfile

[low] 1-30: Ensure that HEALTHCHECK instructions have been added to container images

(CKV_DOCKER_2)

---

[low] 1-30: Ensure that a user for the container has been created

(CKV_DOCKER_3)

🔇 Additional comments (2)

renovate.json (1)

25-30: LGTM!

opensuse-tumbleweed.dockerfile (1)

3-4: LGTM!

Also applies to: 6-7, 9-10, 12-13, 16-21

---

📝 Summary

Summary by CodeRabbit

• Bug Fixes

  • Pinned key desktop environment package versions to provide more consistent and reproducible container builds.

• Maintenance

  • Added automated update tracking for the pinned openSUSE package versions.

Walkthrough

The Dockerfile pins GNOME Shell, Mutter, GJS, and VTE versions. Renovate now reads matching versions from openSUSE download data. The install step receives the pinned versions as environment variables.

Changes

Package version pinning

Layer / File(s)	Summary
Renovate-driven package pinning renovate.json, opensuse-tumbleweed.dockerfile	The Dockerfile defines Renovate-managed versions for four packages and passes them to install-suse.sh. The Renovate configuration reads release versions from openSUSE download directory JSON data.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to f36e9

The pinned versions match the installer inputs and available openSUSE entries, with no established merge-blocking risk.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: obtaining openSUSE Tumbleweed package versions from the repository file list through Renovate.
Description check	✅ Passed	The description explains why the pull request changes the package version source and is related to the changeset.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/reconfigure

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[renovate]

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your Renovate settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

---

Detected Package Files

• .github/workflows/build.yml (github-actions)
• .github/workflows/cleanup.yml (github-actions)
• .github/workflows/code-scan.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• .github/workflows/code-scan.yml (regex)
• almalinux-10.dockerfile (regex)
• alpine-3.24.dockerfile (regex)
• alpine-edge.dockerfile (regex)
• archlinux-unstable.dockerfile (regex)
• archlinux.dockerfile (regex)
• centos-10.dockerfile (regex)
• fedora-43.dockerfile (regex)
• fedora-44.dockerfile (regex)
• ubuntu-24.04.dockerfile (regex)
• ubuntu-26.04.dockerfile (regex)

Configuration Summary

Based on the default config's presets, Renovate will:

• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Run lock file maintenance (updates) early Monday mornings.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.

---

What to Expect

With your current configuration, Renovate will create 3 Pull Requests:

chore(deps): update amezin/container-registry-prune-action action to v0.4.5

• Schedule: ["at any time"]
• Branch name: renovate/amezin-container-registry-prune-action-0.x
• Merge into: master
• Upgrade amezin/container-registry-prune-action to 4b4965427da5aa037005aa1849921efda619eaa9

chore(deps): update amezin/detect-changes-action action to v2.2.5

• Schedule: ["at any time"]
• Branch name: renovate/amezin-detect-changes-action-2.x
• Merge into: master
• Upgrade amezin/detect-changes-action to 3e2f995c5422ad75a989d22ab9b39cf18c53a07e

chore(deps): update docker/setup-buildx-action action to v4.4.1

• Schedule: ["at any time"]
• Branch name: renovate/docker-setup-buildx-action-4.x
• Merge into: master
• Upgrade docker/setup-buildx-action to f87e5991a6d7451dcb8d9637bfbc97413f497069

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.