Repository navigation
Release 0.3.0 - #152
Merged
Merged
Release 0.3.0#152
Conversation
A minor release: the compatibility promise, the start-up refusal of clustered modes nobody acknowledged, and the dependency security fixes that cleared the Rust and npm audits since 0.2.1. No on-disk format or schema change, so 0.2.x moves to 0.3.0 and back by swapping the binary. The workspace, the console, both lockfiles, the chart and every current-version example move to 0.3.0. Kept as they were: the container-images page's example of a fix superseding a published tag, and attestation starting at 0.2.0. SECURITY.md still named 0.1.3 as the supported release, and the changelog's compare links stopped at 0.1.3; both now reach 0.3.0.
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
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.
Prepares Record Store 0.3.0. Once this is merged, tag the merge commit
v0.3.0(signed) and push the tag;release.ymldoes the rest.Why a minor release
server.modeofclusterorcontrolnow fails thedeployment_modestart-up check unlessserver.unsupported_cluster_modeacknowledges it (3267003). Standalone deployments are unaffected. Before 1.0 that needs at least a minor bump.No on-disk format or schema change: 0.2.x ↔ 0.3.0 is a binary swap.
What changed here
Cargo.tomlandconsole/package.json→ 0.3.0, with both lockfiles refreshed.release-version.sh v0.3.0passes.CHANGELOG.md: the Unreleased entries become[0.3.0]. Added an intro, an Upgrading section (including the rollback caveat that 0.2.1 refuses a config file containingunsupported_cluster_mode) and a Security section. The compare links now include 0.2.0, 0.2.1 and 0.3.0.docs/,deploy/(Compose defaults, Helm chartversion/appVersion, nfpm, package script) and the issue templates → 0.3.0.SECURITY.mdsupported-versions table → 0.3.0. It still named 0.1.3.Deliberately left:
container-images.md's "once 0.2.0 exists… a fix ships as 0.2.1" example, andverifying-releases.md's "from 0.2.0 onwards" (attestation start).Checked locally
.github/scripts/release-version.sh v0.3.0→version=0.3.0release-notes.shrenders the 0.3.0 sectionnpm audit --omit=dev --audit-level=high(SEC-AUDIT-NPM) → 0 vulnerabilitiestests/rust-audit.sh(SEC-AUDIT-RUST) → cleanBefore tagging
READY## [0.3.0] - 2026-10-29