feat: bump version to1.3.0 and update deps; iterate nested

[alain-sv]

No description provided.

[qodo-code-review]

PR Summary by Qodo

Bump to v1.3.0, refresh deps, and fix A2A route test for FastAPI 0.139

✨ Enhancement ⚙️ Configuration changes 🧪 Tests 📝 Documentation 🕐 10-20 Minutes

AI Description

• Bump project version to 1.3.0 and refresh dependency lower bounds.
• Update A2A event-route test to handle FastAPI included-router wrapping.
• Document dependency and test-scope changes in the changelog.

Diagram

graph TD
  A["pyproject.toml"] --> B("Runtime deps") --> C("FastAPI app")
  D["tests/test_a2a.py"] --> C --> E("Route discovery")
  F["src/supervaizer/__version__.py"] --> G("Release v1.3.0")
  H["docs/CHANGELOG.md"] --> G

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Assert via app.router and standard Starlette route containers

• ➕ Avoids relying on a non-standard/less-documented attribute like route.original_router
• ➕ Can be generalized by flattening known containers (e.g., Mount/Router) rather than custom attributes
• ➖ May still require framework-specific handling as FastAPI/Starlette route types evolve
• ➖ Could be more verbose than the current targeted recursion

2. Test against the source router directly (keep a reference)

• ➕ Most stable: avoids introspecting FastAPI's assembled app.routes tree
• ➕ Clearer intent: validates the A2A router contains the expected route
• ➖ Requires exposing/storing the router instance in the server/app fixture or factory
• ➖ Less end-to-end: doesn't prove the route is actually mounted on the app at runtime

Recommendation: Current approach is reasonable for a compatibility fix: it keeps the test end-to-end (verifying the mounted app route) while accommodating FastAPI 0.139 router wrapping. If this breaks again in future FastAPI upgrades, consider switching to flattening known Starlette containers or asserting via a retained reference to the A2A router to reduce reliance on internal attributes.

Files changed (4) +42 / -14

Enhancement (1) +1 / -1

__version__.pyBump package VERSION constant to 1.3.0 +1/-1

Bump package VERSION constant to 1.3.0

• Updates the exported VERSION/__version__ value from 1.2.0 to 1.3.0 to match the release.

src/supervaizer/version.py

Tests (1) +12 / -1

test_a2a.pyTraverse nested/included router wrappers when locating /a2a/events +12/-1

Traverse nested/included router wrappers when locating /a2a/events

• Adds a small recursive route iterator to walk nested routes exposed via included-router wrappers (via original_router.routes). Updates the /a2a/events lookup to use this iterator so the read-scope assertion remains valid under FastAPI >=0.139.0.

tests/test_a2a.py

Documentation (1) +17 / -0

CHANGELOG.mdAdd Unreleased notes and 1.3.0 entry for deps + test fix +17/-0

Add Unreleased notes and 1.3.0 entry for deps + test fix

• Adds an Unreleased 'Changed' section describing updated dependency lower bounds and lock refresh, plus a 'Fixed' entry for the A2A event-scope test adjustment. Introduces the 1.3.0 release header dated 2026-07-02 with a recorded test pass summary.

docs/CHANGELOG.md

Other (1) +12 / -12

pyproject.tomlBump dependency lower bounds and set bumpversion current_version=1.3.0 +12/-12

Bump dependency lower bounds and set bumpversion current_version=1.3.0

• Raises minimum versions for key runtime dependencies (FastAPI, sse-starlette, Typer, Uvicorn) and updates deploy/dev extras (e.g., boto3, google-cloud-run, hatch, pytest, ruff). Updates bumpversion configuration to mark the new 1.3.0 release.

pyproject.toml

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 32 rules

1. Unreleased contains v1.3.0 notes 🐞 Bug ⚙ Maintainability

Description

docs/CHANGELOG.md places the v1.3.0 dependency-bump and test-fix bullets under the "[Unreleased]"
heading even though a dated "[1.3.0]" section is added immediately below. This makes the changelog
ambiguous and can cause the next bumpversion run (which inserts a new version header at
"[Unreleased]") to leave already-released entries in the wrong section.

