Release: Prepare v0.2.5

[huronat]

What this does

• bumps the Rust package and lockfile to 0.2.5
• advances the Helm appVersion to the same version
• updates the design status and release documentation
• keeps the chart package version unchanged because this workflow publishes the application image, not a packaged chart

After merge, pushing tag v0.2.5 will run the existing release workflow. It publishes GitHub binaries/checksums and the private ECR tags 0.2.5-amd64, 0.2.5-arm64, and multi-architecture 0.2.5.

Verification

• release version-consistency gate reproduced locally
• cargo test --locked: 285 passed
• cargo test --locked --features s3,gcs,mcp-http,athena: 298 passed
• helm lint deploy/helm/synty
• git diff --check

Summary by CodeRabbit

• Release
  • Updated the release version to 0.2.5 across the application, deployment chart, and system design documentation.
  • Expanded release build coverage for macOS and Ubuntu, including bounded remote trace queries.
  • Clarified release tagging and upgrade behavior in contributor documentation.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release is updated from 0.2.4 to 0.2.5 across package metadata, Helm chart metadata, design documentation, and workflow guidance. Release instructions now include the athena feature in macOS and Ubuntu build matrices.

Changes

Release 0.2.5

Layer / File(s)	Summary
Version metadata alignment Cargo.toml, deploy/helm/synty/Chart.yaml, docs/design.md, .github/workflows/release.yml	Package and chart versions, design status, and release tag guidance are aligned with version 0.2.5.
Release build matrix guidance CONTRIBUTING.md	macOS and Ubuntu release builds include athena, which enables bounded remote trace queries; the instructions also clarify release consumption during upgrades.

Possibly related PRs

• superlinked/synty#12: Updates the same release-version metadata and workflow guidance.
• superlinked/synty#14: Implements a similar release-version bump across shared files.
• superlinked/synty#10: Updates release/versioning metadata in overlapping files.

Suggested reviewers: svonava

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the release prep for v0.2.5, matching the main change set.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/release-v0.2.5

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 53-57: Update the release instructions in the CONTRIBUTING release
section to remove the stale `git tag v0.2.0` example. Replace it with a
version-neutral tagging command or the current 0.2.5 release tag, keeping the
surrounding workflow consistent with the documented release process.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d6375c5-1da6-4039-ba6f-693eda664d57

📥 Commits

Reviewing files that changed from the base of the PR and between 2cc9eea and 37363c7.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• .github/workflows/release.yml
• CONTRIBUTING.md
• Cargo.toml
• deploy/helm/synty/Chart.yaml
• docs/design.md

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Remove the stale hard-coded release tag example.

This release section still instructs contributors to run git tag v0.2.0; following it for this release would publish the wrong tag. Replace it with a version-neutral command or the current release tag, and keep the release guidance synchronized with the 0.2.5 workflow.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 53 - 57, Update the release instructions in the
CONTRIBUTING release section to remove the stale `git tag v0.2.0` example.
Replace it with a version-neutral tagging command or the current 0.2.5 release
tag, keeping the surrounding workflow consistent with the documented release
process.

Source: Coding guidelines