chore: release main

[github-actions]

🤖 I have created a release beep boop

ask-plugin: 0.2.2

0.2.2 (2026-04-08)

Features

• registry: edge cache /api/registry/** via Nitro routeRules (#36) (1c9b7db), closes #34

---

This PR was generated with Release Please. See documentation.

---

Summary by cubic

Release ask-plugin v0.2.2 with edge caching for registry API routes to improve performance and reduce origin load. Updates version metadata for the plugin and manifest.

• New Features
  • Edge cache /api/registry/** via Nitro routeRules to lower latency and cut backend hits.

^{Written for commit 002d0cc. Summary will update on new commits.}

[cloudflare-workers-and-pages]

Deploying ask-registry with    Cloudflare Pages

Latest commit:	002d0cc
Status:	✅  Deploy successful!
Preview URL:	https://0428c89e.ask-registry.pages.dev
Branch Preview URL:	https://release-please--branches--ma-vd2h.ask-registry.pages.dev

View logs

[cubic-dev-ai]

No issues found across 3 files

_{Auto-approved: Automated release PR that only updates version metadata and the changelog. No source code logic changed.}

Architecture diagram

sequenceDiagram
    participant Client as AI Agent / Client
    participant Edge as Edge Network (Nitro Cache)
    participant Origin as Nitro Origin Server
    participant DB as Registry Database

    Note over Client,DB: Request Flow for /api/registry/**

    Client->>Edge: GET /api/registry/entry-name
    
    alt NEW: Edge Cache Hit
        Edge-->>Client: 200 OK (Cached Response)
    else NEW: Edge Cache Miss / Expired
        Edge->>Origin: Forward Request to Origin
        Origin->>DB: Query registry metadata
        DB-->>Origin: Entry details
        Origin->>Origin: Process response
        Origin-->>Edge: Return Data + Cache-Control Headers
        Edge->>Edge: NEW: Cache response based on routeRules
        Edge-->>Client: 200 OK
    end

    Note over Edge,Origin: routeRules applied to /api/registry/** path

Loading

[github-actions]

🤖 Created releases:

• ask-plugin-v0.2.2

🌻