Repository navigation
chore(release): 0.3.0 - #131
Merged
Merged
Conversation
Workspace-wide minor bump for the downstream-integration release that anvil consumes from crates.io. - Breaking: kindling-client SpoolConfig is now #[non_exhaustive] (+ max_bytes / max_age_ms), and kindling-runtime's public config/error/strategy types are #[non_exhaustive]. Pre-1.0, a breaking change bumps the minor -> 0.3.0. - Ships KINTEG-003 (observation list/enumerate read API), KINTEG-009 (spool retention cap), and KINTEG-008 (kindling-runtime facade, first publish). - Bumps workspace.package version + all intra-workspace dep pins to 0.3.0, npm package versions to 0.3.0, the publish_readiness lockstep constant, and adds a CHANGELOG [0.3.0] section. No schema change (stays v5). The crates.io publish (cargo login + scripts/publish.sh) and the v0.3.0 tag / GitHub Release stay user-gated.
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
1 participant
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.
Release prep for 0.3.0
Workspace-wide minor bump so the downstream-integration work anvil consumes is publishable to crates.io. Does not publish anything — the
cargo login+scripts/publish.shstep and thev0.3.0tag / GitHub Release stay user-gated.Why 0.3.0 (minor, not patch)
kindling-clientshippedSpoolConfigat 0.2.0 without#[non_exhaustive]; KINTEG-009 adds that attribute plus new fields — a breaking change. Pre-1.0 semver bumps the minor.kindling-runtimealso marks its public config/error/strategy#[non_exhaustive]. The workspace version is shared, so all crates move to 0.3.0 together.What ships in 0.3.0
POST /v1/observations/list+Client::list_observations: exhaustive, deterministically-paginated read API (unblocks anvil KDS-004).kindling-runtimefacade crate (first crates.io publish).No schema change (stays v5).
Changes in this PR
workspace.package.version0.2.0 → 0.3.0 and all intra-workspace dependency pins.package.jsonversions (root + 4 packages) → 0.3.0 (interdeps areworkspace:*).publish_readinesslockstep constant + test name → 0.3.0.CHANGELOG.md[0.3.0]section (Breaking + Added).Verification
cargo build --workspace,cargo clippy --all-targets --all-features -D warnings,cargo fmt --all --check,cargo test -p eddacraft-kindling --test publish_readiness(version lockstep + pins at 0.3.0), andpnpm -r run type-checkall green.Release steps after merge (user-gated)
cargo login→scripts/publish.sh(publishes crates in dependency order: types → store → provider → service → server → client → runtime → kindling).v0.3.0onmain+ GitHub Release → triggerspublish.yml(npm) andrelease.yml(prebuilt binaries).