-
Notifications
You must be signed in to change notification settings - Fork 14
New release to allow google-cloud-logging 3.0? #227
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
Comments
Hi everyone, thanks a lot for your effort in supporting issues related to error_reporting.
|
Thanks for reporting this, I started the process to release v1.5.0, which should fix this issue |
Thank you @daniel-sanche! Any thoughts on this part though?
The same problem happened a while ago in #92, and it will happen again as soon as google-cloud-logging cuts their next release, as described above. Any chance you could configure your renovate bot to relax the upper bound to at least the next major version (assuming semver), eg |
Thank you all! |
Hi all! First off, thank you for maintaining this library. We all appreciate it!
google-cloud-logging 3.0 is out, but google-cloud-error-reporting restricts its dependencies pretty narrowly, so 1.4.1 doesn't support 3.0. Looks like that constraint is already updated in #224 though, any chance you could cut a release with it?
More broadly, #224 still restricts to
google-cloud-logging>=1.14.0, <3.0.1
, so we'll have this exact same problem with the next google-cloud-logging release. Ideally libraries should be more permissive in their dependency constraints to avoid this problem. Consider relaxing it to<4.0
, or something similar?The text was updated successfully, but these errors were encountered: