Repository navigation
Tags: lopadova/AskMyDocs
Tags
docs(readme): close the roadmap and changelog gap from v8.27 to v8.35 (… …#470) The roadmap table jumped from v8.26.0 straight to v8.32→v8.34, and the changelog's newest entry was v8.30.0. Five versions had shipped without a roadmap row and five without a changelog entry, so the two tables that answer "what is in this product" disagreed with each other and with the code. Backfilled from verifiable sources rather than reconstructed from memory: merge dates come from the merge commits (#397 2026-07-10, #402 2026-08-24, #403/#404 2026-08-06, #424 2026-08-30, #443/#448/#452 2026-08-29, #455/#461 2026-08-30), and the substance from the ADRs that accompanied each cycle plus the CLAUDE.md sections written when the work landed. Where a changelog entry already existed (v8.27, v8.28, v8.30) the roadmap row summarises that entry rather than re-deriving the history. Roadmap gains v8.27.0, v8.28.0, v8.29.0, v8.30.0, v8.31.0 and v8.35.0, so the table now runs unbroken from v8.25 to the present. Changelog gains v8.29.0, v8.31.0, v8.32.0, v8.33.0, v8.34.0 and v8.35.0. v8.27.0 also stops claiming to be "in progress": PR #424 merged on 2026-08-30 and completed it, so the heading was three weeks stale and would have told a prospective consumer the API connector was unfinished. v8.35.0 is this cycle — laravel/ai 0.8→0.11 and laravel-flow 1.1→2.5 landing together, the flow surface closing its R32/R44/R45 gaps, and the empty-tenant fix that came out of review. The entry keeps the parts that are load-bearing for anyone upgrading: that the tenant on converted history was the real risk and why a `default` stamp there would have been undetectable, that four of the v2 breakages fail at boot rather than gradually, and that the first R32 test was theatre because routes register at boot from a flag the test flipped too late. R45 parity verified rather than assumed: every version documented here already has its deep doc-site page — connectors-api, team-management, case-study-email-datasets, system-administration, source-permissions, ingest-provenance, tool-firewall and flow-orchestration all exist. The doc-site was never what fell behind; the README was.
docs(v8.26.0): invite-only SPA registration + native Invitations admi… …n + release notes (#389) * docs(v8.26): document invite-only SPA registration + native admin (README/CLAUDE/doc-site) Cover all work merged since v8.25.0 (PRs #381–#387) accurately in the README: - Add the v8.26.0 Changelog entry and Roadmap row covering the invite-only SPA registration flow (POST /api/auth/register over CodeValidator + RedemptionService, redeem outside a DB txn, force-delete on exhausted-between-checks race, 422 on invite_code, throttle:register 6/min/IP), the native in-app Invitations admin (superseding the v8.22 cross-mount panel, gated by INVITATIONS_ADMIN_ENABLED via the additive features.invitations_admin flag on /api/auth/me), per-mailbox IMAP connection serialization, the connector test-fetch/enable surface, the SQS queue-column widening, and the timezone-aware RAG prompt (KB_PROMPT_TIMEZONE). - Add the SPA sign-up paragraph to the Invitations narrative section (the only feature from #387 that had no README coverage at all). - CLAUDE.md (R9): note RegisterController/RegisterRequest, the register route + rate limiter, lang/{en,it}/register.php, and the native admin in the Invitations reference row. - doc-site (R45): add an "Invite-only sign-up (SPA registration)" section to invitations.mdx for parity. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(v8.26): clarify INVITE_REQUIRED is a package-level flag (Copilot review) INVITE_REQUIRED / invitations.invitation_required is only defined in config/invitations.php and consumed by padosoft/laravel-invitations — no host signup flow reads it, and the host SPA register endpoint is always invite-only. Drop the misleading 'still governs the broader signup paths' claim in docs-site and reword the README env comment accordingly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PreviousNext