Skip to content

fix(renovate): keep each OpenVox release line within its major - #246

Open
bootc wants to merge 1 commit into
OpenVoxProject:mainfrom
bootc:fix/renovate-major-lines
Open

bootc wants to merge 1 commit into
OpenVoxProject:mainfrom
bootc:fix/renovate-major-lines

Conversation

@bootc

@bootc bootc commented Nov 21, 2026 •

Copy link
Copy Markdown
Member

Short description

#245 breaks the build because it moves the OpenVox 8 parts of the image to OpenVox 9. build_versions.yaml has one build line per OpenVox major, and the release 8 and release 9 lines use the same Renovate depNames. For the release 8 openvox gem entry, and for the Containerfile defaults, Renovate proposes a major update (8.34.0 → 9.5.0). That lands on the same renovate/openvox-9.x branch as the genuine 9.3.0 → 9.5.0 update for the release 9 line.

This PR disables major updates for openvox, openvox-server and openvoxdb, so each pinned version stays within its current major. A new major gets a new build line, added by hand. The rule replaces the blanket allowedVersions: /^8\./ on the custom.voxpupuli-artifacts datasource, which also stopped the release 9 openvox-server/openvoxdb versions from ever being updated.

The change is made in .sync.yml. .github/renovate.jsonc is regenerated to match, and it is byte-identical to what the container_modulesync_configs template renders.

A local renovate --platform=local --dry-run=lookup run shows the difference:

Before After
renovate/openvox-9.x openvox 8.34.0 → 9.5.0 (both Containerfiles, release 8 line) and 9.3.0 → 9.5.0 (release 9 line) Only 9.3.0 → 9.5.0 (release 9 line)
renovate/openvoxdb-9.x — (blocked by /^8\./) 9.2.0 → 9.2.1 (release 9 line)

Once this is merged, Renovate should rebase #245 down to the release 9 change alone, or close it and open a fresh PR.

Checklist

I have:

🤖 Generated with Claude Code

build_versions.yaml has one build line per OpenVox major release, and
the release 8 and release 9 lines share the same Renovate depNames. For
the release 8 entries (and the Containerfile defaults, which are also on
8), Renovate proposed a major update to 9.x. That landed on the same
renovate/openvox-9.x branch as the genuine 9.x minor update, moving the
OpenVox 8 parts of the image to OpenVox 9 and breaking the build (OpenVoxProject#245).

Disable major updates for openvox, openvox-server and openvoxdb, so every
pinned version stays within its current major; a new major gets a new
build line, added by hand. This replaces the blanket allowedVersions
/^8\./ rule on the voxpupuli-artifacts datasource, which also stopped the
release 9 openvox-server and openvoxdb versions from ever being updated.

The rule goes in .sync.yml, with .github/renovate.jsonc regenerated to
match the modulesync template output.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Chris Boot <bootc@boo.tc>
@bootc
bootc requested a review from a team as a code owner November 21, 2026 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants