Skip to content

fix: upgrade go-jsonstream to v3.1.2 and LaunchDarkly deps to current releases - #432

Draft
kinyoklion wants to merge 1 commit into
v7from
rlamb/jsonstream-3.1.2
Draft

fix: upgrade go-jsonstream to v3.1.2 and LaunchDarkly deps to current releases#432
kinyoklion wants to merge 1 commit into
v7from
rlamb/jsonstream-3.1.2

Conversation

@kinyoklion

Copy link
Copy Markdown
Member

Upgrades the four LaunchDarkly dependencies to the releases carrying the go-jsonstream v3.1.2 performance changes (launchdarkly/go-jsonstream#56, #57, #58 — append-based jwriter internals, byte-class-table escape scan, single-pass jreader tokenizer; public API and observable behavior unchanged):

  • go-jsonstream v3.1.1 → v3.1.2
  • go-sdk-common v3.5.0 → v3.5.1
  • go-sdk-events v3.6.2 → v3.6.3
  • go-server-sdk-evaluation v3.0.1 → v3.0.2

For the SDK this lands in data-source payload parsing (ldmodel direct parse -46% on a real 3,228-flag / 3.2 MB payload), flag-state and data-store serialization, and event output encoding (string-array writes -47%).

The diff is the four version bumps only — no go directive change (this module already requires 1.25) and no CI matrix change (floor already 1.24). Validated locally: full unit suite green, repo-pinned golangci-lint clean.

Third tier of the dependency-ordered updates; ld-relay (v8 and v9), streamer, and sdk-test-harness follow once this is tagged.

… releases

go-jsonstream v3.1.2 brings the append-based jwriter internals, the
byte-class-table escape scan, and the single-pass jreader tokenizer
into flag-payload parsing, flag-state serialization, and event output.
go-sdk-common v3.5.1, go-sdk-events v3.6.3, and
go-server-sdk-evaluation v3.0.2 carry the same jsonstream upgrade.
@kinyoklion

Copy link
Copy Markdown
Member Author

In holding for testing — please do not merge yet. This will be marked ready once validation against the updated dependency set is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant