Skip to content

chore(main): release 9.17.0 - #468

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore(main): release 9.17.0#468
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

9.17.0 (2026-08-14)

Features

  • Add async big segment store manager and async Redis adapter (#462) (aa492d2)
  • Add async event processor (ec7c113)
  • Add async event processor (#472) (ec7c113)
  • Add async FDv1 polling data source and feature requester (#475) (cca37a8)
  • Add async FDv1 streaming and data source status tracking (#464) (4bf7067)
  • Add async FDv2 data sources (#485) (5da1515)
  • Add async hook, plugin, and flag tracker (#463) (686a70a)
  • Add async migration support (#470) (577d51e)
  • Add async persistent feature store foundation and Redis adapter (f9c76ee)
  • Add AsyncConfig for the async SDK client (#471) (0587a78)
  • Add AsyncLDClient with FDv1 data system and public API (#480) (fd041a5)
  • Add environment ID support for hooks. (#484) (49e809f)

Bug Fixes

  • Return empty prerequisites for a flag that fails to evaluate in all_flags_state (#483) (73e9b07)

This PR was generated with Release Please. See documentation.


Note

Overview
This PR bumps the package from 9.16.1 to 9.17.0 across pyproject.toml, ldclient/version.py, .release-please-manifest.json, and the provenance example in PROVENANCE.md.

It adds the 9.17.0 section to CHANGELOG.md, documenting the release (2026-08-14): a large async SDK surface (AsyncLDClient, AsyncConfig, async event processor, FDv1/FDv2 data sources, hooks/plugins, migration, persistent stores and Redis adapters, big segments), plus a fix for empty prerequisites when flag evaluation fails in all_flags_state.

Reviewed by Cursor Bugbot for commit 7b59562. 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 July 27, 2026 15:16
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 5 times, most recently from d1ba299 to de9e6ad Compare August 3, 2026 13:46
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 7 times, most recently from bbc32ab to a62ded8 Compare August 5, 2026 21:11
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 6 times, most recently from f626961 to 76e2ce4 Compare August 13, 2026 21:54
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 76e2ce4 to 7b59562 Compare August 14, 2026 20:18
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.

0 participants