chore: bump version to 0.3.0 (pre-release)

[Rahul Dass (rahuldass19)]

Pre-release version bump: v0.2.0 → v0.3.0

81 commits, 40 files (+4088/-209 lines) shipped since the last release in January 2026. This PR updates the version string everywhere so the next publish picks up the correct version.

Files changed

File	Change
\pyproject.toml\	\

---

Summary by Gitar

• Dependency management:
  • Added pytest-timeout as a dev dependency in uv.lock.
  • Tightened typing-extensions version marker in uv.lock.

_{This will update automatically on new commits.}

Summary by CodeRabbit

• Documentation

  • Updated documentation to identify v0.3.0 as the current release.
  • Clarified that the typed TrustStatus enum is available from v0.3.0 onward.

• Release Metadata

  • Updated package version information to v0.3.0 across the project and Express middleware package.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

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

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 22744954-4498-4a4b-90ac-9d988d1af86f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

The project version was updated to v0.3.0 across Python metadata, runtime exports, and Express middleware. README references now identify v0.3.0 as the current release and document its typed TrustStatus support.

Changes

Release version alignment

Layer / File(s)	Summary
Package version metadata pyproject.toml, middleware/express/package.json, src/qwed_ucp/__init__.py	Package metadata and the runtime __version__ value were updated to 0.3.0.
Release documentation README.md	Trust Status and roadmap references were updated from v0.2.0 to v0.3.0.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 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 main change: a pre-release version bump to 0.3.0.
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 release/v0.3.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gitar-bot]

💡 Quality: Unrelated typing-extensions marker change bundled in version bump

The uv.lock change alters the exceptiongroup dependency marker for typing-extensions from python_full_version < '3.13' to python_full_version < '3.11', which is unrelated to a version bump and shrinks the range of Python versions that pull in typing-extensions. Since uv.lock is machine-generated, a hand-edited or stale marker can diverge from what uv lock would produce and cause resolution surprises on Python 3.11/3.12. Regenerate the lockfile with uv lock and confirm this marker change is intentional rather than an artifact.

_{Was this helpful? React with 👍 / 👎}

[greptile-apps]

Greptile Summary

This PR prepares version 0.3.0 for release. The main changes are:

• Bump Python package metadata and runtime version to 0.3.0.
• Align the Express middleware package version with the release.
• Update release references in the README.
• Refresh development dependency metadata in the lockfile.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
README.md	Updates current-release and TrustStatus references to version 0.3.0.
middleware/express/package.json	Updates the Express middleware package version to 0.3.0.
pyproject.toml	Updates the Python project version to 0.3.0.
src/qwed_ucp/init.py	Aligns the runtime package version with the release metadata.
uv.lock	Updates locked project and development dependency metadata.

_{Reviews (2): Last reviewed commit: "fix: restore uv.lock marker, only change..." | Re-trigger Greptile}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitar-bot]

Code Review 👍 Approved with suggestions 1 resolved / 2 findings

Updates project version to 0.3.0 and includes the necessary pytest-timeout dependency, addressing the jump in express middleware versions. Note that the unrelated typing-extensions marker change in uv.lock should be isolated from version bumps.

💡 Quality: Unrelated typing-extensions marker change bundled in version bump

📄 uv.lock:157-158

The uv.lock change alters the exceptiongroup dependency marker for typing-extensions from python_full_version < '3.13' to python_full_version < '3.11', which is unrelated to a version bump and shrinks the range of Python versions that pull in typing-extensions. Since uv.lock is machine-generated, a hand-edited or stale marker can diverge from what uv lock would produce and cause resolution surprises on Python 3.11/3.12. Regenerate the lockfile with uv lock and confirm this marker change is intentional rather than an artifact.

✅ 1 resolved

✅ Quality: express middleware version jumps 0.1.0 to 0.3.0, skipping 0.2.0

📄 middleware/express/package.json:3
middleware/express/package.json goes from 0.1.0 straight to 0.3.0 while the rest of the project moved 0.2.0 -> 0.3.0, meaning the npm package never had a published 0.2.0. If this is intentional alignment with the Python package that's fine, but confirm no consumers expect a 0.2.0 npm release; otherwise the version skip is harmless.

🤖 Prompt for agents

Code Review: Updates project version to 0.3.0 and includes the necessary pytest-timeout dependency, addressing the jump in express middleware versions. Note that the unrelated typing-extensions marker change in uv.lock should be isolated from version bumps.

1. 💡 Quality: Unrelated typing-extensions marker change bundled in version bump
   Files: uv.lock:157-158

   The uv.lock change alters the exceptiongroup dependency marker for typing-extensions from `python_full_version < '3.13'` to `python_full_version < '3.11'`, which is unrelated to a version bump and shrinks the range of Python versions that pull in typing-extensions. Since uv.lock is machine-generated, a hand-edited or stale marker can diverge from what `uv lock` would produce and cause resolution surprises on Python 3.11/3.12. Regenerate the lockfile with `uv lock` and confirm this marker change is intentional rather than an artifact.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

---

Important

Your trial ends in 5 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

_{Was this helpful? React with 👍 / 👎 | Gitar}

[mintlify]

Docs PR opened: QWED-AI/docs#241

Documented the qwed-ucp v0.3.0 release with a changelog entry, updated GitHub Action pin, and TrustStatus availability note.