fix: Trigger release / Code comments change#363
Merged
abelonogov-ld merged 1 commit intomainfrom Feb 11, 2026
Merged
Conversation
Vadman97
approved these changes
Feb 11, 2026
Merged
Vadman97
pushed a commit
that referenced
this pull request
Feb 12, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>launchdarkly-observability-python: 1.1.0</summary> ## [1.1.0](launchdarkly-observability-python-1.0.0...launchdarkly-observability-python-1.1.0) (2026-02-12) ### Features * address dependabot issues ([#359](#359)) ([ca1130c](ca1130c)) </details> <details><summary>launchdarkly-observability-android: 0.25.1</summary> ## [0.25.1](launchdarkly-observability-android-0.25.0...launchdarkly-observability-android-0.25.1) (2026-02-12) ### Bug Fixes * release package by trigger new build ([#364](#364)) ([7eaf5cd](7eaf5cd)) * Trigger release / Code comments change ([#363](#363)) ([06b34da](06b34da)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Release/version and documentation-only changes; no functional code changes are included in this diff. > > **Overview** > Updates release metadata to publish new versions of the Android and Python observability SDKs. > > Bumps `sdk/@launchdarkly/observability-android` to `0.25.1` (manifest + `gradle.properties`) and records two release-trigger bugfix entries in `CHANGELOG.md`. Bumps `sdk/@launchdarkly/observability-python` to `1.1.0` (manifest + `pyproject.toml`), updates `PROVENANCE.md`’s verification example version, and adds a changelog entry noting dependency-related updates. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 4cece0b. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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.
Summary
The goal to bump version to trigger release
Note
Low Risk
Comment-only changes that clarify Session Replay behavior; no functional or API behavior changes.
Overview
Updates KDoc wording to clarify Session Replay semantics:
ReplayOptions.enablednow explicitly states capture begins immediately on initialization, andLDReplay.start()/stop()docs are simplified to “starts/stops capture” (removing mention of event buffering).Written by Cursor Bugbot for commit b0d1899. This will update automatically on new commits. Configure here.