cello-framework 1.2.2__tar.gz → 1.2.4__tar.gz

{cello_framework-1.2.2 → cello_framework-1.2.4}/CLAUDE.md

@@ -4,7 +4,7 @@
 
 **Cello** is an ultra-fast, Rust-powered Python async web framework designed to achieve C-level performance on the hot path while maintaining Python's developer experience. It's the successor to frameworks like FastAPI, Robyn, and Litestar, combining their best features with pure Rust implementation for maximum performance.
 
-**Version:** 1.2.2
+**Version:** 1.2.4
 **License:** MIT
 **Python Requirement:** 3.12+
 **Author:** Jagadeesh Katla
@@ -346,6 +346,8 @@ def handle_value_error(request, exc):
 
 ## Version History
 
+- **v1.2.4**: Critical fix — async handlers broken since v1.2.1; `pyo3_asyncio::tokio::into_future` failed silently after server startup switched to `py.allow_threads + block_on` (v1.2.1), causing all `async def` handlers to return 500; fixed by driving coroutines via `tokio::task::spawn_blocking + asyncio.run()` (`handler.rs`)
+- **v1.2.3**: Full middleware Python API — `cello.middleware` module with `JwtAuth`, `BasicAuth`, `ApiKeyAuth`, `CsrfConfig`, `AdaptiveRateLimitConfig`; `app.use()` dispatcher; 6 new `enable_*` methods on App (`enable_jwt`, `enable_session`, `enable_security_headers`, `enable_csrf`, `enable_basic_auth`, `enable_api_key`); all docs import paths corrected (`from cello import RoleGuard` not `cello.guards`)
 - **v1.2.2**: Security & bug fixes — CSRF `HttpOnly` on double-submit cookie (critical, broke all AJAX CSRF); all middleware `skip_path` prefix bypass fixed via `path_matches_skip()` helper; `FixedWindowStore` window_start never updated after reset; unused `mut` cleaned in minijinja tests
 - **v1.2.1**: Bug fixes — server port never bound (`pyo3_asyncio` replaced with native `py.allow_threads` + `tokio::block_on`); `ProblemDetails` was missing from Python module export; `And`/`Or` guards now accept both `*args` and list styles; CSRF `HttpOnly` removed from double-submit cookie (JS must read it); `FixedWindowStore` window_start never updated after reset; all middleware `skip_path` used raw `starts_with` allowing prefix bypass; doc corrections (`type_uri` not `type_url`)
 - **v1.2.0**: Bug fixes (shutdown coroutine never awaited, KeyboardInterrupt in shutdown handler, `request.redis` AttributeError); Redis Lua scripting (`eval`, `evalsha`, `script_load`); Rust-native `AsyncClient` backed by `reqwest + Tokio` — GIL never held during HTTP I/O, HTTP/2, gzip, rustls

{cello_framework-1.2.2 → cello_framework-1.2.4}/Cargo.lock

