Skip to content

chore: release v0.16.0#211

Merged
mostafa merged 1 commit into
mainfrom
release/v0.16.0
Jun 15, 2026
Merged

chore: release v0.16.0#211
mostafa merged 1 commit into
mainfrom
release/v0.16.0

Conversation

@mostafa

@mostafa mostafa commented Jun 14, 2026

Copy link
Copy Markdown
Member

Summary

Release v0.16.0. Bumps the workspace from 0.15.0 to 0.16.0 (workspace package version plus all 17 inter-crate path pins across the six dependent crates), syncs both Cargo.lock and fuzz/Cargo.lock, and finalizes CHANGELOG.md by promoting the [Unreleased] block to [0.16.0] - 2026-06-15 with a TL;DR, a v0.15.0...v0.16.0 compare link, and the release reference link.

Headline framing: the "MCP server" release.

Full release notes: see the new [0.16.0] section in CHANGELOG.md.

Test plan

  • cargo fmt --all -- --check
  • cargo metadata --locked for the workspace and fuzz/ (lockfile/manifest consistency)
  • cargo clippy --workspace --all-targets --all-features -- -D warnings (CI)
  • cargo test --workspace --all-features (CI)
  • mkdocs build --strict (CI)
  • cargo deny check (CI)

This commit is a version/changelog bump only; no source changed since the last merge to main, so the heavier gates are left to CI.

Post-merge

After merge, tag v0.16.0 on main and create the GitHub Release using the [0.16.0] body verbatim. The publish.yml (now including the new rsigma-mcp crate in the publish order), release-binaries.yml, and docker.yml workflows fire on release: published.

Bump the workspace and all inter-crate version pins from 0.15.0 to
0.16.0, sync the workspace and fuzz lockfiles, and finalize the
CHANGELOG by promoting the [Unreleased] section to [0.16.0] with a
TL;DR summary and a release reference link.
@mostafa mostafa merged commit fa246de into main Jun 15, 2026
16 checks passed
@mostafa mostafa deleted the release/v0.16.0 branch June 15, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant