Repository navigation
Conversation
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>
lbetz
approved these changes
Nov 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Short description
#245 breaks the build because it moves the OpenVox 8 parts of the image to OpenVox 9.
build_versions.yamlhas one build line per OpenVox major, and the release 8 and release 9 lines use the same Renovate depNames. For the release 8openvoxgem entry, and for the Containerfile defaults, Renovate proposes a major update (8.34.0 → 9.5.0). That lands on the samerenovate/openvox-9.xbranch as the genuine 9.3.0 → 9.5.0 update for the release 9 line.This PR disables major updates for
openvox,openvox-serverandopenvoxdb, so each pinned version stays within its current major. A new major gets a new build line, added by hand. The rule replaces the blanketallowedVersions: /^8\./on thecustom.voxpupuli-artifactsdatasource, which also stopped the release 9openvox-server/openvoxdbversions from ever being updated.The change is made in
.sync.yml..github/renovate.jsoncis regenerated to match, and it is byte-identical to what thecontainer_modulesync_configstemplate renders.A local
renovate --platform=local --dry-run=lookuprun shows the difference:renovate/openvox-9.xopenvox8.34.0 → 9.5.0 (both Containerfiles, release 8 line) and 9.3.0 → 9.5.0 (release 9 line)renovate/openvoxdb-9.x/^8\./)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:
Signed-off-byannotation to each of my commitsGenerated-byorAssisted-byannotations to each of my commits created with the help of an AI agent🤖 Generated with Claude Code