-
Notifications
You must be signed in to change notification settings - Fork 49
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: revert 3057 #3063
fix: revert 3057 #3063
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as described so I'm approving, but should this be cherry-picked and turned into a hotfix PR instead?
Shoot, yes, forgot to do it to the right branch. 1 sec |
Ok it's to release now |
Beauty! 🙌 |
## [3.6.9](v3.6.8...v3.6.9) (2024-04-12) ### Bug Fixes * revert 3057 ([#3063](#3063)) ([25eea61](25eea61))
🎉 This PR is included in version 3.6.9 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
# [3.7.0-alpha.3](v3.7.0-alpha.2...v3.7.0-alpha.3) (2024-04-12) ### Bug Fixes * revert 3057 ([#3063](#3063)) ([25eea61](25eea61))
🎉 This PR is included in version 3.7.0-alpha.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
All Submissions:
Changes proposed in this Pull Request:
#3057 in conjunction with some cron job seems to cause some sort of issue that fills up the logs with millions of notices a minute. This PR rolls that change back so we can re-approach the problem in some other way that should have less side-effects.
How to test the changes in this Pull Request:
Other information: