renovate: disable maxMajorIncrement for Arch Linux images

[amezin]

No description provided.

[renovate]

Reconfigure PR Results

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

---

Detected Package Files

• .github/workflows/aur-publish.yml (github-actions)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/master.yml (github-actions)
• .github/workflows/ci.yml (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 GitHub.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
• Update _VERSION environment variables in GitHub Action files.

---

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): update ghcr.io/archlinux/archlinux docker tag to v20260202

• Schedule: ["at any time"]
• Branch name: renovate/ghcr.io-archlinux-archlinux
• Merge into: master
• Upgrade ghcr.io/archlinux/archlinux to sha256:be812dc69c6d0ae55fa3bd04fc55d4aad1732f5e6a16999d427ba638b7fdb92b

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated dependency management configuration to control major version increments, ensuring more stable updates for a specific package. This restricts automatic major version updates to maintain system stability.

Walkthrough

A new configuration field maxMajorIncrement: 0 is added to the renovate.json packageRules entry for the ghcr.io/archlinux/archlinux package to prevent major version increments. This is a configuration-only modification with no functional logic changes.

Changes

Cohort / File(s)	Summary
Renovate Configuration renovate.json	Added maxMajorIncrement: 0 to the packageRules entry for matchPackageNames: ghcr.io/archlinux/archlinux to constrain major version updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author; this is a very lenient check that only fails when description is completely off-topic.	Consider adding a brief description explaining why maxMajorIncrement: 0 is being set for Arch Linux images to provide context for reviewers.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding maxMajorIncrement: 0 configuration for Arch Linux images in renovate.json.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate/reconfigure

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46be552 and 094ac77.

📒 Files selected for processing (1)

• renovate.json

🔇 Additional comments (1)

renovate.json (1)

18-18: Verify: maxMajorIncrement: 0 allows unlimited major upgrades, not disables them.

According to the Renovate documentation, "allows unlimited major version upgrades by setting maxMajorIncrement to 0."

The PR title says "disable maxMajorIncrement" but setting it to 0 actually removes the limit, allowing Renovate to propose any major version jump. If the intent is to prevent major version increments for Arch Linux images, you should either:

• Remove this setting entirely (use the default limit), or
• Disable major updates via matchUpdateTypes rule with enabled: false

If unlimited major upgrades is the intended behavior, then the configuration is correct but the PR title is misleading.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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 and usage tips.}