Update opbeat to version 4.13.2 🚀 #156
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
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.
Hello lovely humans,
opbeat just published its new version 4.13.2.
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 opbeat.
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 418 commits .
e67d53e4.13.22144212hapi: do not overwrite tags of eventsbbd743e4.13.1e6b092fcore: update inlined code from async-listener to match v0.6.5720bcc7test: bump knex dev-dependency to ^0.13.052e2745chore: bump debug dependency to ^2.6.688149a9test: stop using deprecated fs.exists()c81908etest: ignore specific linting errorsd783a55core: stop using deprecated util.is*e51d085test: bump standard linter to ^10.0.21b5ea33http/https: end trace before response end event callback is calledcfa8e47test: make sure we don't loose context in express-graphqlbb25113test: make tests fail less06877d74.13.0fe4e90cchore: bump stackman dependencyThere are 250 commits in total. See the full diff.