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

Require the bugsnag top level lib when notifying of a deploy #275

Merged
merged 1 commit into from
Feb 1, 2016

Conversation

snmaynard
Copy link
Contributor

This fixes #274 and #272.

kattrali added a commit that referenced this pull request Feb 1, 2016
Require the bugsnag top level lib when notifying of a deploy
@kattrali kattrali merged commit 958e6a0 into master Feb 1, 2016
@kattrali
Copy link
Contributor

kattrali commented Feb 1, 2016

🌟

@flynfish
Copy link

flynfish commented Mar 9, 2016

Is this going to be released in a gem update soon?

@kattrali
Copy link
Contributor

kattrali commented Mar 9, 2016

@flynfish Yep! Released in 4.0.0, (its a major release since support for ruby 1.8 was dropped).

@flynfish
Copy link

flynfish commented Mar 9, 2016

👍 thanks!

olivierlacan added a commit to codeschool/orientation that referenced this pull request Feb 24, 2017
To avoid Bugsnag.configure bug.

See: bugsnag/bugsnag-ruby#275
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.

Bugnsag deploy notification failed, #<NoMethodError: undefined method `configuration' for Bugsnag:Module>
3 participants