Open
Conversation
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
4d2cd0a to
e86865e
Compare
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
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
9.15.1 (2026-03-06)
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Low Risk
Low risk: this PR only updates version numbers and release documentation; no runtime logic changes are included in the diff.
Overview
Release
9.15.1. Updates version references across release metadata (.release-please-manifest.json,pyproject.toml,ldclient/version.py) and refreshesPROVENANCE.mdto use the new version.Adds a
CHANGELOG.mdentry for9.15.1, noting a bug fix to fallback behavior when using custom data system configuration.Written by Cursor Bugbot for commit e86865e. This will update automatically on new commits. Configure here.