Repository navigation
chore: re-enable renovate - #405
Merged
Merged
Conversation
Reverts #404. The monorepo migration is still under evaluation, so the repository keeps receiving dependency updates until that decision is made. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
Reverts #404 by removing
"enabled": falsefromrenovate.json, restoring the file to its previous contents.Why
Disabling renovate assumed the migration into tuist/tuist was going ahead. That decision is still open, so the repository should keep receiving dependency updates in the meantime.
If the migration does go ahead later, disabling renovate is a one-line change to make again at that point.
馃 Generated with Claude Code