Code

docs/CHANGELOG.md[R15-30]

+### Changed
+
+- **`pyproject.toml` (since v1.3.0)** — Runtime lower bounds: FastAPI `>=0.139.0`, sse-starlette `>=3.4.5`, Typer `>=0.26.8`, Uvicorn `>=0.49.0`. **`deploy` extra:** boto3 `>=1.43.39`, google-cloud-run `>=0.16.1`, google-cloud-secret-manager `>=2.23.0`. **`dev` extra:** hatch `>=1.17.0`, pytest `>=9.1.1`, pytest-asyncio `>=1.4.0`, ruff `>=0.15.20`. Lock file refreshed via `uv lock`.
+
+### Fixed
+
+- **A2A event scope test** — `tests/test_a2a.py` now walks FastAPI included-router wrappers when locating `/a2a/events`, preserving the read-scope assertion under FastAPI `0.139.0`.
+
+| Status     | Count |
+| ---------- | ----- |
+| ✅ Passed  | 683   |
+| 🤔 Skipped | 0     |
+| 🔴 Failed  | 0     |
+| ⏱️ in      | 56s   |
+
+## [1.3.0] - 2026-07-02

Relevance

⭐⭐⭐ High

Team previously accepted CHANGELOG accuracy fixes (PR#19) and routinely updates CHANGELOG for
releases/maintenance (PR#33).

PR-#19
PR-#33

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The changelog shows v1.3.0-scoped bullets under [Unreleased] above the [1.3.0] header, and
bumpversion is configured to create releases by replacing the ## [Unreleased] line—so content left
there will not automatically move into the new release section.

docs/CHANGELOG.md[13-34]
pyproject.toml[142-155]
PR-#19

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The changelog entries describing changes for v1.3.0 are currently recorded under `## [Unreleased]` even though the `## [1.3.0] - 2026-07-02` section exists below.

## Issue Context
The repo’s bumpversion config inserts a new release header at `## [Unreleased]` (string replace), so any already-released bullets left under Unreleased can remain above the release header and appear as “unreleased” for subsequent releases.

## Fix Focus Areas
- docs/CHANGELOG.md[13-34]
- pyproject.toml[142-155]

## Suggested fix
1. Move the `### Changed` and `### Fixed` subsections (and the associated test-run table, if it is meant to describe the 1.3.0 release) from under `## [Unreleased]` to under `## [1.3.0] - 2026-07-02`.
2. Leave `## [Unreleased]` empty (or with placeholder headings) so future changes land there correctly.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

[qodo-code-review]

1. Unreleased contains v1.3.0 notes 🐞 Bug ⚙ Maintainability

docs/CHANGELOG.md places the v1.3.0 dependency-bump and test-fix bullets under the "[Unreleased]"
heading even though a dated "[1.3.0]" section is added immediately below. This makes the changelog
ambiguous and can cause the next bumpversion run (which inserts a new version header at
"[Unreleased]") to leave already-released entries in the wrong section.

Agent Prompt

## Issue description
The changelog entries describing changes for v1.3.0 are currently recorded under `## [Unreleased]` even though the `## [1.3.0] - 2026-07-02` section exists below.

## Issue Context
The repo’s bumpversion config inserts a new release header at `## [Unreleased]` (string replace), so any already-released bullets left under Unreleased can remain above the release header and appear as “unreleased” for subsequent releases.

## Fix Focus Areas
- docs/CHANGELOG.md[13-34]
- pyproject.toml[142-155]

## Suggested fix
1. Move the `### Changed` and `### Fixed` subsections (and the associated test-run table, if it is meant to describe the 1.3.0 release) from under `## [Unreleased]` to under `## [1.3.0] - 2026-07-02`.
2. Leave `## [Unreleased]` empty (or with placeholder headings) so future changes land there correctly.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools