Skip to content
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

fix(lookup): better warn logs for unexpected downgrade #29978

Merged
merged 2 commits into from
Jul 2, 2024

Conversation

rarkins
Copy link
Collaborator

@rarkins rarkins commented Jul 2, 2024

Changes

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

@rarkins rarkins enabled auto-merge July 2, 2024 05:41
@rarkins rarkins requested review from zharinov and viceice July 2, 2024 05:41
@rarkins rarkins added this pull request to the merge queue Jul 2, 2024
Merged via the queue into main with commit 622c604 Jul 2, 2024
38 checks passed
@rarkins rarkins deleted the fix/downgrade-warn branch July 2, 2024 06:05
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 37.421.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants