Skip to content

Conversation

muffinresearch
Copy link
Contributor

Closes #2375

@muffinresearch
Copy link
Contributor Author

See the release details here:

https://github.com/getsentry/raven-node/releases

Note specifically:

  • Node processes with raven will now exit in exactly the same situations as if raven were not present
    • Previously, there were failure scenarios where raven would erroneously cause the process to continue to run when it should have shut down
    • Be aware when upgrading: it is possible that with raven-node 2.0, your node process will shut down from exceptions where it previously did not

@tofumatt
Copy link
Contributor

tofumatt commented Jul 9, 2017

I ran this locally, hit pages that throw, browsed around, ran the tests, and things seemed fine with no premature exits from exceptions. I'm gonna say this is okay.

@tofumatt tofumatt force-pushed the greenkeeper/raven-2.0.2 branch from a3c7d72 to 429dc55 Compare July 9, 2017 00:49
@tofumatt
Copy link
Contributor

tofumatt commented Jul 9, 2017

Looks like #2615 supercedes this though; tested that and it works as well so will merge that.

@greenkeeper greenkeeper bot deleted the greenkeeper/raven-2.0.2 branch July 9, 2017 01:39
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.

2 participants