Release fix: lowercase GHCR tags and bump to v0.1.1

[EshwarCVS]

Summary

This PR fixes the failed release run and prepares a valid initial publish:

• Fixes Docker publish failure by lowercasing GHCR owner in image tags
• Bumps version from 0.1.0 to 0.1.1 to avoid PyPI filename reuse rejection
• Keeps stage→master flow intact

Root cause from failed v0.1.0 run

1. Docker publish failed because ghcr.io/FasterApiWeb/... contains uppercase owner; GHCR requires lowercase repository names.
2. PyPI rejected 0.1.0 upload because those filenames were already used previously and cannot be reused.

Result

After merge, tagging v0.1.1 on master should produce a successful release.

Made with Cursor

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

Benchmark Results

Automated benchmark on ubuntu-latest, Python 3.13. Baseline is from README (Apple Silicon).
CI runners are slower than local machines — compare the speedup ratio, not raw req/s.

Framework-Level (Direct ASGI, 50,000 requests)

Endpoint	FasterAPI	FastAPI	Speedup	vs Baseline Speedup
GET /health	211,141/s	19,264/s	10.96x	🟢 +60.0%
GET /users/{id}	181,456/s	13,719/s	13.23x	🟢 +51.5%
POST /users	108,491/s	11,028/s	9.84x	🟢 +37.6%

Routing (100 routes, 1.5M lookups)

Router	Ops/s	Speedup	vs Baseline
Radix tree	870,891	8.8x	🟢 +15.8%
Regex	98,972	1.0x

How to read this

• Speedup = FasterAPI req/s ÷ FastAPI req/s (higher is better)
• vs Baseline compares the speedup ratio against the README baseline
• 🟢 = improved, ⚪ = within noise, 🔴 = regression (>5% drop in speedup)
• Raw req/s will differ from README (CI runner vs Apple Silicon) — the ratio is what matters