Repository navigation
Description
2026-11-21 code validation update: The #85 public-cap mutation fix is validated by all new-HEAD workflows at
098e37cb(full counteraudit handoff); it is not yet independently approved or merged. #92 gates the actual candidate/release; #91 remains 0/2; Pages #48 still not verified live. Competitive positioning: migration credibility over feature count. No release/promotion executed.
2026-11-21 launch dependencies update: See current comparative audit and launch strategy and exact 0.6.0 candidate-to-publication checklist #92. #85 read-only
max_entriescounteraudit fix is on draft HEAD098e37cb..., subject to a fresh complete CI and external signoff. #91 external consumers still 0/2, public Pages #48 unverified, no 0.6 candidate/tag/PyPI released. First actively promoted release ≠ first public package; latest published remains 0.5.0.
2026-11-21 adoption gate update: PR #89 is MERGED at
b118890c67c10cc6315af21f03e8633b7c3d703c; GitHub Pages remains not activated or verified. PR #90 is MERGED atd36a21388f25ed9d9528d4ac8ed832a76b571eedand provides the reproducible in-repository, published 0.2.2 → 0.5.0 InMemory onboarding demo, with final-head successful CI/CodeQL and Linux Python 3.11/3.12 checks and a required 0.6.0 pinned-artifact refresh checklist. Windows/macOS remain unverified. PR #90 counts as ZERO of the TWO independently run external consumer exercises. Track separately: (A) fresh external FastAPI app on InMemory+Redis and (B) actual externalfastapi-cache2migration including scoped cleanup/rollback. Protocol and evidence ledger: #91. Log platform, distribution hashes, Python/FastAPI/Redis versions, consent to quote feedback, reproduced issues and outcome. #85 remains unmerged until independent review of the expiry heap, LRU and concurrency invariants. No 0.6.0 release or public announcement approved. Earlier planning text below is historical where inconsistent.
2026-11-21 promotion readiness update: The 0.6.0 campaign remains not authorized / not published. #85 is now cleanly rebased on post-#87 stable, with full-capacity LRU/expiry 10k/100k CI and deterministic heap fuzz; require final exact-head pass and independent review. #89 proposes a manual-only GitHub Pages workflow and competitive guide; its intended URL is not confirmed live. Add Python Weekly to the editorial-outreach shortlist, alongside PyCoder's Weekly; verify Python Weekly's current submission channel rather than assuming an accessible form. Before any Reddit post by
u/Calm_Exchange_989, check account age/karma/activity from the live platform, each subreddit's rules and the actual active weekly thread. The account's age/karma have not been verified by this plan. Reddit's Reddiquette calls 9:1 a rule of thumb (not an automatic universal pass); avoid self-promo-dominant accounts and never game karma. Hacker News announcements must be personally authored by the maintainer, not AI-generated, without solicited votes. Do not approach curated directories before independent adoption evidence.
Objective — first coordinated public launch: 0.6.0
The 0.5.0 PyPI release is already public. 0.6.0 is the intended FIRST intentionally promoted release, not the first PyPI release. No date or posting is authorized yet. The main promise is a maintained, independently tested drop-in migration from fastapi-cache2==0.2.2 (same fastapi_cache import and ordinary default keys) with safer HTTP/private-response behavior and Redis compatibility. Opt-in features are supporting evidence, not the headline. Track version scope in #86.
Hard launch gates
- Documentation source and link checks: #87 merged at
8c079c8after 32/32 green checks, including built-site link/anchor checker and installation/migration docs. - Publicly hosted documentation: docs: build versioned documentation site after PR #52 quickstart #48 remains open; approve host, versioned URL, then independently verify the live pages and links before publicly advertising a website.
- #54 / PR #85: redesign O(N) per-write scan; demonstrate 10k/100k bounded write scaling on Python 3.8 and modern Python; benchmark and actual concurrency/expiry test pass.
max_entriesmust remain opt-in, per-process, entry count only. - #50: decide by feature freeze whether opt-in privacy-safe events are included. They must NOT delay the release indefinitely; don't advertise unshipped events.
- #53 review: no unmitigated library-controlled cross-tenant leakage, documented custom auth/proxy/cardinality limitations and clear safe-by-default examples.
- Two independently run consumer exercises: one fresh FastAPI app (InMemory+Redis), one real
fastapi-cache2migration (separate venvs, cache cleanup/rollback) with reproducible notes and permission to quote any feedback. - Final 0.6.0 versioned wheel/sdist, changelog, installed smoke, source-SHA migration parity, supported Python/Redis CI, CodeQL, current installed-security profiles, authenticated Dependabot delta, scoped risk decision and independent reviewer signoff. Never inherit 0.5.0 hashes/approvals.
- Public demo (<5 minutes), verified copy-paste install with exact pin, migration comparison and screenshots of docs if useful; don't imply a universal tenant isolation or Redis Cluster guarantee.
- Explicit release approval, tag/TestPyPI/PyPI/GitHub Release and final provenance, before public announcement.
Where to introduce it (priority, channel rules and format)
- Own sources (launch day): GitHub repo front-page clarity and topics, pinned release, quickstart, changelog, badges, hosted docs if actually deployed, PyPI description. Original demo/benchmark results with traceable commands, not unsupported performance claims.
- PyCoder's Weekly submission: verified official link submission form; submit a useful migration walkthrough and repo link; inclusion is editorial, not guaranteed.
- r/Python: post in the monthly showcase thread per contemporary moderator notices; don't submit a separate self-promo feed post unless the rules later explicitly allow it. Provide source URL, compatibility limits, ask for concrete migration feedback.
- r/opensource weekly showcase: a current (2026-11-17) explicitly designated thread for open-source project introductions. Post a useful concise demo with license/repo and real usage, under current thread rules. Recheck the active weekly thread at launch.
- FastAPI Discord: official docs link to the community chat. Participate helpfully first; ask moderators/inspect channel rules before sharing a library link, never mass-send DMs.
- r/FastAPI: check current rules/mod permission first; prefer a technical before/after tutorial with verified behavior rather than naked promo. Previous moderator guidance rejects blatant self promotion.
- Show HN: consider one genuine, hands-on demonstration only if the author can personally answer technical questions; HN says a mere version bump is not enough. HN guidelines prohibit generated/AI-edited post text and vote solicitation. The maintainer should write the HN submission personally; never autopost or coordinate upvotes.
- Technical articles / professional network: a developer-authored migration case study on dev.to, personal blog or LinkedIn, focused on evidence (import preserved, Redis 4–8 conditional, response/private safety, exact artifact audits). Separate topic/angle rather than duplicating generic promotional copy.
- Curated directories later: awesome-fastapi PR template notes that projects under one year or under 100 stars might not qualify; do not send a premature PR. Check other directories for submission rules at the time.
Messaging rules
- What is true: 0.5.0 published, opt-in
vary_headers, ordinary key-golden migration, Redis standalone client profiles; further features only once a 0.6.0 wheel ships. - Do not claim: officially supported by FastAPI/upstream/Redis, 0 vulnerabilities, 100% drop-in for private applications, production-grade memory byte caps, Redis Cluster namespace clearing, generic auto-tenant isolation or universal rollback.
- Avoid fake endorsements, performance multipliers without repeatable measurements, paid traffic campaigns, repetitive posts across subreddits, automated HN content, purchased stars/upvotes.
Success metrics — first 2 weeks after publication
- At least two reproducible independent consumer installations/migrations (record genuine success and failure).
- Searchable public installation/migration docs, all internal HTML links passing, no contradiction between PyPI and source.
- Track organic package downloads as context only (may include mirrors/CI); focus on actual GitHub issues, questions, reproduced bugs, upgrade stories and pull requests.
- Triage every externally reported correctness/privacy regression promptly. Review channel clicks/downloads as aggregate indicators only where available.
- Record which channels yielded useful conversations; don't equate stars with adoption.
Suggested sequence
Preflight: merge #87 once link checker passes; optionally host the site with explicitly approved deployment. Resolve #85 O(N), freeze a narrow 0.6.0 scope, produce an independently tested demo and security release evidence.
Launch: manually publish approved 0.6.0; announce on GitHub/PyPI first, then submit to PyCoder's Weekly and one community at a time where permitted. Respond thoughtfully, rather than trying to post everywhere simultaneously.
Follow-up: 7–14 days later summarize verified consumer feedback, bug triage and what changed in the next backlog. No automated monitoring or scheduled outreach is set up by this issue.
Related: #48 (public docs hosting), #53 (identity safety), #54 (bounded memory), #50 (events), #86 (0.6 roadmap).
Activity
docs(site): publish navigable 0.5.0 onboarding and verified links (#87)
docs(pages): manual GitHub Pages hosting, API reference and alternati…
docs(migration): runnable published before-and-after adoption demo (#90)
agustin18 commentedon Nov 21, 2026
Competitive positioning and 0.6.0 promotion preflight — 2026-11-21
Status, not an announcement: Published fastapi-cache-stable 0.5.0 remains the only advertised artifact. #85 at PR HEAD after the read-only-
max_entriesfix is draft and unmerged; its exact new CI and independent counteraudit remain gates. #50 is design-only; #53 is an unresolved security-context classification gate. No two external consumers yet (#91: 0/2). Public Pages URL is not verified (#48).Market comparison (external docs checked 2026-11-21; no claim of independent performance superiority)
fastapi_cacheimports and ordinary key format, with independently verified package migrations/rollback and modern Redis client test profiles; conservative authenticated-response defaults, fixed maintenance defects@cacheergonomics and basic backends; upstream's prior behavior may differ, so not every app is zero-change or can safely restore cached private responsesfastapi-cache2apps minimizing migration/edit risk. Our tested Python 3.8–3.10 functional legacy compatibility and ordinary Redis/key migration bridge may help some existing deployments.Age/HEAD and deeperCache-Controloptions. CacheX supports newer Python (3.14–3.15); we stop at <3.14. CacheX has its own migration-from-fastapi-cache2 guide and proven docs: never claim we are the only migration option. Comparison.fastapi_cacheimports; no requirement for Redis-native DI integrationDepends(), OpenTelemetry, rate limiting, eviction groups and Redis-centric ops; compelling choice for a new Redis-heavy app. Different API and runtime requirements; don't claim it is a drop-in replacement.Truthful differentiator: “Already use
fastapi-cache2? Upgrade to a maintained, tested, lower-friction compatible fork with predictable ordinary keys, clearer privacy defaults, modern Redis client checks and repeatable wheel/sdist migration evidence.” This is a qualified compatibility path, not a guarantee of no changes, universal tenant isolation, Redis Cluster namespace clear, performance wins or zero security advisories.Feature freeze recommendation: Include #85 only after the independent review/CI and intentional docs; defer #50 to 0.7.0 unless a small opt-in privacy-minimizing callback PR independently passes before freeze. #53 requires a written library-owned-vs-app-owned risk disposition (with reproduced negatives), not vague closure. Do not add tags, stale, single-flight, locks or rate limits merely to chase CacheX/Cashews parity.
Adoption execution / measurable gates
Launch order option: complete #85 → choose #50 deferral → #53 assessment → prospective
0.6.0rc1/TestPyPI only with approval → independent consumers against the exact candidate → release gates → 0.6.0 publication → re-run published-demo pins → configure/verify Pages if not already live → coordinated launch. A release candidate may serve as an outreach testing artifact, but the0.6.0final wheel and tag remain blocked until evidence and explicit maintainer sign-off.Reassess competitor versions and community rules immediately before publication; the current market changes rapidly.