fix(renovate): renovate validation#54
Conversation
inffy
requested review from
NiHaiden,
hanthor,
ledif and
renner0e
as code owners
There was a problem hiding this comment.
Pull request overview
This PR fixes Renovate validation by correcting the regex manager template variable name from version to currentValue, which aligns with Renovate's expected named capture group format for version extraction. The PR also includes formatting changes that add extra whitespace after some property colons.
- Changed regex capture group from
(?<version>...)to(?<currentValue>...)to fix Renovate validation - Added extra whitespace after colons on select properties
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "$schema": "https://docs.renovatebot.com/renovate-schema.json", | ||
| "extends": [ | ||
| "extends": [ |
There was a problem hiding this comment.
The whitespace changes (extra spaces after colons) introduce inconsistent formatting in the JSON5 file. Lines 3, 16, and 21 now have two spaces after the colon, while other properties in the file (lines 2, 17, 20) maintain single spaces. This inconsistency reduces code maintainability and doesn't appear to fix any validation issues. Consider either applying consistent spacing throughout the file or reverting these whitespace-only changes.
| "regexManagers": [ | ||
| { | ||
| "fileMatch": ["^Containerfile$"], | ||
| "fileMatch": ["^Containerfile$"], |
There was a problem hiding this comment.
The whitespace changes (extra spaces after colons) introduce inconsistent formatting in the JSON5 file. Lines 3, 16, and 21 now have two spaces after the colon, while other properties in the file (lines 2, 17, 20) maintain single spaces. This inconsistency reduces code maintainability and doesn't appear to fix any validation issues. Consider either applying consistent spacing throughout the file or reverting these whitespace-only changes.
| ], | ||
| "datasourceTemplate": "github-releases", | ||
| "depNameTemplate": "ublue-os/artwork" | ||
| "depNameTemplate": "ublue-os/artwork" |
There was a problem hiding this comment.
The whitespace changes (extra spaces after colons) introduce inconsistent formatting in the JSON5 file. Lines 3, 16, and 21 now have two spaces after the colon, while other properties in the file (lines 2, 17, 20) maintain single spaces. This inconsistency reduces code maintainability and doesn't appear to fix any validation issues. Consider either applying consistent spacing throughout the file or reverting these whitespace-only changes.
No description provided.