How do I install the Update Redhat Family Image Releases skill?

Run npx skillmds@latest add tomevault-io/update-redhat-family-image-releases in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Redhat Family Image Releases safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Redhat Family Image Releases?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Redhat Family Image Releases free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Redhat Family Image Releases?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Redhat Family Image Releases by tomevault-io

Name: Update Redhat Family Image Releases
Author: tomevault-io

Update Redhat Family Image Releases

Update Rocky Linux, AlmaLinux, CentOS Stream, Fedora, or all Red Hat-family container image release files in this repository. Use when requests mention `update rocky`, `update almalinux`, `update centos stream`, `update fedora`, `update redhat-family distributions`, or otherwise ask to bump release RPMs under `image-scripts/images/*`. Follow upstream HTTP repo directory listings, update the matching `build.sh` files, run `./test-runner.sh test image-scripts/test@image-name` for each changed image, and keep commits split per changed image directory. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Update Red Hat Family Image Releases

Overview

Update the release-related lines in image-scripts/images/{rocky-*,almalinux-*,centos-*-stream,fedora-*}/build.sh by reading the upstream HTTP package listings and then verify each changed image with its matching image-scripts/test@... test.

Quick Start

From repo root, run ruby skills/update-redhat-family-image-releases/scripts/discover_release_updates.rb <scope>.
Edit the build.sh files reported by the script.
Run ./test-runner.sh test image-scripts/test@<image-name> for every changed image.
Keep one commit per changed image directory, for example image-scripts: update rocky-9 to <ver>.

Use rocky, almalinux, centos-stream, fedora, or all for <scope>.

Workflow

Select Targets

rocky: update every image-scripts/images/rocky-*
almalinux: update every image-scripts/images/almalinux-*
centos-stream: update every image-scripts/images/centos-*-stream
fedora: update every image-scripts/images/fedora-*
all: update all of the above

Discover Exact Versions

Never guess RPM filenames or point releases.
Use scripts/discover_release_updates.rb to read the current repo state and the upstream directory listings.
Read references/release-workflow.md only when you need the per-family URL and variable rules.
If a stable Fedora image is no longer on the live Fedora releases mirror, treat it as stale repo content to remove instead of chasing archive URLs.

Edit Only Release-Related Lines

Rocky: update POINTVER and RELEASE.
AlmaLinux 9/10/future: update POINTVER and RELEASE.
AlmaLinux 8: update POINTVER and RELEASE, but leave BASEURL and UPDATES on ${RELVER} unless the upstream layout changed.
CentOS Stream: update RELEASE to the highest centos-stream-release-<POINTVER>-*.rpm in the major stream's BaseOS packages listing. If the newest RPM embeds a different <POINTVER> than the current file, update POINTVER to match it. Keep BASEURL and UPDATES on <major>-stream unless the upstream layout changed.
Fedora stable: update the shared release suffix in the four fedora-release* lines.
Fedora rawhide: update RAWHIDE_RELVER; keep the four RELEASE lines consistent with it.

Verify Every Changed Image

Run ./test-runner.sh test image-scripts/test@<image-name> for each changed image directory.
If osvm or test-runner has local changes, run nix develop .#test-runner -c bundle exec ./test-runner/bin/test-runner test image-scripts/test@<image-name> from repo root so the tests use the local code.
Do not skip a changed image because another image in the same family passed.

Keep Commits Focused

Make one commit per changed image directory, not one commit for the whole family sweep.
Use subjects such as image-scripts: update rocky-9 to <ver>, image-scripts: update centos-9-stream release to <ver>, image-scripts: update almalinux-10 to <ver>, or image-scripts: update fedora-rawhide release to <ver>.

Source: vpsfreecz/vpsadminos — distributed by TomeVault.

---name: update-redhat-family-image-releasesdescription: Update Rocky Linux, AlmaLinux, CentOS Stream, Fedora, or all Red Hat-family container image release files in this repository. Use when requests mention `update rocky`, `update almalinux`, `update centos stream`, `update fedora`, `update redhat-family distributions`, or otherwise ask to bump release RPMs under `image-scripts/images/*`. Follow upstream HTTP repo directory listings, update the matching `build.sh` files, run `./test-runner.sh test image-scripts/test@image-name` for each changed image, and keep commits split per changed image directory. Use when this capability is needed.---# Update Red Hat Family Image Releases## OverviewUpdate the release-related lines in `image-scripts/images/{rocky-*,almalinux-*,centos-*-stream,fedora-*}/build.sh` by reading the upstream HTTP package listings and then verify each changed image with its matching `image-scripts/test@...` test.## Quick Start1. From repo root, run `ruby skills/update-redhat-family-image-releases/scripts/discover_release_updates.rb <scope>`.2. Edit the `build.sh` files reported by the script.3. Run `./test-runner.sh test image-scripts/test@<image-name>` for every changed image.4. Keep one commit per changed image directory, for example `image-scripts: update rocky-9 to <ver>`.Use `rocky`, `almalinux`, `centos-stream`, `fedora`, or `all` for `<scope>`.## Workflow### Select Targets- `rocky`: update every `image-scripts/images/rocky-*`- `almalinux`: update every `image-scripts/images/almalinux-*`- `centos-stream`: update every `image-scripts/images/centos-*-stream`- `fedora`: update every `image-scripts/images/fedora-*`- `all`: update all of the above### Discover Exact Versions- Never guess RPM filenames or point releases.- Use `scripts/discover_release_updates.rb` to read the current repo state and the upstream directory listings.- Read [references/release-workflow.md](references/release-workflow.md) only when you need the per-family URL and variable rules.- If a stable Fedora image is no longer on the live Fedora releases mirror, treat it as stale repo content to remove instead of chasing archive URLs.### Edit Only Release-Related Lines- Rocky: update `POINTVER` and `RELEASE`.- AlmaLinux 9/10/future: update `POINTVER` and `RELEASE`.- AlmaLinux 8: update `POINTVER` and `RELEASE`, but leave `BASEURL` and `UPDATES` on `${RELVER}` unless the upstream layout changed.- CentOS Stream: update `RELEASE` to the highest `centos-stream-release-<POINTVER>-*.rpm` in the major stream's BaseOS packages listing. If the newest RPM embeds a different `<POINTVER>` than the current file, update `POINTVER` to match it. Keep `BASEURL` and `UPDATES` on `<major>-stream` unless the upstream layout changed.- Fedora stable: update the shared release suffix in the four `fedora-release*` lines.- Fedora rawhide: update `RAWHIDE_RELVER`; keep the four `RELEASE` lines consistent with it.### Verify Every Changed Image- Run `./test-runner.sh test image-scripts/test@<image-name>` for each changed image directory.- If `osvm` or `test-runner` has local changes, run `nix develop .#test-runner -c bundle exec ./test-runner/bin/test-runner test image-scripts/test@<image-name>` from repo root so the tests use the local code.- Do not skip a changed image because another image in the same family passed.### Keep Commits Focused- Make one commit per changed image directory, not one commit for the whole family sweep.- Use subjects such as `image-scripts: update rocky-9 to <ver>`, `image-scripts: update centos-9-stream release to <ver>`, `image-scripts: update almalinux-10 to <ver>`, or `image-scripts: update fedora-rawhide release to <ver>`.---> Source: [vpsfreecz/vpsadminos](https://github.com/vpsfreecz/vpsadminos) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions