release: 1.0.0#63
Conversation
First stable release. Bump version to 1.0.0, flip the classifier to Development Status :: 5 - Production/Stable, and reword the README Stability & versioning section from Beta to stable (the public contract is now frozen under SemVer, breaking only on a major bump with one minor of deprecation notice). No code behavior changed since 0.4.0 — this release ships the guarantees, format versioning, and docs that make the contract dependable. Move the [Unreleased] notes into [1.0.0] in the changelog.
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
First stable release 🎉
Turns becwright from a well-tested
0.xinto a stable1.0with a committed public contract. This is the release act at the end of the path-to-1.0.0 work (PRs #59, #60, #61, #62): the groundwork is already merged; this PR flips the switches.Changes
pyproject.toml:version = "1.0.0", classifier →Development Status :: 5 - Production/Stable.src/becwright/__init__.py:__version__ = "1.0.0".README.md/README.es.md: Stability & versioning section reworded from Beta → stable; the path-to-1.0 checklist replaced with a one-line summary of the groundwork; pin examples updated to1.0.0.CHANGELOG.md:[Unreleased]notes moved into[1.0.0]— 2026-07-02 with a release summary and compare links.No behavior change since 0.4.0
Intentionally. Everything that makes the contract dependable (format versioning, frozen field set, documented + test-locked exit codes and
check --json, deprecation policy, real-repo validation) already landed in #59–#62. This release only adds the guarantee, so a user on 0.4.0 upgrading to 1.0.0 sees the same tool with a stable promise.After merge — publish
Per
documentation/releasing.md: create a GitHub release taggedv1.0.0(matchespyproject.toml). That triggersrelease.yml, which builds the binaries, sets the npm package versions from the tag, and publishes to npm + PyPI. (npmpackage.jsonfiles are set from the tag at publish time, so they aren't edited here.)Test plan
pytest— 253 passing.pyproject.tomland__version__(both1.0.0).Development Status :: 5 - Production/Stable).0.4.0references left in README.