v0.19.0 - #200
Conversation
* feat: added file capability * fix: JS tomfoolery * chore: change input to main now that libdatadog's side was merged * fix: post bump fixes * fix: review * fix: address comments * fix: detached buffer thing * fix: transport for files renamed, uniform lazy loading
* feat: added env capability * feat: respect envcapabilities method unsafedness * feat: validate before saying it's ok * revert: remove set/unset since they would be dangerous APIs in libdatadog (and are most likely not useful in the near/middel future in dd-trace-js) * chore: change input to main's commit that has the change * docs: update doc to remove specific references to the capabilities * fix: remove extra checks * fix: cache env beforehand
* feat: add DDSketch WASM bindings
* feat: added env capability * feat: respect envcapabilities method unsafedness * feat: validate before saying it's ok * revert: remove set/unset since they would be dangerous APIs in libdatadog (and are most likely not useful in the near/middel future in dd-trace-js) * chore: change input to main's commit that has the change * docs: update doc to remove specific references to the capabilities * fix: remove extra checks * fix: cache env beforehand * feat: Adopt TraceExporter's Telemetry stuff * docs: fix libdatadog's behavior when 0 is passed * chore: js tomfoolery * fix: comments * fix: use Cells uniformaly * feat: make the losslessness obvious
|
@Aaalibaba42 Could you please take a look to the pipeline error if it's relevant to your changes? |
|
These test assertions aren't on main, they were added directly on the v0.x branch as part of PR #180 (v0.18.0). That PR bumped the pinned libdatadog revision to 6356aee to pick up the fix for |
|
Thanks for the clarifications, Asking Bryan if his PR is ready to merge |
2 participants
Minor release including:
Features
Build