Update newrelic to the latest version 馃殌 #100
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
1795642Merge pull request #1200 from NodeJS-agent/nwolfe/v2.0.0cf06882Merge pull request #1199 from NodeJS-agent/nwolfe/log-updatec783805Merge pull request #1201 from NodeJS-agent/nwolfe/pg-native0ce467ddocs: updated changelog for v2.0.021fc8fbImproved logging around setting transaction name.ffff3f4tests: pg-native requires Node 4+f7bba4cMerge pull request #1198 from NodeJS-agent/mkuba/docs-minor-updatesb73a498added instrumentMessages to intro tutorial, updated OperationSpec and QuerySpec documentation328d4dbMerge pull request #1197 from NodeJS-agent/mkuba/client-cross-process-id3d4e7eccat: fixed client_cross_process_id attribute to always refer to the first originating transactionb2840abMerge pull request #1188 from NodeJS-agent/mkuba/message-tutorial-updates5cc2476docs: update of message shim tutorial7a3dc07Merge branch 'nwolfe/messaging-update' into v2.xfb849ffMerge pull request #1194 from NodeJS-agent/bclement/channel-get-testd3f35b9Merge pull request #1187 from NodeJS-agent/nwolfe/messaging-updateThere 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 馃尨