Skip to content

chore(main): release 0.9.0 - #72

Merged
tanderson-ld merged 1 commit into
mainfrom
release-please--branches--main
Oct 28, 2026
Merged

tanderson-ld merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.9.0 (2026-10-28)

⚠ BREAKING CHANGES

  • Use None rather than zero for indefinite initialization waiting (#64)

Bug Fixes

  • Use None rather than zero for indefinite initialization waiting (#64) (8bff7b3)

This PR was generated with Release Please. See documentation.


Note

Overview
This Release Please PR cuts 0.9.0 by bumping the version everywhere it is published (pyproject.toml, ld_openfeature/version.py, Sphinx docs/conf.py, and .release-please-manifest.json) and adding the 0.9.0 section to CHANGELOG.md.

The release notes call out a breaking change from #64: LaunchDarklyProvider's start_wait now uses None for indefinite initialization waiting, not 0. Callers who relied on start_wait=0 to block until ready must pass None instead; 0 now means no wait in the constructor (same as documented for LDClient).

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

@tanderson-ld

Copy link
Copy Markdown
Contributor

AI review comment: hold off merging this at 1.0.0 — the version is a release-please config artifact, not an intended GA. This repo's release-please-config.json is missing bump-minor-pre-major (the Ruby provider repo sets it), so the fix!: in #64 escalated the bump to a major. Two corrections are in flight: a Release-As: 0.9.0 commit override has been added to #64's body, and a one-line config PR adding bump-minor-pre-major: true is coming. When that config PR merges, release-please will re-run on the push and retitle this PR to 0.9.0 (same changelog, still flagged breaking).

tanderson-ld added a commit that referenced this pull request Oct 28, 2026
Adds `bump-minor-pre-major: true` to the release-please config, matching
the Ruby provider repo's configuration.

**Why:** release-please's default versioning strategy escalates a
breaking change to a major bump even below 1.0.0. The `fix!:` in #64
therefore retitled the open release PR #72 to **1.0.0** instead of
**0.9.0**. Crossing to 1.0 should be a deliberate GA decision, not a
side effect of a missing config flag.

**Effect:** merging this PR triggers a release-please run, which will
recompute #72 to 0.9.0 (a `Release-As: 0.9.0` override has also been
added to #64's body as a belt-and-suspenders measure — both mechanisms
agree). The changelog is unchanged and the release remains flagged as
breaking.

With this flag, pre-1.0 breaking changes bump the minor (0.x → 0.(x+1))
going forward.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> Adds **`bump-minor-pre-major`: true** to `release-please-config.json`
so release-please treats breaking changes as **minor** bumps while the
package is still below **1.0.0**, instead of jumping to **1.0.0** by
default.
> 
> This aligns versioning with the Ruby provider repo and keeps a
deliberate **1.0.0** GA cut separate from conventional-commit breaking
changes (e.g. retitling an in-flight release PR from **1.0.0** to
**0.9.0** without changing the breaking changelog content).
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
ae994ba. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@github-actions github-actions Bot changed the title chore(main): release 1.0.0 chore(main): release 0.9.0 Oct 28, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from badfd77 to 4ca60d1 Compare October 28, 2026 19:34
@tanderson-ld
tanderson-ld self-requested a review October 28, 2026 19:38
@tanderson-ld
tanderson-ld merged commit ebf6be5 into main Oct 28, 2026
15 checks passed
@tanderson-ld
tanderson-ld deleted the release-please--branches--main branch October 28, 2026 19:41
@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