@@ -341,7 +341,7 @@ dependencies = [
 
 [[package]]
 name = "cello-framework"
-version = "1.2.2"
+version = "1.2.4"
 dependencies = [
  "async-graphql",
  "async-graphql-value",

{cello_framework-1.2.2 → cello_framework-1.2.4}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "cello-framework"
-version = "1.2.2"
+version = "1.2.4"
 edition = "2021"
 description = "Ultra-fast Rust-powered Python async web framework"
 license = "MIT"

{cello_framework-1.2.2 → cello_framework-1.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cello-framework
-Version: 1.2.2
+Version: 1.2.4
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/features/core/async.md

@@ -254,8 +254,7 @@ All Python-side decorators and wrappers in Cello automatically detect whether a
 | Pydantic validation | Yes | Validates the request body, then awaits the handler |
 
 ```python
-from cello import App, cache
-from cello.guards import RoleGuard
+from cello import App, cache, RoleGuard
 from pydantic import BaseModel
 
 app = App()

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/features/core/blueprints.md

@@ -183,8 +183,7 @@ app.register_blueprint(v2)
 Apply middleware to all routes within a blueprint. Async handlers work seamlessly with blueprint-level middleware and per-route guards:
 
 ```python
-from cello import App, Blueprint
-from cello.guards import RoleGuard, Authenticated
+from cello import App, Blueprint, RoleGuard, Authenticated
 
 # Public blueprint -- no auth required
 public_bp = Blueprint("/public")

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/features/middleware/overview.md

@@ -172,8 +172,7 @@ app.use(ApiKeyAuth(keys={"key1": "service-a"}, header="X-API-Key"))
 All Python-side middleware wrappers -- including the `@cache` decorator, guard wrappers, and Pydantic validation -- fully support async handlers. Each wrapper uses `inspect.iscoroutinefunction()` to detect async handlers at decoration time and generates the appropriate sync or async wrapper. This means you can freely use `async def` handlers with any combination of caching, guards, and validation without encountering unawaited coroutine issues.
 
 ```python
-from cello import App, cache
-from cello.guards import RoleGuard
+from cello import App, cache, RoleGuard
 from pydantic import BaseModel
 
 class Item(BaseModel):

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/features/security/overview.md

@@ -261,7 +261,7 @@ app.use(api_auth)
 Control access with composable guards:
 
 ```python
-from cello.guards import RoleGuard, PermissionGuard, And, Or
+from cello import RoleGuard, PermissionGuard, And, Or
 
 # Simple role check
 admin_only = RoleGuard(["admin"])

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/index.md

@@ -37,7 +37,7 @@ hide:
 [:material-package-variant: PyPI](https://pypi.org/project/cello-framework/){ .md-button }
 
 <div class="hero-badges">
-  <code class="badge-version">v1.2.0</code>
+  <code class="badge-version">v1.2.4</code>
   <code class="badge-tests">441 tests passing</code>
   <code class="badge-license">MIT License</code>
   <code class="badge-python">Python 3.12+</code>
@@ -178,8 +178,7 @@ hide:
 === ":material-api: REST API"
 
     ```python
-    from cello import App, Response, Blueprint
-    from cello.guards import RoleGuard
+    from cello import App, Response, Blueprint, RoleGuard
 
     app = App()
     api = Blueprint("api", url_prefix="/api/v1")
@@ -371,21 +370,21 @@ How Cello stacks up against popular Python web frameworks (4 workers, 5 processe
 
 <!-- ===== WHAT'S NEW ===== -->
 
-## :material-creation: What's New in v1.2.0
+## :material-creation: What's New in v1.2.4
 
 <div class="whats-new-box" markdown>
 
-!!! tip "v1.2.0 -- Bug Fixes & Rust-Native AsyncClient"
+!!! tip "v1.2.4 — Critical Fix: async def Handlers Now Work Correctly"
 
-    Cello v1.2.0 ships critical bug fixes and a brand-new Rust-native HTTP client — the GIL is never held during HTTP I/O.
+    Cello v1.2.4 fixes a critical regression introduced in v1.2.1 where all `async def` route handlers silently returned 500 errors.
 
-    - :material-bug-check: **Critical Bug Fixes** -- Shutdown coroutine now properly awaited, `KeyboardInterrupt` handled cleanly in shutdown handler, `request.redis` AttributeError resolved.
+    - :material-bug-check: **Async handlers fixed** — `async def` handlers now execute correctly; `pyo3_asyncio::tokio::into_future` was failing silently after the v1.2.1 server startup change.
 
-    - :material-language-rust: **Rust-Native AsyncClient** -- Backed by `reqwest + Tokio` with HTTP/2, gzip, and rustls. GIL is never held during HTTP I/O — true async performance.
+    - :material-language-rust: **`spawn_blocking + asyncio.run()`** — coroutines are now driven via Tokio's blocking thread pool, releasing the main Tokio thread during Python I/O waits.
 
-    - :material-database: **Redis Lua Scripting** -- New `eval`, `evalsha`, and `script_load` methods for atomic server-side operations.
+    - :material-test-tube: **New async client test suite** — `tests/verify_async_client.py` covers all HTTP methods with a self-contained local echo server.
 
-    [:material-tag: Full Release Notes](releases/v1.2.0.md){ .md-button .md-button--primary }
+    [:material-tag: Full Release Notes](releases/v1.2.4.md){ .md-button .md-button--primary }
     [:material-book-open-variant: Migration Guide](releases/migration.md){ .md-button }
 
 </div>

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/overrides/main.html

@@ -2,7 +2,7 @@
 
 {% block announce %}
 <span class="cello-announce">
-  Cello v1.2.0 — Redis Lua scripting, Rust-native AsyncClient, critical bug fixes
+  Cello v1.2.4 — Critical fix: async handlers now work correctly
   <a href="{{ base_url }}/releases/" class="cello-announce-link">
     Release notes →
   </a>
@@ -37,7 +37,7 @@
     "operatingSystem": "Linux, macOS, Windows",
     "programmingLanguage": ["Python", "Rust"],
     "license": "https://opensource.org/licenses/MIT",
-    "softwareVersion": "1.2.0",
+    "softwareVersion": "1.2.4",
     "author": {
       "@type": "Person",
       "name": "Jagadeesh Katla",

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/reference/api/app.md

@@ -728,9 +728,9 @@ Add a global guard to all routes.
 > *Since v0.5.0*
 
 ```python
-from cello.guards import AuthenticatedGuard
+from cello import Authenticated
 
-app.add_guard(AuthenticatedGuard())
+app.add_guard(Authenticated())
 ```
 
 | Parameter | Type | Description |

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/reference/index.md

@@ -78,7 +78,7 @@ The building blocks of every Cello application -- from creating your app to hand
 
     Role-based and permission-based access control. Composable guards that protect routes and blueprints.
 
-    **Key classes:** `RoleGuard` `PermissionGuard` `CompositeGuard`
+    **Key classes:** `RoleGuard` `PermissionGuard` `Authenticated` `And` `Or` `Not`
 
     [:octicons-arrow-right-24: Guards Reference](api/guards.md)
 
@@ -166,8 +166,8 @@ The most commonly used classes and functions at a glance.
 | [`Response`](api/response.md) | `cello` | HTTP response builder |
 | [`Blueprint`](api/blueprint.md) | `cello` | Route grouping |
 | [`Depends`](api/context.md) | `cello` | Dependency injection marker |
-| [`RoleGuard`](api/guards.md) | `cello.guards` | Role-based access guard |
-| [`PermissionGuard`](api/guards.md) | `cello.guards` | Permission-based access guard |
+| [`RoleGuard`](api/guards.md) | `cello` | Role-based access guard |
+| [`PermissionGuard`](api/guards.md) | `cello` | Permission-based access guard |
 | [`JwtConfig`](config/security.md) | `cello.middleware` | JWT authentication config |
 | [`RateLimitConfig`](config/middleware.md) | `cello.middleware` | Rate limiting config |
 | [`SessionConfig`](config/security.md) | `cello.middleware` | Session management config |
@@ -219,8 +219,7 @@ The most commonly used classes and functions at a glance.
 === "Guards & Auth"
 
     ```python
-    from cello import App
-    from cello.guards import RoleGuard, PermissionGuard
+    from cello import App, RoleGuard, PermissionGuard
     from cello.middleware import JwtConfig, JwtAuth
 
     app = App()

cello_framework-1.2.4/docs/releases/index.md

@@ -0,0 +1,303 @@
+---
+title: Release Notes
+description: Version history, changelogs, and migration guides for every Cello Framework release
+icon: material/tag-multiple
+tags:
+  - Release Notes
+  - Changelog
+  - v1.2.4
+  - Migration
+---
+
+# :material-tag-multiple: Release Notes
+
+---
+
+## :material-new-box: Latest Release — v1.2.4
+
+!!! success "Cello v1.2.4 — Critical Fix: async def Handlers (June 2026)"
+
+    Fixes a critical regression introduced in v1.2.1 where all `async def` route handlers silently returned 500 errors due to `pyo3_asyncio` not being initialised after the server startup change.
+
+    **Highlights:**
+
+    - :material-bug-check: **All `async def` handlers now work** — coroutines are driven via `tokio::task::spawn_blocking + asyncio.run()`
+    - :material-test-tube: **New test suite** — `tests/verify_async_client.py` covers all HTTP methods with a local echo server
+    - :material-arrow-up: **Drop-in upgrade** from v1.2.3 — no API changes
+
+    [:octicons-arrow-right-24: Full v1.2.4 Release Notes](v1.2.4.md){ .md-button .md-button--primary }
+    [:octicons-arrow-right-24: Migration Guide](migration.md){ .md-button }
+
+---
+
+## :material-timeline: Version Timeline
+
+```mermaid
+timeline
+    title Cello Framework Releases
+    2026-06 : v1.2.4 - Critical Fix: async def Handlers
+            : v1.2.3 - Full Middleware Python API & Docs Fixes
+            : v1.2.2 - Security & Bug Fixes (CSRF, skip_path, rate limiter)
+            : v1.2.1 - Critical Bug Fixes (server bind, ProblemDetails export)
+            : v1.2.0 - Redis Lua Scripting & Rust-Native AsyncClient
+            : v1.1.0 - MiniJinja Jinja2-Compatible Templates
+    2026-02 : v1.0.1 - Cross-Platform & Compatibility Patch
+            : v1.0.0 - Production Ready (Stable)
+            : v0.10.0 - Event Sourcing, CQRS, Saga
+            : v0.9.0 - GraphQL, gRPC, Message Queues
+            : v0.8.0 - Database Pooling, Redis, Transactions
+    2026-01 : v0.7.0 - OpenTelemetry, Health Checks
+    2025-12 : v0.6.0 - Smart Caching, Adaptive Rate Limiting
+    2025-10 : v0.5.0 - DI, Guards (RBAC), Prometheus
+    2025-08 : v0.4.0 - JWT, Sessions, Cluster Mode
+    2025-06 : v0.3.0 - WebSocket, SSE, Blueprints
+```
+
+---
+
+## :material-history: All Releases
+
+<div class="grid cards" markdown>
+
+-   :material-bug-check:{ .lg .middle } **v1.2.4** — Critical Async Fix
+
+    ---
+
+    Fixes all `async def` handlers returning 500 since v1.2.1. Coroutines now driven via `spawn_blocking + asyncio.run()`.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.2.4.md)
+
+-   :material-api:{ .lg .middle } **v1.2.3** — Full Middleware Python API
+
+    ---
+
+    `cello.middleware` module, `app.use()` dispatcher, 6 new `enable_*` methods, all doc import paths corrected.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.2.3.md)
+
+-   :material-shield-bug:{ .lg .middle } **v1.2.2** — Security & Bug Fixes
+
+    ---
+
+    Critical CSRF `HttpOnly` fix (broke all AJAX apps), auth `skip_path` prefix bypass fix, rate limiter fixed-window reset bug.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.2.2.md)
+
+-   :material-bug-check:{ .lg .middle } **v1.2.1** — Critical Bug Fixes
+
+    ---
+
+    Server port never bound, `ProblemDetails` missing from Python export, `And`/`Or` guard `*args` style, `HttpOnly` removed from CSRF cookie.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.2.1.md)
+
+-   :material-database-sync:{ .lg .middle } **v1.2.0** — Redis Lua & AsyncClient
+
+    ---
+
+    Redis Lua scripting (`eval`, `evalsha`, `script_load`), Rust-native `AsyncClient` backed by `reqwest + Tokio` — GIL never held during HTTP I/O.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.2.0.md)
+
+-   :material-file-code:{ .lg .middle } **v1.1.0** — MiniJinja Templates
+
+    ---
+
+    Jinja2-compatible template engine via `minijinja` Rust crate. `app.enable_templates()`, `app.render()`, globals, auto HTML-escaping.
+
+    :material-calendar: June 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.1.0.md)
+
+-   :material-wrench:{ .lg .middle } **v1.0.1** — Cross-Platform & Compatibility Patch
+
+    ---
+
+    Windows multi-worker subprocess mode, ARM JSON fallback, async guard/cache/blueprint compatibility, export completeness.
+
+    :material-calendar: February 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.0.1.md)
+
+-   :material-check-decagram:{ .lg .middle } **v1.0.0** — Production Ready
+
+    ---
+
+    Stable release with performance optimizations, API stability guarantees, and the complete feature set.
+
+    :material-calendar: February 2026
+
+    [:octicons-arrow-right-24: Release Notes](v1.0.0.md)
+
+-   :material-star-shooting:{ .lg .middle } **v0.10.0** — Advanced Patterns
+
+    ---
+
+    Event Sourcing, CQRS, and the Saga Pattern for distributed transaction coordination.
+
+    :material-calendar: February 2026
+
+    [:octicons-arrow-right-24: Release Notes](v0.10.0.md)
+
+-   :material-api:{ .lg .middle } **v0.9.0** — API Protocols
+
+    ---
+
+    GraphQL support, gRPC integration, and message queue adapters for Kafka and RabbitMQ.
+
+    :material-calendar: February 2026
+
+    [:octicons-arrow-right-24: Release Notes](v0.9.0.md)
+
+-   :material-database:{ .lg .middle } **v0.8.0** — Data Layer
+
+    ---
+
+    Database connection pooling, Redis integration, and transaction support with automatic rollback.
+
+    :material-calendar: February 2026
+
+    [:octicons-arrow-right-24: Release Notes](v0.8.0.md)
+
+-   :material-eye:{ .lg .middle } **v0.7.0** — Enterprise Observability
+
+    ---
+
+    OpenTelemetry distributed tracing, structured health check endpoints, and GraphQL support.
+
+    :material-calendar: January 2026
+
+    [:octicons-arrow-right-24: Release Notes](v0.7.0.md)
+
+-   :material-speedometer:{ .lg .middle } **v0.6.0** — Smart Middleware
+
+    ---
+
+    Intelligent caching with TTL, adaptive rate limiting based on system load, DTO validation, and circuit breaker.
+
+    :material-calendar: December 2025
+
+    [:octicons-arrow-right-24: Release Notes](v0.6.0.md)
+
+-   :material-shield-check:{ .lg .middle } **v0.5.0** — Security & DI
+
+    ---
+
+    Dependency injection, composable RBAC guards, Prometheus metrics, and OpenAPI generation.
+
+    :material-calendar: October 2025
+
+    [:octicons-arrow-right-24: Release Notes](v0.5.0.md)
+
+-   :material-lock:{ .lg .middle } **v0.4.0** — Auth & Sessions
+
+    ---
+
+    JWT authentication, token-bucket rate limiting, secure cookie sessions, security headers, and cluster mode.
+
+    :material-calendar: August 2025
+
+    [:octicons-arrow-right-24: Release Notes](v0.4.0.md)
+
+-   :material-access-point:{ .lg .middle } **v0.3.0** — Real-time
+
+    ---
+
+    WebSocket support, Server-Sent Events, multipart form handling, and Flask-inspired blueprints.
+
+    :material-calendar: June 2025
+
+    [:octicons-arrow-right-24: Release Notes](v0.3.0.md)
+
+</div>
+
+---
+
+## :material-shield-half-full: Support Policy
+
+| Version | Status | Support Until |
+|:--------|:-------|:--------------|
+| **1.2.x** | :material-check-circle:{ style="color: #4caf50" } **Active** | Current |
+| 1.1.x | :material-wrench:{ style="color: #ffab40" } Maintenance | December 2026 |
+| 1.0.x | :material-wrench:{ style="color: #ffab40" } Maintenance | October 2026 |
+| 0.10.x | :material-shield-alert:{ style="color: #ff9800" } Security Only | August 2026 |
+| < 0.10 | :material-close-circle:{ style="color: #f44336" } End of Life | — |
+
+!!! info "Version policy"
+
+    Cello follows [Semantic Versioning](https://semver.org/). Starting with **v1.0.0**, the public API is stable — no breaking changes until v2.0. **Maintenance** releases receive bug fixes. **Security Only** releases receive critical security patches only.
+
+---
+
+## :material-arrow-up-bold-circle: Upgrading
+
+=== "pip"
+
+    ```bash
+    # Upgrade to the latest stable release
+    pip install --upgrade cello-framework
+
+    # Pin to a specific version
+    pip install cello-framework==1.2.4
+    ```
+
+=== "requirements.txt"
+
+    ```text
+    cello-framework>=1.2.4,<2.0.0
+    ```
+
+=== "pyproject.toml"
+
+    ```toml
+    [project]
+    dependencies = [
+        "cello-framework>=1.2.4,<2.0.0",
+    ]
+    ```
+
+!!! warning "Read the migration guide before upgrading"
+
+    Breaking changes are documented in the [Migration Guide](migration.md). Always review it before bumping a minor version.
+
+---
+
+## :material-file-document-multiple: Additional Resources
+
+<div class="grid cards" markdown>
+
+-   :material-format-list-bulleted:{ .lg .middle } **Full Changelog**
+
+    ---
+
+    Every commit, bug fix, and improvement in one place.
+
+    [:octicons-arrow-right-24: Changelog](changelog.md)
+
+-   :material-directions-fork:{ .lg .middle } **Migration Guide**
+
+    ---
+
+    Step-by-step instructions for upgrading between versions.
+
+    [:octicons-arrow-right-24: Migration Guide](migration.md)
+
+</div>
+
+---
+
+## :material-bell-ring: Stay Updated
+
+- :material-star: [Star the repo on GitHub](https://github.com/jagadeesh32/cello) to show support and get notified
+- :material-rss: [Releases RSS Feed](https://github.com/jagadeesh32/cello/releases.atom) for automated notifications
+- :fontawesome-brands-discord: [Join Discord](https://discord.gg/cello) for release announcements and discussion

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/releases/v0.5.0.md

@@ -65,14 +65,18 @@ def profile(request, user=Depends(get_current_user)):
 
 Composable access control guards that run before the handler. Guards inspect the request context and either allow or deny access.
 
+!!! note "API names updated in v1.x"
+    `RoleGuard`, `PermissionGuard`, `AuthenticatedGuard`, `AndGuard`, `OrGuard`, `NotGuard` were the original v0.5.0 names.
+    Current names: `RoleGuard` → still `RoleGuard` (from `cello`), `PermissionGuard` → still `PermissionGuard` (from `cello`),
+    `AuthenticatedGuard` → `Authenticated`, `AndGuard` → `And`, `OrGuard` → `Or`, `NotGuard` → `Not`.
+
 ```python
-from cello import App
-from cello.guards import RoleGuard, PermissionGuard, AuthenticatedGuard
+from cello import App, RoleGuard, PermissionGuard, Authenticated
 
 app = App()
 
 # Require authentication
-@app.get("/dashboard", guards=[AuthenticatedGuard()])
+@app.get("/dashboard", guards=[Authenticated()])
 def dashboard(request):
     return {"welcome": request.context.get("user_id")}
 
@@ -90,18 +94,18 @@ def delete_user(request):
 **Composable logic with And, Or, Not:**
 
 ```python
-from cello.guards import AndGuard, OrGuard, NotGuard
+from cello import And, Or, Not, RoleGuard, PermissionGuard, Authenticated
 
 # Admin OR has special permission
-flexible = OrGuard([
+flexible = Or([
     RoleGuard(["admin"]),
     PermissionGuard(["elevated:access"]),
 ])
 
 # Authenticated AND not banned
-safe = AndGuard([
-    AuthenticatedGuard(),
-    NotGuard(RoleGuard(["banned"])),
+safe = And([
+    Authenticated(),
+    Not(RoleGuard(["banned"])),
 ])
 
 @app.get("/resource", guards=[flexible])

{cello_framework-1.2.2 → cello_framework-1.2.4}/docs/releases/v0.6.0.md

@@ -56,17 +56,10 @@ def create_user(request):
 Rate limits now adjust based on server health:
 
 ```python
-from cello.middleware import AdaptiveRateLimitConfig
-
-config = AdaptiveRateLimitConfig(
-    base_requests=100,
-    window=60,
-    cpu_threshold=0.8,      # Reduce limits at 80% CPU
-    memory_threshold=0.9,   # Reduce limits at 90% memory
-    latency_threshold=100,  # Reduce limits if latency > 100ms
-    min_requests=10         # Never go below 10 req/min
-)
+from cello import App, RateLimitConfig
 
+# Adaptive rate limiting (adjusts based on server load)
+config = RateLimitConfig.adaptive(capacity=100, refill_rate=10)
 app.enable_rate_limit(config)
 ```
 
@@ -109,18 +102,15 @@ Invalid requests return RFC 7807 Problem Details:
 Protect against cascading failures:
 
 ```python
-from cello.middleware import CircuitBreaker, CircuitBreakerConfig
+from cello import App
 
-config = CircuitBreakerConfig(
-    failure_threshold=5,     # Open after 5 failures
-    recovery_timeout=30,     # Try again after 30 seconds
-    half_open_requests=3     # Allow 3 test requests
+app.enable_circuit_breaker(
+    failure_threshold=5,   # Open after 5 failures
+    reset_timeout=30,      # Try again after 30 seconds
+    half_open_target=3,    # Allow 3 test requests in half-open state
 )
 
-circuit = CircuitBreaker(config)
-
 @app.get("/external-api")
-@circuit.protect
 async def call_external(request):
     return await external_service.fetch()
 ```
@@ -130,8 +120,7 @@ async def call_external(request):
 Guards can now be applied at multiple levels:
 
 ```python
-from cello import App, Blueprint
-from cello.guards import RoleGuard, PermissionGuard
+from cello import App, Blueprint, RoleGuard, PermissionGuard
 
 # Controller-level guard
 admin_bp = Blueprint("/admin", guards=[RoleGuard(["admin"])])
@@ -181,9 +170,7 @@ The cache middleware configuration has changed:
 app.enable_cache(max_age=300)
 
 # After (v0.6.0)
-from cello.middleware import CacheConfig
-config = CacheConfig(default_ttl=300, max_size=1000)
-app.enable_cache(config)
+app.enable_caching(ttl=300)
 ```
 
 ### Rate Limit Response