-
Notifications
You must be signed in to change notification settings - Fork 175
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
New release #330
Comments
As said in #326 (comment), I would like to add #322 to the next (3.5) release too, so that's the blocker. |
@Jean85 It has been over a month since #326 was merged. Can you please consider to tag the new version as soon as possible? We are introducing Messenger in our app and we'll have to basically copy the entire #326 code in our app if this doesn't get tagged soon. I don't see anything that would stop you from tagging 3.5.1 or 3.6 immediately after #322 gets merged so IMO it doesn't make sense to delay tagging 3.5.0 any longer. |
You can fork the repo and merge it on your side if you want to have both PRs active. I've refrained to go forward because a Symfony maintainer pointed to me the fact that I should change the approach on how this bundle works, so I'm trying to understand how to proceed. |
Ok, thanks for the info and the fast response. |
Hey,
Could you push a new release so we can start using Sentry with messenger?
Thank you!
The text was updated successfully, but these errors were encountered: