[Snyk] Upgrade zipkin from 0.10.1 to 0.22.0 #3
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.
Snyk has created this PR to upgrade zipkin from 0.10.1 to 0.22.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: zipkin
This release includes in #476, a long requested feature (see #201, #135, #124, #175 and #106) but we did not want to release it until we got users involved in the testing of the feature with real use cases. Thanks @ kurtharriger for taking care of the unit testing part and @ mikhailrojo for actually testing the feature in production code.
We also include some fixes:
This version mainly adds support for AWS SQS transport, thanks to @ asanluis (for the code, iterations and spirit) but also drops support to node8 on builds as EOL.
v0.19.2
[#439] Added agent option to http transport - thanks to @ RAWeber
[#449] Fixes the express instrumentation by using right hooks in the response reported by @ jeffthompson1971 in #417 (comment)
This version includes the brand new zipkin-instrumentation-koa package by @ shumsky, some gaps filled in the Typescript interface by @ Igor-lkm (#426 and #428) and a complete refactor of the test suite for instrumentations.
This adds the ability to manually flush spans from the BatchRecorder and fixes a couple bugs, most notably
Error: Must be valid TraceId instance
. Thanks for all the feedback and help making things better!BatchRecorder.flush()
for manual control of span reporting (ex in lambda) #362Error: Must be valid TraceId instance
relating to transpilation #422Span.kind
onServerRecv
and droppedClientAddr
annotations #418v0.18.5
Major improvements in span reporting and debugging support. Notably the issue described in #365 was addressed in #383 with tones of tests in #378, #376, #372, #369, #380 and #385. All these great work is thanks to @ adriancole
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:![](https://camo.githubusercontent.com/df0c6127681fbd937bdf6ce0739543c440831b3917a30428993da5a98d1eb901/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6d4e4451785a44417a597930794e44686c4c5451345a475974595746695a53316b597a63355a6d55315a6d4e6a4d444d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d59304e44466b4d444e6a4c5449304f4755744e44686b5a69316859574a6c4c57526a4e7a6c6d5a54566d59324d774d794a3966513d3d)
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs