This repository has been archived by the owner on Oct 30, 2020. It is now read-only.
Update newrelic to version 1.28.3 🚀 #131
Closed
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
bergie
force-pushed
the
greenkeeper-newrelic-1.28.3
branch
from
af43104
to
d8c3038
Compare
bergie
force-pushed
the
greenkeeper-newrelic-1.28.3
branch
from
d8c3038
to
6876340
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hello lovely humans,
newrelic just published its new version 1.28.3.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 96 commits .
b030774release: published 1.28.3782535bdocs: updated news with PG fix3d1b6dclint: fixed comment wrapping21959a7tests: updated pg tests to find named segment1d2cf20instrumentation: in pg do not create segments for row listenersc8f7278docs: added example of using createBackgroundTransaction()fdd909adocs: added more details for createBackgroundTransactionc0901e6collector: Send a unique identifier on connect6724b8dlogging: More logging around segment creation28e8c2aoptimization: Improved environment reading at startupb6aa053Add comment explaining what _fatalException is forb646e79docs: Updated changelog for v1.28.32e0a2farelease: published 1.28.2e1ccb77docs: Updated changelog for v1.28.22495053instrumentation: added instrumentation for directorThere are 96 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade