Skip to content

chore(v4): release 4.0.0#53

Merged
aaron-zeisler merged 1 commit into
v4from
release-please--branches--v4
May 28, 2026
Merged

chore(v4): release 4.0.0#53
aaron-zeisler merged 1 commit into
v4from
release-please--branches--v4

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 28, 2026

🤖 I have created a release beep boop

4.0.0 (2026-05-28)

⚠ BREAKING CHANGES

  • remove easyjson from go-sdk-common (#50)

Features

  • remove easyjson from go-sdk-common (#50) (e7dec07)

This PR was generated with Release Please. See documentation.


Note

Low Risk
Diff only updates version manifest and changelog; consumer risk from easyjson removal is documented for the release, not introduced in this PR’s files.

Overview
This PR is a Release Please cut that publishes v4.0.0 by updating .release-please-manifest.json from 3.5.0 to 4.0.0 and adding the matching CHANGELOG section for the v3.5.0...v4.0.0 release.

The new changelog entry records the breaking change for this major: easyjson is removed from go-sdk-common (#50). Downstream apps that depended on the launchdarkly_easyjson build tag or generated easyjson codecs need to move to v4 and standard JSON paths (e.g. encoding/json / go-jsonstream) instead.

No library source changes appear in this diff—only release metadata and documentation of what shipped in 4.0.0.

Reviewed by Cursor Bugbot for commit fa6628e. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions github-actions Bot requested a review from a team as a code owner May 28, 2026 17:05
@aaron-zeisler aaron-zeisler merged commit 37ef4f9 into v4 May 28, 2026
4 checks passed
@aaron-zeisler aaron-zeisler deleted the release-please--branches--v4 branch May 28, 2026 17:11
@github-actions
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant