Skip to content

roadmap(0.6): bounded InMemory, privacy-safe observability and targeted correctness #86

Open

Description

@agustin18

2026-11-21 post-#85 merge status: #85 MERGED into stable as 190d105915972d436ddbf4ad152ad654a4db392a, after independent GO and exact-head 29/29 CI, 13/13 Redis migration/rollback, CodeQL and installed-security checks. Implementation issue #54 closed as source-complete, NOT published; 0.5.0 remains latest on PyPI and is unbounded. Docs reconciliation PR #93 is draft awaiting docs/CI review. #50 recommended deferred to 0.7.0 by default. Remaining 0.6.0 gates: #53 privacy risk disposition, #91 independent consumer exercises (0/2), #92 exact final artifacts/security/approval, #48 manual Pages environment + public-site verification. Earlier pre-merge updates below are historical.


2026-11-21 latest release prep: #85 immutable-max_entries fix HEAD 098e37cb4530a3d4fd282080e2d0c3251e089f4a is 0 commits behind and full exact-head CI 29/29 + migration 13/13 + CodeQL/security/Redis green (counteraudit report). Still DRAFT, unmerged, independent reviewer GO pending. Separate #92 release gates and #91 external consumers (0/2) block final publication. #50 recommended deferred to 0.7.0 absent a separately audited PR; #53 risk disposition must be completed. 0.5.0 still published.


2026-11-21 release planning checkpoint: The mutable max_entries bug found by independent counteraudit was reproduced on #85 c33aa6f. Draft #85 now has a read-only property and regression tests at latest HEAD 098e37cb4530a3d4fd282080e2d0c3251e089f4a; new HEAD workflows are not yet certified and the fix is NOT merged. Exact-head counteraudit request. Created #92 for the 0.6.0 release candidate → exact-artifact, security, external-consumer and publication gates. Recommended freeze: #85 plus #53 classification, postpone #50 until 0.7.0 unless independently audited in time; nothing has been released or scheduled. Competitive evidence/launch strategy.


2026-11-21 #54 technical preflight: Draft PR #85, HEAD c33aa6f571330299cf5606802e0db811836404b7, is 0 commits behind current stable. All exact-head CI (29/29), migration (13/13), CodeQL, Redis and installed security workflows passed; external counteraudit brief/evidence. Not independently approved; do not merge or include max_entries in shipped-0.5.0 claims. Pages activation and two external consumers remain separately blocked by #48/#91.


2026-11-21 integration checkpoint: #89 MERGED into stable (b118890c): secure, manual-only Pages documentation sources; external Pages environment/URL checks still pending. #90 MERGED into stable (d36a21388f25ed9d9528d4ac8ed832a76b571eed): an isolated published 0.2.2→0.5.0 before/after tutorial; pins remain 0.5.0 until 0.6.0 publication, with explicit checklist to update/validate against the exact new artifacts. This does not count toward either external consumer in #88. Execute and record both independent consumers under #91. #85 is still draft/unmerged pending an independent expiry-heap/invariants audit. Limit 0.6.0 to adoption/confidence, with #50 optional and #53 security gate; no tag/PyPI/public outreach.


2026-11-21 candidate-freeze update: #85 squash-rebased cleanly onto #87 stable and expanded 10k/100k CI to include full-capacity eviction churn and TTL reclaim, with seeded 40,000-operation invariants fuzz. Correct clear(namespace) bound to O(N + k log N). Keep it draft until exact HEAD CI + independent review. #89 proposes optional manual GitHub Pages deployment, curated 0.5.0 API reference and honest competitor fit map; no automatic website activation or PyPI release. 0.6.0 competitive promise: preserve fastapi_cache migration contract, verifiable modern Redis and privacy semantics; #54 and optional #50 are supporting evidence, not pressure to copy CacheX tags, locks, coalescing or stale serving. #88 remains the first coordinated promotion plan (0.5.0 already published).


Adoption decision: #88 plans 0.6.0 as the first coordinated public launch after publication (0.5.0 is already released). No outreach, hosted docs deployment or publication has been authorized. Release readiness includes a public onboarding demo and real external consumer feedback, not just green CI. #85 must pass 10k/100k performance gating and independent expiry-heap review; #87 must pass every internal built-site link check.\n\n## Status: planning only (not published)

