-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update newrelic to the latest version 🚀 #204
Conversation
Version 2.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Version 2.0.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 2.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Version 2.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 46 commits.
There are 46 commits in total. See the full diff |
Version 2.2.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Version 2.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 2.3.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 2.3.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 2.0.0 of newrelic just got published.
The version 2.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of newrelic.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 279 commits.
1795642
Merge pull request #1200 from NodeJS-agent/nwolfe/v2.0.0
cf06882
Merge pull request #1199 from NodeJS-agent/nwolfe/log-update
c783805
Merge pull request #1201 from NodeJS-agent/nwolfe/pg-native
0ce467d
docs: updated changelog for v2.0.0
21fc8fb
Improved logging around setting transaction name.
ffff3f4
tests: pg-native requires Node 4+
f7bba4c
Merge pull request #1198 from NodeJS-agent/mkuba/docs-minor-updates
b73a498
added instrumentMessages to intro tutorial, updated OperationSpec and QuerySpec documentation
328d4db
Merge pull request #1197 from NodeJS-agent/mkuba/client-cross-process-id
3d4e7ec
cat: fixed client_cross_process_id attribute to always refer to the first originating transaction
b2840ab
Merge pull request #1188 from NodeJS-agent/mkuba/message-tutorial-updates
5cc2476
docs: update of message shim tutorial
7a3dc07
Merge branch 'nwolfe/messaging-update' into v2.x
fb849ff
Merge pull request #1194 from NodeJS-agent/bclement/channel-get-test
d3f35b9
Merge pull request #1187 from NodeJS-agent/nwolfe/messaging-update
There are 250 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