Repository navigation
Release js-core dependency removal patches - #343
Merged
Merged
Conversation
leoromanovsky
marked this pull request as ready for review
July 23, 2026 00:27
leoromanovsky
requested review from
sameerank and
typotter
and removed request for
a team
July 23, 2026 00:27
typotter
approved these changes
Jul 24, 2026
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
|
PR Shepherd is now watching this PR: fixing basic CI failures, rebasing when it falls behind, and re-queueing after transient merge-queue failures. To disable it, add the If you have any questions, reach the team in #ai-devx-flow. |
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
This branch was previously deployed
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
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.
Motivation
@datadog/flagging-core@2.0.1and@datadog/openfeature-node-server@2.0.1install@datadog/js-core@0.0.3fromDataDog/browser-sdksolely for the timestamp primitive. PR #342 moved that primitive into runtime-agnostic core so Node.js consumers no longer pull browser SDK runtime dependencies. These patch releases make that fix available to package consumers.Changes
This release advances
@datadog/flagging-corefrom2.0.1to2.0.2,@datadog/openfeature-browserfrom1.2.4to1.2.5, and@datadog/openfeature-node-serverfrom2.0.1to2.0.2. Browser and Node.js now pin core exactly at2.0.2, the lockfile reflects those coordinated versions, and the changelog records the dependency removal and packed Node.js purity check.Decisions
The three packages move together because browser and Node.js deliberately pin core to an exact version. Browser retains its direct browser SDK dependencies; the purity boundary applies to core and node-server. The signed package tags were created locally but were not pushed. After this PR is merged with a merge commit, publish in dependency order: core, browser, then node-server.
Validation
bash scripts/internal-deps-validate.shbash scripts/versions-validate.shyarn licenses:validateyarn lintyarn format:checkBUILD_MODE=release yarn buildyarn typecheckyarn test(457 tests across 22 suites)yarn test:browser-installyarn test:node-install(7/7 consumer checks)yarn test:node-install:with-of(7/7 consumer checks)yarn lerna run pack --streamValidation ran with Node.js v26.5.0.