Skip to content

Restrict Curios Renovate updates to matching MC versions - #99

Merged
rubensworks merged 1 commit into
masterfrom
claude/pr-96-ci-failure-y3i1cz
Sep 27, 2026
Merged

rubensworks merged 1 commit into
masterfrom
claude/pr-96-ci-failure-y3i1cz

Conversation

@rubensworks

Copy link
Copy Markdown
Member

Curios versions end with +<mc version> (e.g. 15.0.0+26.1.2), but Renovate compared them only by the leading number. So it proposed 17.0.0-beta+26.3 for both the 1.21.1 and 26.1.2 packs in #94.

This adds per-MC allowedVersions rules for curios-neoforge, the same approach already used for TheOneProbe, TerraBlender and Architectury. Checked against the Curios maven metadata:

Packs Pattern Matches
1.21.1 /\+1\.21\.1$/ 9.2.0 ... 9.5.1+1.21.1
26.1* /\+26\.1(\.\d+)?$/ 15.0.0-beta.1+26.1, 15.0.0-beta.2+26.1.2, 15.0.0+26.1.2
26.3* /\+26\.3(\.\d+)?$/ 17.0.0-beta+26.3, 17.0.0-beta.2+26.3

renovate-config-validator passes.

Note: the 1.21.1 all-deps pack currently pins 7.4.3+1.20.4, a 1.20.4 build. With this rule, Renovate will propose 9.5.1+1.21.1 for it.

Once this is merged, #94 should be closed or updated by Renovate.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RR4D2pnFdhtTzJpTf9EhqK


Generated by Claude Code

Curios versions end with +<mc version>, so without this Renovate proposed
26.3 builds for the 1.21.1 and 26.1.2 packs (e.g. #94).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RR4D2pnFdhtTzJpTf9EhqK
@rubensworks
rubensworks merged commit 818ab32 into master Sep 27, 2026
61 checks passed
@rubensworks
rubensworks deleted the claude/pr-96-ci-failure-y3i1cz branch September 27, 2026 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants