chore: graduate workspace to 1.0.0 for first stable release #418

Merged
jwilger merged 1 commit from chore/release-1.0.0 into main 2026-06-13 15:50:06 -07:00
Owner

Summary

Graduates the EventCore workspace from 0.x to a stable 1.0.0 ahead of the first stable release. All milestone 1.0.0 issues are merged.

Bumps the lockstep [workspace.package].version and every internal path-dependency version pin from 0.9.0 to 1.0.0 (the path pins must move in lockstep or cargo rejects a 1.0.0 path crate against a ^0.9.0 requirement).

Why a manual bump

release-plz computes the next version from conventional commits relative to the last release (0.9.0); in 0.x the breaking read-stream change (#364) yields 0.10.0, not a major 1.0.0 — hence the open v0.10.0 release PR (#417). release-plz honors a manually-set-higher manifest version, so setting the workspace to 1.0.0 here makes the next automated release PR target v1.0.0 and supersede #417.

Scope

Version-only change. It publishes nothing — publication happens when the resulting chore(release): v1.0.0 PR is merged. cargo check --workspace passes with all crates at 1.0.0; full pre-commit suite (fmt/clippy/nextest/doc/check/audit) green.

## Summary Graduates the EventCore workspace from `0.x` to a stable **1.0.0** ahead of the first stable release. All milestone 1.0.0 issues are merged. Bumps the lockstep `[workspace.package].version` and every internal path-dependency version pin from `0.9.0` to `1.0.0` (the path pins must move in lockstep or `cargo` rejects a `1.0.0` path crate against a `^0.9.0` requirement). ## Why a manual bump release-plz computes the next version from conventional commits relative to the last release (`0.9.0`); in `0.x` the breaking read-stream change (#364) yields `0.10.0`, not a major `1.0.0` — hence the open v0.10.0 release PR (#417). release-plz honors a manually-set-higher manifest version, so setting the workspace to `1.0.0` here makes the next automated release PR target **v1.0.0** and supersede #417. ## Scope Version-only change. It **publishes nothing** — publication happens when the resulting `chore(release): v1.0.0` PR is merged. `cargo check --workspace` passes with all crates at 1.0.0; full pre-commit suite (fmt/clippy/nextest/doc/check/audit) green.
chore: graduate workspace to 1.0.0 for first stable release
All checks were successful
CI / Detect Changes (pull_request) Successful in 4s
CI / Format (pull_request) Successful in 19s
CI / Request auto_review semantic review (pull_request) Successful in 2s
auto_review auto_review: no findings
CI / Test (pull_request) Successful in 3m21s
CI / Security Audit (pull_request) Successful in 29s
CI / Mutation (pull_request) Has been skipped
CI / Clippy (pull_request) Successful in 1m26s
CI / CI Gate (pull_request) Successful in 2s
df23bc7d15
Bumps the lockstep `[workspace.package].version` and every internal
path-dependency version pin from 0.9.0 to 1.0.0 ahead of the first
stable release. All milestone 1.0.0 issues are merged, so the workspace
is graduating from 0.x to a stable 1.0.0 API.

release-plz computes a next version from conventional commits relative
to the last release (0.9.0), which in 0.x yields 0.10.0 for the breaking
read-stream change rather than a major 1.0.0. Per the release-plz
behavior of honoring a manually-set-higher manifest version, setting the
workspace to 1.0.0 here makes the next automated release PR target
v1.0.0 (superseding the open v0.10.0 release PR).

This is a version-only change; it publishes nothing. Publication happens
when the resulting `chore(release): v1.0.0` PR is merged.
auto-review left a comment

The pull request updates the version of the EventCore workspace and its internal dependencies from 0.9.0 to 1.0.0, preparing for the first stable release. This is a version-only change with no functional modifications, and all checks pass, making it safe to merge.

LLM usage and cost

The pull request updates the version of the EventCore workspace and its internal dependencies from 0.9.0 to 1.0.0, preparing for the first stable release. This is a version-only change with no functional modifications, and all checks pass, making it safe to merge. ## LLM usage and cost - Reasoning (gpt-4o) in=3272 out=74 cost=$0.017470 - Cheap (gpt-4o-mini) in=583 out=52 cost=$0.000119 Estimated total USD: $0.017589 via https://api.openai.com and https://api.openai.com
jwilger deleted branch chore/release-1.0.0 2026-06-13 15:50:06 -07:00
Sign in to join this conversation.
No description provided.