Skip to content

chore(renovate): require approval for next branch #35831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2025
Merged

Conversation

viceice
Copy link
Member

@viceice viceice commented May 9, 2025

Changes

makes no sense to autmatically update them. we should do manually approve updates and merge main from time to time as needed.

Context

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@viceice viceice requested a review from rarkins May 9, 2025 08:06
@viceice viceice enabled auto-merge May 9, 2025 08:07
@viceice viceice added this pull request to the merge queue May 9, 2025
Merged via the queue into main with commit 30ef4cb May 9, 2025
40 checks passed
@viceice viceice deleted the viceice-patch-1 branch May 9, 2025 08:24
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 40.11.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

RGunning pushed a commit to RGunning/renovate that referenced this pull request May 25, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants