v0.19.0 - #226
Merged
Merged
Conversation
…th 3 updates (#139) Bumps the gh-actions-packages group with 3 updates in the / directory: [actions/checkout](https://github.com/actions/checkout), [actions/setup-node](https://github.com/actions/setup-node) and [DataDog/dd-octo-sts-action](https://github.com/datadog/dd-octo-sts-action). Updates `actions/checkout` from 6.0.2 to 7.0.0 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...9c091bb) Updates `actions/setup-node` from 6.3.0 to 6.4.0 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@53b8394...48b55a0) Updates `DataDog/dd-octo-sts-action` from 1.0.3 to 1.0.4 - [Release notes](https://github.com/datadog/dd-octo-sts-action/releases) - [Commits](DataDog/dd-octo-sts-action@acaa02e...96a2546) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: gh-actions-packages - dependency-name: actions/setup-node dependency-version: 6.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gh-actions-packages - dependency-name: DataDog/dd-octo-sts-action dependency-version: 1.0.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: gh-actions-packages ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [libdd-crashtracker](https://github.com/DataDog/libdatadog) from v35.0.0 to v37.0.0. - [Release notes](https://github.com/DataDog/libdatadog/releases) - [Commits](DataDog/libdatadog@aa78483...86b7f57) --- updated-dependencies: - dependency-name: libdd-crashtracker dependency-version: b2a83ff19a2f4760d180bd9eb9e91f41566ba5b9 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
… 3 updates (#142) Bumps the minor-updates group with 3 updates in the / directory: [eslint](https://github.com/eslint/eslint), [eslint-plugin-import-x](https://github.com/un-ts/eslint-plugin-import-x) and [globals](https://github.com/sindresorhus/globals). Updates `eslint` from 10.0.3 to 10.6.0 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v10.0.3...v10.6.0) Updates `eslint-plugin-import-x` from 4.16.2 to 4.17.1 - [Release notes](https://github.com/un-ts/eslint-plugin-import-x/releases) - [Changelog](https://github.com/un-ts/eslint-plugin-import-x/blob/master/CHANGELOG.md) - [Commits](un-ts/eslint-plugin-import-x@v4.16.2...v4.17.1) Updates `globals` from 17.4.0 to 17.7.0 - [Release notes](https://github.com/sindresorhus/globals/releases) - [Commits](sindresorhus/globals@v17.4.0...v17.7.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.5.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: minor-updates - dependency-name: eslint-plugin-import-x dependency-version: 4.17.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: minor-updates - dependency-name: globals dependency-version: 17.7.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: minor-updates ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…141) Bumps [express](https://github.com/expressjs/express) from 4.22.1 to 5.2.1. - [Release notes](https://github.com/expressjs/express/releases) - [Changelog](https://github.com/expressjs/express/blob/master/History.md) - [Commits](expressjs/express@v4.22.1...v5.2.1) --- updated-dependencies: - dependency-name: express dependency-version: 5.2.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: gh-worker-campaigns-3e9aa4[bot] <244854796+gh-worker-campaigns-3e9aa4[bot]@users.noreply.github.com>
* 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
Co-authored-by: gh-worker-campaigns-3e9aa4[bot] <244854796+gh-worker-campaigns-3e9aa4[bot]@users.noreply.github.com>
* Add remote config wasm layer Also consistently upgrades to v40.0.0 instead of multiple revs being pinned. * Address codex comments * Fix node v18 test * Update to agentless rc * Drop webcrypto polyfill
* feat(libdatadog): add universal core and optional extras packages * refactor: restructure libdatadog packages * test: tighten wasm size budgets * ci(libdatadog): fix cross-platform builds and tests * fix(libdatadog): address package compatibility issues
* feat(libdatadog): add apm data pipeline * test(libdatadog): load pipeline wasm artifact * docs(libdatadog): document cancellable sleep follow-up * test(libdatadog): stabilize timeout retry assertion * fix(libdatadog): expose pipeline API to ESM * refactor(libdatadog): share agentless pipeline adapter * chore(libdatadog): update data pipeline revision * chore(libdatadog): update data pipeline revision * chore(libdatadog): use merged data pipeline revision
* ci(libdatadog): add artifact dependency and size reports * ci(libdatadog): fix wasm report artifact path
* refactor(libdatadog): keep data pipeline on WASM The agentless exporter has no native consumer yet, so its N-API implementation duplicates the WASM exporter and its lifecycle. The default entry point now loads the WASM binding only when it creates an exporter. Refs: #205 * refactor(libdatadog): isolate native backend The native facade exposed the agentless exporter even though every export used WASM, which kept a false backend-parity contract. * fix(libdatadog): defer agentless implementation loading The shared exporter imported the WASM workspace package directly, which root lint cannot resolve. Keeping binding ownership in the WASM facade also defers agentless transport loading until exporter creation.
The package has no native-only consumer, so platform artifacts add build and release work without providing a required capability.
* feat(libdatadog): add dedicated remote config WASM Remote Config pulls in TUF, cryptography, and HTTP dependencies that existing users do not need. Keeping its artifact separate preserves the existing universal WASM load and compile cost. * ci(libdatadog): validate remote config entry point The lint job runs before generated Remote Config modules exist, so fresh checkouts reject both wrapper imports. The request test also verifies that the storage hook wraps the HTTP request. * refactor(libdatadog): simplify remote config packaging Package export maps can target the canonical CommonJS artifacts directly, so forwarding files own no format or compatibility boundary.
v0.x's copy of the wasm request-body test predates the connectionPooling parameter, so replaying it here calls httpRequest with the old nine-argument signature and reads wasm_memory from the wrong slot. Take main's version, which #225 landed with the extra argument. Also take main's Cargo.lock and yarn.lock; replaying the dependency bumps produced only cosmetic dedupe-key differences from the tree those commits were reviewed against.
bengl
force-pushed
the
bengl/v0.19.0-proposal
branch
from
August 31, 2026 17:57
fecc9fb to
20e775a
Compare
Overall package sizeSelf size: 31.66 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
bengl
marked this pull request as ready for review
August 31, 2026 18:01
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or 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
6 participants
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.
What does this PR do?
Releases
0.19.0, bringing every merged-but-unreleasedmainPR ontov0.x.Shape follows the existing
v0.xconvention: one cherry-picked commit per merged PR that isn't in a release yet, oldest first, then release housekeeping and the version bump. The branch is linear offb152efa(v0.18.1) with no merge parent, so rebase-merge works as usual.Cherry-picked (18 commits, oldest first):
8e5588eeae9a3f16a51ad4a617fe588c9311a718a8b1dca31f8107be617af2a1bc95f64f1808e7224cbc1c98707a67eca750cf32b717ec963197ab690b9ef6All 18 applied without conflict.
Plus two commits of release housekeeping:
14c0b30 chore(release): adopt main's http_transport test and lockfiles—v0.x's copy of the wasm request-body test predates theconnectionPoolingparameter, so replaying it here callshttpRequestwith the old nine-argument signature and readswasm_memoryfrom the wrong slot (TypeError: Cannot read properties of undefined (reading 'buffer')). Takes main's version, the one fix(capabilities): copy wasm request bodies before send #225 landed with the extra argument. Also takes main'sCargo.lockandyarn.lock, where replaying the dependency bumps left only cosmetic dedupe-key differences (libdd-common 5.0.0vslibdd-common).20e775a v0.19.0— bumps the root,packages/libdatadog, andpackages/libdatadog/wasmversions plus the@datadog/libdatadog-wasmdependency pin and lockfile.packages/libdatadog/test/package.test.jsasserts all four match, so a root-only bump fails.Deliberately excluded — four
maincommits whose content already shipped onv0.xunder different SHAs:e97ba3e(#159, released as441d070in v0.12.2),0e96992(Bun transport head, released as9dbfe14in v0.15.0),d99947f(#173, released ase2487aain v0.17.0), andae6f3bc(#225, released as5c2e31din v0.18.1).Relationship to
mainThe resulting tree matches
origin/mainexcept fortest/pipeline.js, which keeps 29 lines thatv0.xhas andmaindropped when it rewrote that harness: therefreshes change-buffer views when string interning grows memorytest and adatadog-client-computed-statsheader assertion. Both pass here (52 pass / 0 fail with the pipeline wasm built), so this release ships slightly more coverage thanmainrather than less.Breaking changes for consumers
@datadog/libdatadogchanges API surface entirely. 0.18.1 exported{ find, load, maybeLoad }fromload.js; 0.19.0 exports the WASM API (createAgentlessExporter,backend,zstd_compress,DDSketch). Consumers that usedfind/loadmust move to@datadog/libdatadog-extras, published from the repo root.@datadog/libdatadog-extrasand@datadog/libdatadog-wasm.datadog-js-zstdcrate is gone. Zstd moved intocrates/libdatadog-wasm/src/zstd/, surfaced aszstd_compressfrom@datadog/libdatadog. Anything loadingprebuilds/datadog-js-zstdneeds updating.@datadog/libdatadog-extras.Release mechanics
Merging this pushes
v0.x, which triggers.github/workflows/release.yml: publishes@datadog/libdatadog-wasm@0.19.0,@datadog/libdatadog@0.19.0,@datadog/libdatadog-extras@0.19.0under thelatesttag, then pushes tagv0.19.0.How to test the change?
Run locally in a worktree at this branch:
npx eslint .— cleannpm run build:wasm --prefix packages/libdatadog— buildslibdatadog_wasm+remote_config, no errorsnpm test --prefix packages/libdatadog— 37 pass, 0 failnpm run test:package --prefix packages/libdatadog— 2 pass, 0 failnode scripts/build-wasm.js ./crates/pipeline ./prebuilds/pipelinethennode --test-force-exit test/pipeline.js— 52 pass, 0 failnode --test-force-exit test/http_transport.js— 21 pass, 0 failyarn check:dependencies— no duplicates, tokio limited to the remote config artifactgit diff --stat origin/main HEAD— only thetest/pipeline.jsextras noted aboveNot run locally: the root native suite (
yarn test), which needs a full cargo prebuild; CI covers it viaaction-prebuildify.Follow-up
v0.x's merge base withmainis still6dfdd90(2024-09-03), since this branch takes content by cherry-pick rather than by merge. v0.20.0 will need the same cherry-pick pass.