chore: release main#574
Open
LaunchDarklyReleaseBot wants to merge 1 commit into
Open
Conversation
Vadman97
approved these changes
May 29, 2026
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
2 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.
🤖 I have created a release beep boop
launchdarkly-observability-android: 0.49.0
0.49.0 (2026-05-29)
Features
This PR was generated with Release Please. See documentation.
Note
Low Risk
Version and changelog-only changes with no runtime code in this diff; low risk for consumers beyond adopting the published 0.49.0 artifact.
Overview
This PR is a Release Please cut that publishes
@launchdarkly/observability-android0.49.0 with no additional product code in the diff.It bumps the Android package version from 0.48.0 → 0.49.0 in
.release-please-manifest.jsonandgradle.properties, and adds a 0.49.0 changelog entry. That release documents the already-merged feature: Session ReplayframeRateonReplayOptions, aligned with iOS, so capture interval is driven by frames per second (viaCaptureManager.captureDelayMillis).Reviewed by Cursor Bugbot for commit 82ae221. Bugbot is set up for automated code reviews on this repo. Configure here.