Skip to content

chore: bump go-sdk-common to v4 for EasyJSON removal (v4 cascade)#36

Closed
aaron-zeisler wants to merge 1 commit into
mainfrom
aaronz/SDK-2119/v4-cascade
Closed

chore: bump go-sdk-common to v4 for EasyJSON removal (v4 cascade)#36
aaron-zeisler wants to merge 1 commit into
mainfrom
aaronz/SDK-2119/v4-cascade

Conversation

@aaron-zeisler
Copy link
Copy Markdown

Summary

Updates the go-server-sdk-redis-go-redis integration to use go-sdk-common/v4, part of the EasyJSON removal cascade (SDK-2113).

  • go-sdk-common /v3/v4 (v4.0.0)
  • go-server-sdk/v7 bumped to cascade pseudo (uses v4 deps internally)
  • go directive bumped from 1.19 → 1.24
  • Removes transitive easyjson and josharian/intern dependencies

Dependency Chain (v4 cascade)

go-jsonstream/v4 (#39)        <- feat!: (merged)
└─ go-sdk-common/v4 (#50)     <- feat!: (merged)
   ├─ go-server-sdk-evaluation/v4 (#51) <- feat!: (merged)
   ├─ go-sdk-events/v3 (#43)  <- chore: (merged)
   └─ go-server-sdk/v7 (#380) <- chore:
      └─ go-server-sdk-redis-go-redis (this PR)

Test plan

  • go build ./... clean
  • go vet ./... clean
  • go mod tidy produces no diff
  • Tests compile (go test -count=0 ./...)

Stage 5 cleanup

Once go-server-sdk/v7 has a real tagged release with the v4 deps, this PR's pseudo-version should be flipped to that real version before merge — or merge as-is and follow up.

via LD Research 🤖

…ascade)

Rewrite go-sdk-common imports from /v3 to /v4 and bump
go-server-sdk/v7 to the cascade pseudo-version that uses v4 deps.

Part of SDK-2113 (EasyJSON removal epic).
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