Repository navigation
chore: use shared renovate-config preset - #511
Merged
Merged
Conversation
✅ Deploy Preview for meme-driven-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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
1 participant
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.
What
Replace the duplicated Renovate config with the shared org preset
local>setchy/renovate-config, and add CI that validates it.Why
Baseline settings (best practices, vulnerability alerts, disabled rate limiting, semantic
chorecommits, separate major releases, Biome version updates,dependencylabel,setchyassignee, pinned ranges) now live in one place and are inherited.What stays local
schedule:weekly. Also inherits:disableRateLimitingand:semanticCommitTypeAll(chore)for consistency.CI
Adds
.github/workflows/renovate.yml, which calls the shared reusable validator insetchy/renovate-configand runsrenovate-config-validator --strictwheneverrenovate.json/renovate.json5changes.Notes
Config validationcheck can only run once the reusable workflow in ci: add reusable Renovate config validator workflow renovate-config#2 is merged tomain.