Published: fastapi-cache-stable 0.5.0. Exact release evidence. This issue plans 0.6.0; prior #70 tracks the completed 0.5.0 release. No promised date, tag or release authorization.

Proposed core

  • P0 if reproducible: #53 residual hidden context/tenant/custom auth/proxy trust/cardinality. Prioritize package-owned data disclosure over optional features.
  • P1 candidate: #54, opt-in per-instance bounded InMemory LRU, expired-first reclaim, concurrency/TTL/clear tests. Draft PR #85 is unmerged: max_entries is NOT in published 0.5.0.
  • P1 candidate: #50, opt-in privacy-safe typed events; no raw keys or credentials; measure disabled-by-default overhead.
  • Research: local single-flight with leader failure, cancellation, timeouts and worker boundaries. No distributed-lock commitment.
  • Design first, nonblocking: #49, safe opt-in argument exclusion; never omit response-defining identity, tenant or locale.

Separate maintenance / adoption

  • #45 DynamoDB experimental TTL/close correctness; real-service verification.
  • #55 FIPS/MD5 portability without changing default key digests.
  • #51 Python 3.14 exploration only; do not widen Requires-Python without full CI.
  • #48 searchable docs + landing/install/migration paths + static-site CI; publishing a hosted docs site is separate.

Acceptance and freeze

  • Preserve legacy default-key goldens, default auth/private bypass, Python 3.8–3.10 functional migration and server-side Python 3.11–3.13 security targets unless a separate compatibility decision is approved.
  • Every public feature in its own reviewed PR, with privacy-negative tests, concurrency/failure tests, supported CI and independently installed wheel/sdist checks.
  • No mandatory telemetry or locking dependency, new unproven Cluster support, tags, rate limiting, circuit breaking or second public API in this bounded cycle.
  • Before publication: exact-final-SHA migration/consumer, modern installed-security, authenticated Dependabot delta, issue-scoped risk decision, Towncrier changelog and separate manual tag/PyPI approval. 0.5.0 signoffs are historical and cannot authorize 0.6.0.

See ROADMAP.md and #70 historical.

Activity

  1. agustin18 commented on Nov 21, 2026

    @agustin18
    OwnerAuthor

    0.6.0 adoption-track update (2026-11-21; no release authorization): Draft PR #90 adds a one-command, cross-platform, published-vs-published fastapi-cache2==0.2.2 → fastapi-cache-stable==0.5.0 comparison of an unchanged FastAPI app, plus Python 3.11/3.12 CI and privacy-negative comparator tests. It verifies anonymous MISS/HIT, ETag/304, and intentionally changed auth-cache behavior using fictional identities and isolated InMemory instances. An initial CI run confirmed both published-package probes; the final HEAD still requires fresh CI review. This is an in-repo onboarding demo, not either of the two independent external consumers and not evidence for arbitrary Redis rollback.

    Draft #89 now scopes Pages/OIDC credentials to deploy-only, blocks non-stable jobs, and documents the required external github-pages environment branch protection. It remains manual-only, unmerged and not publicly hosted; its final checks and external setting remain separate approval gates.

    Keep sequencing: independent review #85 → review/merge #89 and manually verify published docs → review/merge #90 demo → #53 security decision, optional #50 freeze → two genuine external consumers + exact candidate migration/security evidence → separately approved 0.6.0 publication/promotion. 0.5.0 remains the latest published version.

  2. agustin18 commented on Nov 21, 2026

    @agustin18
    OwnerAuthor

    Status after approved implementation merge, 2026-11-21: #85 merged into stable at 190d105915972d436ddbf4ad152ad654a4db392a (source-only, 0.5.0 remains latest PyPI). #54 closed as source-completed. #93 documentation reconciliation all checks green (CI 29/29, docs 15 pages / 588 links) but draft pending review. #50 remains deferred to 0.7.0 by default, #53 security risk classification open, #91 external consumers 0/2. 0.6.0 release still NO-GO; #92 exact artifact/security/release gates are separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions