A readable, per-version log of what changed in Suprnova. Each version
section is that version's release record. A version is released when its
version commit and matching v<version> tag are pushed atomically. Newest first.
4.6.2 - 2026-10-23
Added
HttpEmbedderreports the usage its provider sends.Embeddergainsembed_documents_meteredandembed_query_metered, which return the vectors with the provider's ownusage(prompt_tokens,total_tokens) as aMetered<T>; the HTTP provider reads it from the OpenAI-compatible response and sums it across batches, and every other provider reportsNone, so an application that pays per token settles the bill from the provider's count instead of an estimate (#212).HttpEmbedderruns over an application-owned transport.HttpEmbedder::with_transporttakes anEmbeddingTransport: the application sends eachTransportRequest(the pinned endpoint, headers, JSON body, timeout and response cap) through its own HTTP client, credential resolver and admission rules and returns aTransportResponsewith the status, headers and body. The embedding protocol, retries,Retry-After, parsing and vector validation stay in the framework, which also refuses a body over the cap whatever the transport did (#213).LazyEmbedderregisters a shipped profile and loads the model on first use.SearchRegistry::register_embeddercan take aLazyEmbedderbuilt from a shippedModelProfileand a loader; the service starts and tests run without downloading weights. The generation coordinator calls the newEmbedder::resolve_profilebefore it pins a generation, so the generation still records the loaded model's revision, and a loaded model whose id or dimensions differ from the shipped profile is refused by name (#214).- A search generation an interrupted build left behind can be reclaimed.
generations::reclaim_generation(index, generation)andsearch:reclaimrelease the creation lease of acreatinggeneration so the next create call resumes at once instead of waiting the 60-second lease out, publish abuildinggeneration that was never switched to, and report one that is already current. The caller vouches for exclusive ownership, such as its own migration lock;SearchEngine::release_creation_leaseis the driver hook, a no-op for drivers without leases (#215). - A Cloudflare CDN driver for static publication.
CloudflareDriver(featurecdn-cloudflare, on by default and free of new dependencies) works the way an R2 bucket with a custom domain already does: the bucket is the publication disk throughS3Configwith the R2 endpoint, the custom domain serves it, and nothing runs at the edge. The driver owns a few rules on the zone, created on the first switch and corrected on every later one: two URL rewrites that serve/aboutand/about/from the mirroredabout/index.html, a response header rule that carries the published headers, and a cache rule that caches a response only when its ownCache-Controlallows a shared cache, as the published objects' does. It purges by URL in batches of 100 or by prefix, and removes its rules on a first-publication rollback.CloudflareDriver::for_origincovers a hostname that mixes dynamic pages: the proxied application serves the published objects itself and the driver keeps the cache rule and the purges. R2 charges no egress. - An application's own 5xx page is sent as built. With debug off, the
framework answered every browser 5xx with its minimal status-only view,
which also replaced a 503 page the application built on purpose, with its
recovery link and
Content-Security-Policy.HttpResponse::error_view()marks such a response as the application's own error view, and the production view leaves it alone, body and headers. Unmarked 5xx responses keep the minimal view; with debug on the development error page still replaces a marked response that carries an error report (#217).
4.6.1 - 2026-10-23
Fixed
- A Live action's framework frames fit their stack budget again in a debug
build. The static publication lookup that 4.6.0 added to every
GETrequest built its 65 KB future in the request's own frame, so the frames below a Live action grew past the 1 MiB budget that leaves the action room on Tokio's default 2 MiB stack, and a deep action in a debug build could overflow it. The lookup now builds in a frame of its own that returns first. - A fresh scaffold passes its own page budget test and
cargo fmt --check. The React, Vue and Svelte kits'tests/page_budget.rsauditedroutes::register()alone, so the Live script every page loads from/__live/assetsreturned 404 and the test failed on a new application. It now audits the routercmd/main.rsserves, and the notes topic's gate rule moved frombootstrap::registerintolive::authorize()so both can call it. The kits also wrote the Live topic setup, the asset share and the page budget test on lines rustfmt rewrites; the templates now carry rustfmt's layout, and the test's layout no longer depends on the application name. - The page budget audit's URL mode counts the bytes that cross the wire.
budget:audit <url>andPageBudget::audit_urlasked for uncompressed responses and counted decoded bytes as transfer, while a HAR capture of the same visit counted the compressed bytes, so the two modes disagreed on a page that serves gzip. A URL audit now asks for gzip, counts the compressed bytes for the transfer, asset and font rules, and reads the decoded body for the rest. This fix landed after thev4.6.1tag.
4.6.0 - 2026-10-22
Added
-
Lossless PNG recompression.
Image::recompress_png(PngEffort)runs oxipng over a PNG after the pipeline's pixel operations, and the synchronoussuprnova::recompress_pnghelper does the same on PNG bytes.PngEffort::Fastis oxipng's default level;PngEffort::Maximumis level 6 with Zopfli. Pixels, transparency, indexed palettes, the ICC profile and the colour chunks are kept; text, time and location metadata are removed; the output is never larger than the input. Themediafeature carries the dependency. -
Inertia pages in RenderCache. A page declares its cache shape on the
InertiaPropsstruct:#[inertia(cacheable)]on the struct, and#[inertia(public)]or#[inertia(per_request)]on every field (a field without a marker, an unknown field name or the marker on a non-props type fails to compile).Inertia::cache_page::<Props>(route, component, public_shared, per_request_shared)registers the page at boot. RenderCache stores the public shell and stitches the per-request props in after the route guards run; the assembled response isprivate, no-store. Representations are keyed onX-Inertia, the partial set, the asset version and the other protocol headers, which the response lists inVary; a stale asset version answers 409 before any cached bytes leave.suprnova generate-typeswrites the declarations intoinertia-props.tsasinertiaPropCache(manual/render-cache.md,manual/frontend-typescript-types.md). -
A page budget audit.
TestClient::audit_page(url, &PageBudget)renders a page through the in-process request path, follows the assets the document references (scripts, stylesheets and their imports, images and source sets, fonts, icons, media, inline styles, the web app manifest) and returns every failed rule with the asset, the rule, the measured value and the allowed value. The rules cover total transfer, per-asset size, raster format against size (WebP or AVIF with a fallback above the threshold; a PNG within a margin of its oxipng fast-preset size), the one-year immutable policy on fingerprinted assets, no cookie on or for a static asset, no redirect on the first request, a font budget and the third-party hosts the page reaches. Thebudget:audit <url | file.har>console command applies the same rules to a live URL or a HAR capture. Every budget is configurable onPageBudgetand, for the command, throughPAGE_BUDGET_*environment variables (manual/page-budget.md). All three modes measure the application's own resources and list every third-party host, which the allowed-host rule governs, so a HAR capture and the in-process audit of one page agree. The React, Vue, Svelte and Live starter kits shiptests/page_budget.rsover their public pages; the dogfood application runs the same audit. -
Static publication of public Inertia pages. A route declared with
Router::public_page::<Props>(or a public group plusInertia::public_page::<Props>) renders without a session, CSRF token or nonce, and the application publishes its HTML and JSON objects, its fingerprinted assets and its transcoded images to a storage disk the CDN serves. Publication runs as an application boot task after the listener is bound, so the health check never waits for it. Every page references its assets by versioned key and the manifest write is the only switch, so the previous publication stays live until the new one is complete; a storage lease and a conditional manifest write keep two publishers from racing, and graceful shutdown waits for a delivery in progress. Pages regenerate by dependency tag after a committed transaction or job, delivered across processes through the boundBroadcastHub, and on a revalidate interval. TheCdnDrivertrait ships a CloudFront driver (origin switch, invalidation, a viewer-response function that restores the recorded headers); without a driver the origin serves the published objects from the manifest and mirrors them to stable bucket keys after the switch. Public pages get a hash-basedContent-Security-Policywith'unsafe-inline'and nonces removed from every script directive; private pages keep their nonces, and the origin sendsStrict-Transport-Securityonly on HTTPS it can trust. Images are published as WebP at quality 85 or higher, AVIF when ImageMagick is configured, with the metadata-stripped original as the fallback, and kept PNGs go throughrecompress_pngat the maximum preset. Same-origin absolute image URLs and inline rasterdata:images go through the same preparation and are published as objects; a page whose own CSS (astyleattribute or a<style>element) carries a raster image refuses publication, naming the route, and the origin keeps serving it. Third-party images and linked stylesheets are published unchanged.static:publish,static:statusandstatic:pruneare the console commands; prune keeps the live publication and retired versions inside their grace period. The React, Vue and Svelte kits ship a client that fetches the published JSON for public navigations and sends everything else to the origin (manual/static-publication.md). -
Live bindings for Inertia pages.
#[inertia(live(topic = "notes", only = ["stats"]))]on anInertiaPropsstruct binds a Live topic to a list of its props, checked at compile time against the struct and carried into the generated TypeScript. A bound page renders throughInertiaResponse::live::<Props>("Dashboard"), naming each topic family instance with.scope(family, key)and loading its data in.load(...); the response reads the topic cursors before the loader runs and carries them under the reservedliveBindingspage key. Topics are the Live registry's own:LiveRegistry::builder().topic(name)and.public_topic(name)register them,.topic_family(name)gives per-key instances such asnotes.42under onelive:topic.{name}ability (.load_with(...)takes the response builder for deferred and optional props), and every binding goes through Live's subscription log, authorization and transports; a private topic without an authorizer refuses to boot, and a binding the viewer may not subscribe to is omitted from the page instead of leaking its cursor. A change registered withLiveTopics::changedsignals after the commit of its transaction and never after a rollback, coalesced to one signal per topic per request or job and excluding the sender's own page;on_model_scopedpublishes a model's saves and deletes to the instance it maps to. A signal carries only the topic, its cursor and generation, and the affected prop names. The configuredBroadcastHubowns each topic's cursor and its rate (LIVE_TOPIC_SIGNAL_INTERVAL_MS, default 100 ms); with the Redis Streams hub a signal reaches pages on every node, without a hub it reaches the publishing process only; an instance with no member and no activity forLIVE_TOPIC_INSTANCE_RETENTION_SECS(default one day) retires and comes back with a new generation at cursor 0, which the client treats as a reset of its bound props. The React, Vue and Svelte kits ship one client core with an adapter each: a signal older than the render is dropped, a burst reloads once with the union of its props, a failed reload retries with bounded backoff, and polling stays as the fallback. The kit dashboards bindstatsto the per-usernotesfamily (manual/live.md,manual/frontend-pages.md). -
Event sourcing.
#[suprnova::domain_event(name, version)]declares a fact with a stable stored name and schema version,#[suprnova::aggregate]plus theAggregateRoottrait rebuild an aggregate from its history, andAggregate::record(..).awaitthenAggregate::persist().awaitappends facts in their own transaction with an optimistic version check, so two writers never record the same aggregate version (a stale version is a 409 conflict).applyreceives aFactview that is identical when recording and when rebuilding, so a snapshot always equals a full rebuild.Projectorhandlers keep read models andReactorhandlers run side effects once; aQueuedProjectorruns on the queue worker and never reads a synchronous projection. Projectors checkpoint by stored event id andEventReplayrebuilds them from the start in event order, synchronous handlers before queued ones per page, while reactors stay silent. Snapshots shorten rebuilds. Three tables (stored_events,snapshots,projector_checkpoints) ship as a framework migration for SQLite, PostgreSQL and MySQL/MariaDB; rolling it back drops the history. Two domain events with one stored name refuse to boot. The console commands areevent-sourcing:replay,event-sourcing:eventsandevent-sourcing:snapshot. A projector that changes a Live-bound topic signals once after the transaction commits, never on rollback and never during replay. The dogfood app shows a shared tally on a Live page (manual/event-sourcing.md). -
DB_OUTCOME_SETTLE_TIMEOUT(DatabaseConfig::outcome_settle_timeout, default 30 s) bounds how long a caller whosepersistwas cancelled during the commit waits, on its next call, for the transaction's real outcome before reporting it as unknown;Aggregate::is_settled()says whether that wait is pending. It never cancels or bounds a transaction, query or commit.
Changed
-
The default lossy encode quality is 85, not 70. JPEG and lossy WebP encoded without an explicit
qualitycall now use 85, whichDEFAULT_IMAGE_QUALITYnames. Quality below 85 blurs images. -
Inertia protocol middleware runs before RenderCache whatever order the application registered them in, so an asset mismatch is answered before a stored page could be replayed. A cacheable Inertia route with an opaque share hook or provider fails boot with the route name; declare the shared props by name instead. Middleware boxed through the public
into_boxedkeeps its type identity, so ordering and boot checks see it. -
Static files get a cache policy by file name.
StaticFilesserves a fingerprinted file (Vite'sname-<hash>convention, confirmed by the build manifest when one is configured, so an all-lowercase hash counts;fingerprint(pattern)changes the convention for other files) withpublic, max-age=31536000, immutable, and every other file withpublic, max-age=3600unlesscache_control(...)sets another value. Before,cache_controlapplied to every file and nothing was sent when it was unset. A static file response no longer sets the session or XSRF cookie when the request left the session untouched; a request that changed the session (a remember-me rotation, a regeneration) still gets its cookies. -
cdn-cloudfrontis a default feature. It reuses the AWS signing stack the S3 disk and the SQS queue driver already carry and addsquick-xmlfor the distribution configuration; turn it off withdefault-features = false. -
LiveStreams::refreshfollows the shared topic rules for cursor, fanout, scope, socket exclusion and rate, andLiveStreamErrorKind::RuntimeUnavailablealso covers an unavailable configured publisher.
Fixed
-
The MariaDB vector driver reads a quoted index distance. MariaDB 12.3.3 renders the vector index option as
`DISTANCE`='cosine'inSHOW CREATE TABLE, where 12.3.1 renderedDISTANCE=cosine. The driver kept the quotes, saw a distance mismatch and refused everysimilarcall; it now strips them (#216). -
A savepoint rollback discards the callbacks of the work it rolls back. Nested transactions and named savepoints in
DB::transactionnow record their after-commit and rollback callbacks under one lock with the savepoint they belong to, and each savepoint statement and its bookkeeping complete together even when the caller is cancelled. Before, a nested transaction rolled back to an enclosing savepoint could still run its after-commit callbacks when the outer transaction committed. A panicking callback no longer stops the callbacks after it. -
The built-in driver honours the JPEG quality setting. The OxideAV registry encoder ignored the quality option and wrote every JPEG at 75. The driver now calls the JPEG encoder directly with the pipeline's quality.
-
Two tools with one name in different crates now fail the build at link time. Every
#[tool]emits one marker symbol,__suprnova_tool_followed by the tool's name, so the linker reports a duplicate symbol that names the tool when two crates declare the same name. Before, such a duplicate was only refused when the application booted; that check stays as a second net. A crate that forbids unsafe code still builds its tools. -
Tool schemas publish integer fields with their bounds and no JSON Schema format.
schemarswrote Rust's integer formats such asuint64andint32, which clients do not know: Claude Code loggedunknown format "uint64" ignoredfor every such field, and strict clients reject the schema. The bounds carry the same information. The WebMCP browser schemas and thetool-schemas.tsfile thatsuprnova generate-typeswrites follow the same rule.
4.5.1 - 2026-10-21
Fixed
- The locked dependency set no longer carries the webpki advisories
RUSTSEC-2026-0381, 0382 and 0383.
rustls-webpki0.103.16,webpki-roots1.0.10 andwebpki-root-certs1.0.10 replace versions whose bundled roots trusted distrusted emSign intermediates. Binaries built from the tag with--locked, the CLI among them, get the fixed versions.
4.5.0 - 2026-10-21
Changed
- Three public enums have new variants.
RevocationgainsDocumentRelationsBefore,RegistrationOutcomegainsUnavailableandMetadataErrorKindgainsTooManyBrowserTools. Amatchover one of them with no wildcard arm no longer compiles. (#174, #167, #166) - Database search vector delivery now uses retryable claims. Concurrent delivery reports an in-flight error, and a stalled vector call times out after 45 seconds. (#202)
- Search touches now report an error when a declared relation key is missing or cannot be read from the model. (#203)
- Eloquent counter updates now use the saved row to check search eligibility and invalidate cached pages. (#198)
- New starter kits offer more search results only when another accessible page is available. (#196)
- Successful search requests now bootstrap session and CSRF cookies for new clients. Reuse them when reporting search clicks. (#195)
- Event retries now resolve their original provenance before checking the target's current existence or access scope. (#192)
- Newly generated starter explanations retain every contributing history event. Regenerate existing recommendations to refresh their stored provenance. (#193)
- Starter recommendation reads load ranked candidates in bounded pages and load similarity histories only for selected peers and the viewer. Custom search engines now need key lookups for starter reads, as they do for graph reads. (#194)
- Quoted phrases now constrain semantic and hybrid searches using each engine's lexical phrase matching rules. (#191)
- Indexing and semantic queries now require the provider's model id and
revision to match the generation. Rebuild with
search:reindexafter changing models. (#187) - Worker boot now constructs configured search providers before validating searchable indexes. (#188)
- Configured search providers are now available inside application bootstrap hooks for server, worker and console processes. (#199)
- Qdrant now supports retained flush fences and index deletion through the search maintenance commands. Flush fences use the configured tombstone lifetime. (#189)
- Qdrant generation deletion can now resume from the dropping state while ordinary writes continue to reject that state. (#190)
- Qdrant hash lookups now retain the source version when skipping unchanged documents, preserving stale-write protection. (#186)
- Loading a searchable model without timestamps now reads its content and search version together. Locking model reads keep their row locks until the version is loaded; ordinary reads use one SELECT on Postgres, MySQL and SQLite. (#178)
- Saving a searchable model without timestamps now updates the search version carried by that same instance, including saves in an explicit transaction. (#177)
- Graph traversal now replaces earlier paths with stronger later paths, including when the node limit is full. (#176)
RecommendationRunnow exposesranking_digest. Apply the new recommendation migration when upgrading. (#175)- Custom graph stores must handle
DocumentRelationsBefore, which removes stale relation facts while keeping the document node and its engagement edges. (#174) - Serialized recommendation explanations now omit social and shared-engagement edge references. Server-side explanations keep them for verification. (#173)
- On MySQL and MariaDB, an email address now matches an account only when it
equals the stored address after trimming and lowercasing. Accent variants
and other collation folds, such as
ssforß, no longer match at sign-in, password reset, email verification, passkeys or OAuth linking; Postgres and SQLite already compared exactly. A user who typed an unaccented form of an accented address types it exactly after upgrading. (#167) UserProvidergainedrehash_password_for_sign_in(user, credentials, recorded_epoch), the rehash the session guard'sattemptcalls. It checks the stored epoch and the verified hash, writes atomically and returns the snapshot it wrote. The default callsrehash_password_if_requiredonly for a user without a credential epoch, so a custom provider that upgrades hashes on sign-in implements the new method;onceandlogout_other_devicesstill call the old one. The built-in Eloquent and database providers implement it. (#168)
Fixed
- Database search vector updates and deletions now release their SQL connection before calling the vector store, avoiding deadlocks on shared pools. (#202)
- Search touches now find parent keys even when a child hides or renames them in JSON output. (#203)
- Retiring a database search generation now removes list tables for attributes that have since been removed from the index definition. (#201)
- Database search now detects MySQL and MariaDB separately for each named connection, so generation tables use the correct collation. (#200)
- Incrementing or decrementing a counter now adds or removes search results when the new value crosses a model's indexing threshold. (#198)
- Starter kit notes search now stops offering more results at the accessible hit cap, even when more notes match the query. (#196)
- A first JSON search without a cookie now returns an impression that a later click from the same client can validate. (#195)
- Retrying a recorded recommendation event now succeeds after its target is deleted or its access scope changes. (#192)
- Starter explanations now include peers' shared-target events and all repeated positive events, so verification detects removed contributors. (#193)
- Reading a short starter recommendation list no longer loads the whole visible catalog, and still fills the list after filtering inaccessible targets. (#194)
- Semantic and hybrid searches now exclude documents missing required quoted phrases and refill filtered candidates to preserve result depth. (#191)
- Replacing an embedding provider with another model of the same dimensions now reports a rebuild error instead of silently mixing incompatible vectors. (#187)
- Workers with searchable models now start with an environment-selected HTTP or fastembed provider. (#188)
- Fresh starter kits can create the notes search generation with the configured provider during bootstrap. Initialization failures now name likely causes. (#199)
- Qdrant flushes now block delayed writes, including keys absent at the start, and deleting an index removes its collections and generation metadata. (#189)
- Pruning a retired Qdrant generation now removes its collection and metadata instead of failing after deletion starts. (#190)
- Unchanged Qdrant documents now keep their latest version, so delayed older removals cannot delete them. (#186)
- A concurrent save can no longer make a loaded search document carry a newer version than the row content it contains. (#178)
- A borrowed save no longer leaves a searchable model reporting its previous search version after the database has saved a new revision. (#177)
- Graph recommendations now use a stronger indirect route even when a weaker direct route reached the item first, and explain the route used. (#176)
- Recommendations created before an upgrade now obey the current peer minimum, and changing ranking settings refreshes unchanged users on the next full run. (#175)
- Editing a document now keeps its recommendation engagement signals while rebuilding declared relations, including when a document job is retried. (#174)
- Recommendation explanations no longer reveal which followed accounts engaged through edge keys that a client can recompute. (#173)
- Cancelling a text stream from a response callback now leaves its status clear, and callbacks cannot overwrite a replacement request's state. (#184)
- Event streams now stay open after a connection error so the browser can reconnect and continue receiving messages. (#183)
- Stream readers mounted together with the same id now share their text and callbacks in all three Inertia kits. (#182)
- Stream requests now use the fresh CSRF cookie after sign-in, so Inertia navigation no longer leaves them sending a stale token. (#181)
- Adding a source to a Content Security Policy now changes only the policy containing its directive, keeping other policies in the header unchanged. (#180)
- Live now announces interrupted actions to screen readers in the shipped browser bundles. (#172)
- A sign-up whose address collides with an existing account only under the database's looser comparison answers the same generic response as a registered address and creates nothing, instead of a conflict error. (#167)
- Schema watchers now report new form request refusals even when the generated file stays unchanged, without repeating unchanged refusals on every edit. (#171)
- Postgres schema dumps now remove entire multiline extension comments even when they contain semicolons, preventing invalid snapshots. (#170)
- Live components now reject more than 64 browser tools on the server, preventing oversized tool metadata from disabling ordinary clicks. (#166)
- Headless Live tools now report when their growing state no longer fits a follow-up request, so agents can restart instead of receiving an unusable handle. (#165)
- Concurrent fresh database migrations now recover when another migration creates the authorization server or agent auth tables first on Postgres. (#164)
- Concurrent agent assertions now share one provider key-set fetch, preventing unknown keys from triggering duplicate requests to the provider. (#163)
- Live tool actions now accept optional dates and date-times, and date-times in lists and maps, without failing before the action runs. (#169)
- Password resets now cancel password sign-ins already in progress, so an old password cannot create a new session after the reset. (#168)
- Agent tools now refuse guards that use a different user provider from the caller's default guard, preventing matching ids from signing in as another person. (#160)
- Built-in approval and agent claim forms now refuse agent tool submissions, even when the tool has your signed-in session and a valid form token. (#161)
- On MySQL and MariaDB, accent-insensitive email comparisons could let a different mailbox receive a magic link for another account. Account lookups now require byte equality after trimming and lowercasing, and magic links go to the stored account address. Conflicting registrations return the same generic response without issuing a token. (#167)
- On MySQL and MariaDB, an email change that differed only by accents could still receive a verification stamp for the old address. Verification now checks the exact address atomically, so that change refuses the stamp. (#162)
4.4.0 - 2026-10-20
Added
-
Handlers become agent tools with
#[tool]. A routed#[handler]marked#[tool]is a tool agents can call.#[tool_input]derives the input's JSON Schema (draft 2020-12) from the struct and itsserdeandvalidatorattributes, so an agent is told what the server enforces.tool_scopes!declares scopes, and aToolCallerargument tells the handler and its policies who is calling: apublicguest, auseror anagentaccount. A tool call runs the route's middleware, validation, policies and rate limits, under per-caller and per-address budgets. An invalid or duplicate name, a missing description or an undeclared scope fails the build. See Agents. -
An MCP endpoint serves the application's tools.
Router::agents(AgentsConfig::new())servesPOST /mcpover MCP's Streamable HTTP transport, revision 2026-07-28, and toinitialize-based clients of revisions 2025-06-18 and 2025-11-25, without sessions. It serves protected resource and authorization server metadata at the well-known locations under the application's root, lists every tool to a client without a token and only the tools a token may call to one with a token, runspublictools without a token, answers 401 and 403 with the scopes a call needs, so a client's first call of a tool that needs a token sends it to sign in, refuses a foreignOrigin, and bounds the body, the answer and the run time. Structured results follow the session's revision: on 2026-07-28 a tool's output schema and result pass through as declared, and on the two older revisions a non-object output schema is left out oftools/listand a non-object result comes back as text alone. -
Users approve MCP clients through a built-in OAuth server.
AgentsConfig::oauth_server(OAuthServer::new())mounts the new Magnetar authorization server plugin: OAuth 2.1 with the authorization code grant and PKCES256, clients identified by a client ID metadata document or dynamic registration, exact redirect URIs, tokens bound to the MCP endpoint and the approved scopes, refresh tokens rotated on every use, revocation, and tokens stored only as digests. Default approval and connected-agents pages ship, andConnectedAgentslists and revokes a user's grants. Its issuer isAPP_URL. -
Tokens from an outside identity provider sign users in.
OutsideIssuer, added withAgentsConfig::resolver, accepts the user tokens a provider you name signs, checked against its published keys for issuer, audience, expiry and scope. It finds the user bysub, by an id the issuer assigns (id_claim, such as Microsoft Entra'soid) or by a claim the token marks verified. -
Agents hold accounts of their own under auth.md.
AgentsConfig::agent_auth(AgentAuth::new())serves auth.md v0.6.0 from the new Magnetar agent auth plugin: anonymous,service_authand ID-JAG registration, the/auth.mddocument, a claim page with a six-digit code, revocation by token and by Security Event Token, registration rate limits and audit events. A claim dispatchesAgentClaimed, delivered at least once with a stableevent_id. Theagents:key,agents:revoke-allandagents:prunecommands print a signing key, revoke every agent credential and run the maintenance pass. -
Live actions can be agent tools, in the browser and headless.
#[tool]on a Live action offers it to agents, with fields marked#[agent_visible]as the result. The Live runtime registers a mounted component's tools with WebMCP. An action markedheadlessis also callable over MCP with no browser, through a sealed state handle bound to the caller; the Gate abilitylive:{component}.mountchecks the mount properties an agent sends, and#[resolve(...)]fills a property from the caller instead. -
Pages offer server tools to agents in the browser.
Router::share_tools,with_toolson a route, a group, an Inertia response or a Live document, andPageTools::addchoose the tools each page registers with WebMCP. A page lists only the tools its viewer may call, a page of public tools stays shared in RenderCache, and the page refreshes its data after a write tool. WithWEBMCP_ORIGIN_TRIAL_TOKENset, every HTML response carries theOrigin-Trialheader. -
The React, Vue and Svelte kits register page and form tools. New projects call
installPageTools(router)and shipusePageTool, for a tool that lives while its component is mounted, anduseFormTool, which makes a form a tool that fills and submits it through Inertia. A destructive form is filled and left for the user to submit.suprnova generate-typeswrites each form request's input schema tofrontend/src/types/tool-schemas.ts. The kits'core.ts,suprnova-webmcpand the Live runtime read a page's tools by the keys they know and ignore the rest, so a later release can add a field without breaking a scaffolded application. A change an older reader must not ignore raises the payload'sv. -
Rust front ends compiled to WebAssembly register WebMCP tools. The new
suprnova-webmcpcrate registers typed page tools, with the input schema the server derives, for as long as their handles live, and calls the application's server tools with the session and the CSRF token. Built for a target without a browser it compiles and answers unsupported. -
Tests call tools as any caller.
TestClient::toolandTestClient::live_toolcall a tool as a page does, andTestClient::mcpcalls the MCP endpoint as a guest, a user with chosen scopes or an agent, claimed or not, without an OAuth or auth.md ceremony.Agents::fakemints a token for a chosen caller, andTestResponse::page_toolsreads the tools a page offers. -
Test requests can come from an address and carry any body.
TestClient::with_peer_addresssends requests as if from that TCP peer, soRequest::ip()and limits keyed by the client address see it.TestRequest::bodysends a body of any content type as it is. -
Applications build their own consent pages on
AgentApprovalsandAgentClaims.AgentApprovals::of(&request)reads the signed-in user's pending authorization as aPendingApprovaland records the decision as anApprovalDecision.AgentClaims::of(&request)reads aPendingClaimand confirms it with the user's code as aClaimConfirmation. Both answer 403 to a tool call, so an agent never approves or claims for the user it acts as. The framework's default pages use them too.ConsentPageHeadersrefuses framing withframe-ancestors 'none', and setsno-storeandno-referrer, on every answer of a consent route, error pages included, and keeps the application's nonce policy. -
url::same_origin_pathchecks a return address, andRedirect::intended_urlreads the intended one.same_origin_pathaccepts only a path that starts with a single/and holds no control byte, so a sign-in page checks areturn_towith it beforeRedirect::set_intended_urlstores it.Redirect::intended_url()returns the addressRedirect::intendedwould follow, without spending it, as Laravel'sgetIntendedUrldoes. -
An application's migrator can create the agents tables and a case-insensitive email index.
suprnova::agents::migrations()creates both plugins' tables, only what is missing. Its rollback leaves them in place, and its documentation gives the statements that drop them.suprnova::auth::migrations::UniqueEmailIgnoringCase::on(table, column)adds a unique index onLOWER(column)on SQLite, PostgreSQL and MySQL 8.0.13 or later. On MariaDB and older MySQL it checks that the column has a unique index of its own and a_cicollation. It refuses a table that already holds addresses that differ only in case, and its index name fits every engine's identifier limit. -
Tests build a router with agent auth without a signing key.
suprnova::testing::install_test_agent_auth_key()gives the test process a generated key when the environment names none. -
#[tool_output]and#[tool_schema]derive schemas through the framework.#[tool_output]marks a tool's output type, any struct or enum, and derivesSerializeandJsonSchemawith noserdeorschemarsdependency of the application's own.#[tool_schema]gives a type nested in a tool's input or output its schema, andsuprnova_webmcp::tool_schemadoes the same for a page tool's input. -
Tools can carry WebMCP's
debugginghint.#[tool(annotations(debugging))]on a server tool or a Live action, thedebuggingoption of the kits'usePageToolanduseFormTool, andPageTool::debuggingmark a tool meant for debugging and developer tooling rather than end users. The MCP endpoint does not send it. -
New projects serve agents.
suprnova newwrites a fresh agent auth signing key into.env, readable by its owner only (mode 0600), and.env.examplenames both variables with no value. Every kit serves the MCP endpoint, the OAuth server and agent auth fromsrc/agents.rs, and its migrator creates both plugins' tables. The Inertia and Live kits' migrator also creates a case-insensitive unique email index, and their sign-in sends a signed-in user who opens a sign-in link on to a same-originreturn_toand keeps the intended address through sign-in and registration. Every kit folds an email address to ASCII lowercase before validating it, and bounds names at 255 characters and addresses at 254. -
The agents maintenance pass prunes the OAuth server's ended rows. The five-minute pass in
serveandagents:prunedelete lapsed pending authorizations and codes, expired tokens, and grants revoked longer ago than the retention, whenever the router mounts the OAuth server, with agent auth or without. A live grant or token is never pruned.agents:pruneneeds agent auth only for--retry-failed. -
The Inertia and Live kits ship their own approval, claim and connected-agents pages. The React, Vue and Svelte kits render
Agents/Approve,Agents/ClaimandAgents/Connectedat/oauth/approve,/agent/claimand/connected-agentson the consent facade, and an approval leaves for the client by a location visit. The Live kit serves the same three pages as plain server-rendered documents with native forms, and an approval leaves through a short page whose meta refresh and link go to the client, whichform-action 'self'allows. Every route runsConsentPageHeaders, no consent page offers a tool, and text a client, an agent or the user chose sits in<bdi>. See Starter Kits. -
The API kit serves agents, with a sign-in for consent only. A new API project serves the MCP endpoint and both plugins with the framework's default pages. A browser signs in at
/loginonly to approve a client or claim an agent: the session runs on the consent pages alone, ends after 15 minutes idle, keeps its cookie for the browser session, and ends atPOST /logout.GET /api/connected-agentslists the user's connected clients and agents, andDELETE /api/connected-agents/clients/{grant}and/agents/{registration}revoke one. Registration mails a link that verifies the address, which a claim needs, andPOST /api/email/verification-notificationmails a new one. -
Auth::email_verification()verifies an address for its signed-in owner.issuemints a single-use link token for the signed-in user, andissue_forone for an account the request just registered. The application mails the link.verifyverifies the address only for the user signed in where the link opens, only while the account still holds the address the link was mailed to, and answersVerified,AlreadyVerified,OtherAccount,AddressChanged,Expired,UnknownorSignIn. Anyone can register another person's address with a password of their own, so a link that verified whoever opened it would verify that account. Verifying changes no credential and starts no session. -
Consent pages refuse a form tool's submission. A kit's form tool sends the form it submits with the
Suprnova-Form-Toolheader, whichsuprnova::agents::FORM_TOOL_HEADERnames.AgentApprovals::ofandAgentClaims::ofrefuse it with 403, as they refuse a tool call, so a form tool on an approval or claim page cannot approve or claim. -
New projects ship two notes tools. The Inertia and Live kits serve
search_notesatGET /notes/searchandcreate_noteatPOST /notes/tools, under thenotes:readandnotes:writescopes, each acting on the caller's own notes. The notes page offers both to an agent in the browser. -
The Live input takes
maxlength. The component library's input sets the attribute only when a caller passes one. The Live kit's account forms bound the name at 255 characters and the address at 254. -
#[tool]warns over WebMCP's budgets. The build warns when a tool's name passes 30 characters, when its description passes 500, and when an input field has no description, and boot logs the same. The warnings never refuse a tool. A tool that keeps a long name on purpose setsbudget = ignorein its marking, which quiets the build warning for that tool alone; boot still logs its budget warnings. -
Live tools describe their arguments.
arguments(amount = "How much to add.")on a Live tool marking gives each action parameter the description an agent reads; an argument name the action does not have fails the build. A mount parameter takes a doc comment. -
The Inertia frontends pin
webmcp-types. The React, Vue and Svelte kits' browser helpers use the community'swebmcp-types0.1.10 definitions for the model context, tool definitions and tool results.
Changed
- Tool names are identifiers. A tool name is 1 to 64 ASCII letters,
digits and underscores, so every model's tool calling accepts it; a name
with a dot or a hyphen fails the build. The shipped tools are renamed verb
first:
posts.createiscreate_post,notes.searchissearch_notes. A browser instance of a Live tool joins the tool name and the instance key with a hyphen, and the whole fits in 64 characters: a root mount that does not fit fails at declaration, and the Live checker reports an island that does not. An application with dotted tool names renames them. MagnetarLifecycleEventandLifecycleEventcarry anattributesmap. Agent auth events record the registration, the client address and the fields auth.md names for each kind in it; it is empty for the other kinds. Code that builds either struct field by field, or destructures it without.., no longer compiles.- Three public enums have new variants.
LifecycleEventKindgains the nine agent auth audit kinds, fromAgentRegistrationCreatedtoAgentRegistrationRevoked.CryptPurposegainsLiveAgentHandleandHandlerArgKindgainsContext. Amatchover one of them without a wildcard arm no longer compiles. - The
agentsfeature is on by default. An application that keeps the framework's default features compiles the agent tools, the OAuth server and agent auth, and Magnetar'smigratecreates their eight tables when it next runs. Nothing is served until the router callsRouter::agents. generate-typesandservewritefrontend/src/types/tool-schemas.ts. The file holds the input schema of each form request, or an empty list, beside the Inertia props types. Each run brings it up to date and names each request it cannot describe exactly as the server does.Redirect::intendedfollows only a path, anhttporhttpsURL, or a relative reference. It ignores a stored value with another scheme, such asjavascript:,mailto:orlocalhost:3000/x, and one with surrounding whitespace or a backslash anywhere, and redirects to its fallback instead. A browser trims whitespace and reads\as/, so such a value could leave the application. See Storing the intended URL.- An Inertia error page keeps a
no-storethe replaced response carried. The error page setCache-Control: no-cache, privateon every page it rendered. It now setsno-storewhen the response it replaces saidno-store, so a page that must not be stored stays unstored when it fails. - Magnetar's
auth_tokenstable gains anaddress_digestcolumn. A token that verifies an email address keeps the SHA-256 of the address it was mailed to. Magnetar'smigrateadds the nullable column the first time it runs. - A custom Magnetar engine, store or token binding refuses email
verification until it implements the new methods.
MagnetarPasswordAuthEnginegainsemail_verification_issueandemail_verification_verify,TokenStoregainsissue_boundandinspect, andUserStoregainsmark_email_verified_for.TokenFieldsgainsread_address_digestandwrite_address_digest. Each has a default, so existing code compiles, and the defaults refuse, soAuth::email_verification()fails closed until they are implemented.
Fixed
- Concurrent writes no longer fail on MariaDB 11.8 and later. These
releases turn
innodb_snapshot_isolationon by default, under which a transaction that updates a row another transaction changed after its first read fails with error 1020, "Record has changed since last read", where MySQL waits and works on the latest row. Two overlapping writes to one table failed one of them with a 500, because each advances the RenderCache ledger, and two requests spending one email verification or password reset link at once could fail the losing request with a database error instead of answering that the link was used. Every connection the framework opens to MySQL or MariaDB now runsSET SESSION innodb_snapshot_isolation = OFFonce, when it opens. A server without the variable, MySQL included, refuses it as unknown and the connection opens as before. The statement never fails a connection: any other refusal, as a MySQL-compatible proxy or service may give, is logged once per pool atwarn, and the connection opens with the server's own setting. See MySQL semantics on MariaDB. DB::transaction_with_attemptsretries by the database's error code. It re-runs an attempt the database refused with MySQL or MariaDB error 1213, 1205 or 1020, or Postgres SQLSTATE 40001 or 40P01, and returns any other database error at once, even one whose message mentions a deadlock. It used to match the word "deadlock" in the message, so a lock wait timeout and MariaDB's error 1020 were never retried. An error with no database code is still matched by its message.- A Postgres schema dump loads where an administrator installed an
extension.
schema:dumpcopied the comment an extension sets on itself, such asCOMMENT ON EXTENSION vector. Loading that dump as the application's role failed with "must be owner of extension", because the extension belongs to the role that installed it. The dump now leaves those comments out, andCREATE EXTENSIONsets them again. - Magnetar's tables hold long values on MySQL and MariaDB. Byte
columns were limited to 255 bytes. These hold passkey and OAuth sign-in
steps, two-factor secrets and recovery codes, and saved provider tokens.
So were the session user agent and the passkey credential id, public key
and provider scope columns. A longer value failed to save, so passkey,
two-factor and social sign-in could fail there. Magnetar's
migratewidens the existing columns the first time it runs. It keeps each column's character set and collation, and leaves a column that an index covers alone, with a warning. - Two servers migrating Magnetar's tables at once no longer collide. A table, index, column or marker that another process created first counts as created.
- Registration answers a validation failure with 422.
Auth::password().registeranswered a weak password or an unusable address with 401. It now answers the framework's validation error, with the message under the field. - Email addresses longer than 254 characters never reach the database.
Sign-in with one answers as an unknown address does. Sign-up, the account
import and OAuth email completion refuse one as a validation error. Such
an address is still counted toward lockouts. An account that already
holds one can no longer sign in by email;
migratelogs how many exist, once per database. - Session metadata stays within its columns. A session keeps at most 1,024 characters of the user agent. A lockout records the client address only when it parses as an IP address.
- New projects get every default feature of the framework. A new
project's
Cargo.tomlturns the framework's default features off and lists the ones it keeps. The list lackedsearch-mediaandagents, so a new project had neither media search nor agent tools. It now lists both. - A form request on GET or HEAD reads its query. As Laravel validates the
query of a GET, a form request on a GET or HEAD request without a body
reads its query string as it reads a url-encoded body: it decodes,
validates and names its fields as
request.query_into()does. Such a request was refused with 415. A request with a body still reads the body, and other methods are unchanged. - Precognition and the real request read a query alike. A query value
holding a JSON object reads as that object where a struct or a map belongs,
and stays text everywhere else, in Precognition, a GET form request and
request.query_into(). Precognition decoded the object wherever it stood, so a route could pass Precognition and fail the real submission. - An
OptionLive mount parameter can be left out. Every mount parameter was registered as required, and no codec decodes null, so anOption<T>parameter could never beNone. It is now optional: left out or null, it mounts asNone. - A page's scripts and styles no longer become the previous URL. The
session recorded any successful GET as the previous URL: a script or
stylesheet that
StaticFilesserved, a request a global middleware answered before any route matched, and an AJAX request. Without aReferer,Redirect::back()could then send the user to a.jsfile. As in Laravel, the session now records a GET only when a route answered it, the fallback route included, and skips a request that sendsX-Requested-With: XMLHttpRequest. A file thatStaticFilesserves is never recorded. - Two uses of one email verification link at once no longer answer 500 on MariaDB. MariaDB 11.8 and later end a transaction that writes a row a concurrent one changed, so the second of two concurrent uses of one Magnetar verification token answered 500. The losing use now reads the token as already used, on every engine. A consume the database ends in a deadlock or a serialization conflict runs again, up to three times, and answers a conflict rather than an internal error if every run conflicts.
- Pages keep their styles under the Vite dev server. In development,
SecurityHeadersallowed the dev server inscript-srcandconnect-srconly, so the browser refused the stylesheet link the framework puts in the head, and a page under the balanced preset rendered with no styles. The dev server is now allowed instyle-src,font-srcandimg-srcas well. - A panic the panic hook reports carries its request. A panic raised inside a request or job scope but outside the framework's own catch reached the tracker without the scope's request id, request, route and user, which an error reported in the same scope carries. It now carries them. The hook never waits on a lock the panicking thread may still hold: a field it cannot read at once is left out, and if the request's auth state is locked, the event names no user rather than a wrong one.
- A panic reported while another report resolves its stack is kept. The panic hook gave up the whole event when the symbol resolver was busy, so the one event a reporter exists for could vanish and only a counter said so. The hook now sends the event without frames and says so in its payload; the message, location, request and release all arrive.
4.3.0 - 2026-10-18
Added
- Searchable models can declare ordered media parts. Path fields name an image, audio or video kind and a storage disk. Indexing loads bounded parts through Storage. Boot and settings sync reject incompatible model profiles.
- EmbeddingGemma 2 can embed images, audio and video locally. The media profile verifies both encoder graphs and their weights with the text model. Rust processors prepare image patches and WAV log-mel features. Video uses a host ffmpeg binary with a timeout. Reference fixtures run without ONNX.
- A knowledge-graph recommender ranks from your own events and relations.
RECOMMEND_ENGINE=graphselects it. A queued rebuild derives a graph of shared engagement (stored only whereRECOMMEND_MIN_PEERSactors agree), public engagement for the typesRECOMMEND_PUBLIC_EVENT_TYPESlists, and relations declared withRecommend::graph_relation. Reads authorize every node and edge first, blend graph paths, stored vectors, followed actors' agreement, freshness, negatives and trust risk per surface with diversity caps, cite the evidence each row rests on, and answer with the starter's rows when the graph's support is thin. - The graph lives in your database or in Memgraph. The
GraphStoretrait ships adatabasestore and, behind thegraph-memgraphfeature, amemgraphstore over Bolt.recommendations:graph-rebuildrebuilds the graph into a new generation and switches readers when it completes. - Search engines recommend and discover from their stored vectors.
SearchEnginegainsstored_vectors,recommendanddiscover; Qdrant answers the latter two natively, and the database and collection engines fold their stored vectors.Recommend::discoversteers a discover query by the viewer's own events.SearchEngine::stored_keysreports which documents a generation holds, so the graph engine leaves out a document that left its index; every shipped engine implements it, and a custom engine needs it to serve the graph engine.
Changed
- Recommendation, search and explanation structs carry new fields.
RecommendConfiggains the graph settings andmin_peers,SearchConfiggainsmedia_max_bytes,IndexTimeSettingsgainsembed_media, andRecommendationExplanationgainsengine,evidenceandfallback_reason. Code that builds one of them field by field without..Default::default()no longer compiles.
Fixed
- A starter suggestion stands on at least three peers. The starter engine kept a
collaborative candidate a single peer contributed, and its explanation
showed a peer count of 1 beside the shared item, which points at that
person; the candidate was one of their own views or purchases.
Recommend::for_userandRecommend::similar_tonow count a collaborative candidate only whenRECOMMEND_MIN_PEERSdistinct peers contribute it, default 3. With fewer, it can still arrive through the affinity, popularity or recent tier, which names no peers. - A model without
updated_atkeeps a search version per row. A searchable model withoutupdated_atcarried version 0 in every document, so a recommendation event or a graph fact could not tell one revision of the row from the next. Each save now raises a version kept in the newsearch_source_versionstable, in the save's own transaction, and Eloquent loads the kept versions with the rows, soto_search_document()returns the row's version without a query of its own. Run your migrations: the table comes withsuprnova::search::migrations(). - A local embedding model keeps its memory bounded on long documents. The
fastembedprovider padded every text in a batch to the batch's longest, and attention memory grows with the square of that length, so one long document among short ones could take a single inference call past 24 GB. It now measures each text with the model's own tokenizer and batches texts of similar length:SEARCH_EMBED_BATCHcounts texts of 512 tokens, a longer text takes the room of several by the square of its length, and a text longer than that runs alone.
4.2.1 - 2026-10-16
Added
- Add a source to a preset's Content-Security-Policy (#156).
SecurityHeaders::csp_source(directive, source)andContentSecurityPolicy::with_source(directive, source)add one source to a directive of the policyfrom_envselected, keeping the preset, its report-only mode and its reporting origins. A directive the policy leaves out starts from the sources it falls back to. An application that allows an analytics host inconnect-srcno longer copies the preset's policy string. - Stream hooks in every Inertia kit. New React, Vue and Svelte applications
get
frontend/src/lib/stream/, Suprnova's own client for the responsesHttpResponse::stream_bytes,stream_jsonandevent_streamsend:useStream,useJsonStream,useEventStreamanduseJsonEventStream, with the names, options and results of Laravel's stream packages. They send the CSRF token from the root template's meta tag or theXSRF-TOKENcookie, and cancel their request when the component unmounts. An existing application can copy the two files from a new scaffold of its kit.
Fixed
View::sharereaches the Inertia root template (#157). The root template rendered without the data shared with every view, so a value shared withView::shareorView::share_for_requestnever reached it, where Laravel's shared data reachesapp.blade.php. It now reads them with Askama'svaluefilter, as other views do:{% if let Ok(domain) = "plausible_domain"|value::<String> %}. Keep such a read inside theif letunless every deployment shares the value, since a missing value fails the render.
4.2.0 - 2026-10-16
Added
- Model search.
Searchableand the typedModel::searchbuilder provide native database, Qdrant, collection and null engines, filters, facets, highlights, scopes and generation rebuilds. Hybrid search uses fastembed or OpenAI-compatible HTTP embeddings, with EmbeddingGemma 2 as the default local model. Opt-in analytics, query suggestions, JSON search and click routes, the Live search-box, the kits' notes search and a judged relevance and latency baseline complete the search surface. - Starter recommendations.
Recommendrecords immutable, deduplicated events and reads scoped collaborative recommendations with affinity, popularity and recent-document fallbacks. Completed runs carry projected explanations, metrics and event provenance; commands generate snapshots, report status and apply application-owned retention. - Opt-in local search inference. The
search-fastembedfeature enables local embeddings, sparse models and reranking. It is off by default; itsortbuild script downloads ONNX Runtime at compile time. The default search build downloads nothing. - pgvector driver.
PgVectorDriverjoins the vector drivers behind thevector-pgvectordefault feature: a Postgres application stores and searches embeddings in its own database. - Search pages in RenderCache. A search on a cached route is stored like
any other render and goes stale when one of its indexes changes: a document
write or removal, a generation switch or a settings sync. Viewer-scoped and
analytics searches are never stored, and
without_render_cache()keeps one search out of the cache.
Fixed
Head::canonical()keeps a//request path on the app's origin (#155). A request for//evil.example/xgave a canonical link to another host. The head now takes the request URL asurl::currentbuilds it,https://example.com//evil.example/x, under the public root.- Inertia kits paint styled under the Vite dev server (#153). The kits
list
src/app.cssas its own Vite entry, so the first server-rendered page loads it as a<link>with the request's nonce instead of waiting for the entry's JavaScript.main.tsandmain.tsxno longer import it. In an existing application, add.entry_points(["src/app.css"])to itsInertiaConfig, add'src/app.css'to the Vite buildinput, and remove the import. - The CLI installs on macOS without warnings (#152). The browser certificate store helpers that only the Linux install path uses are now compiled on Linux only.
- Public responses no longer carry the session or
XSRF-TOKENcookie (#154). A response markedCache-Control: publicor given ans-maxagecould be stored by a CDN or caching proxy with itsSet-Cookielines and replayed to other visitors. The session and CSRF middleware now leave off the cookies the reader already holds; a public response that must deliver a cookie, such as a new session or a rotated remember-me cookie, goes outprivate, no-storeinstead. - The reset email greets the user by name under Magnetar.
PasswordReset::send_linknow looks the account up and greets its name, as the verification and password-changed emails do. A failed lookup sends the plain greeting and logs a warning.
4.1.0 - 2026-10-15
Added
- Error reporting through Sentry-compatible trackers.
Reporterdrivers send scrubbed errors to Rustrak, Sentry or GlitchTip, with bounded background delivery and shutdown flushing. Laravel-shaped helpers and exclusions cover handled errors; requests and background work share the reporting path. Logs, traces and browser reporting are opt-in. The CLI offers local Rustrak, and the reporting chapter documents setup and privacy. - Security headers with per-request CSP nonces.
SecurityHeadersprovides strict, balanced and relaxed presets, validated environment configuration, report-only CSP and violation reporting, HTTPS-only HSTS, and route or group overrides. New full-stack projects register it before every other global middleware; existing applications opt in by registering it. The manual covers every header and the upgrade guide shows the registration.
Fixed
- Framework scripts and asset links share the request's CSP nonce. Inertia
documents and error pages, Vite tags, Head links and scripts, Live bootstrap
assets and stitched RenderCache hits use the nonce the middleware generated.
The document exposes it to Vite and Inertia's client through the
csp-noncemeta element. Complete nonce pages render on every request. - The Live starter's Name boxes show the right name. The register form's Name box started with the word "name", and the profile form showed "name" instead of the user's display name, so saving it unchanged renamed the user. Both now read the component's own field.
- Live component libraries cannot change the application's error
handling. The component scan admitted
Exceptions::reportable,dont_retryanddont_retry_when, so a library could change how the application handles errors and hide its own failures from the error tracker.live:addnow refuses a library that names them, the reporting exclusions orRequest::csp_nonce; reporting an error stays allowed.
4.0.4 - 2026-10-15
Fixed
- A fresh Inertia starter app hydrates its first page without a mismatch.
The React, Vue and Svelte kits loaded their Fluent catalog only in the
browser, so with server-side rendering, on by default since 4.0.0, the
server rendered the raw
welcomekey and the browser the translated heading, and React reported a hydration error. New projects render the same heading from the title prop in both places. - A field shows its own validation message. The Live response named each
issue by its message identifier alone, so a
live:erroroutput under a rejected field read the runtime's generic "Validation failed" while the text a#[validate(message = "...")]rule or the validation catalog provides never reached the page. The server now resolves that text in the request's locale and sends it beside the identifier, and the field's error output shows it. An issue without text, such as a value the field cannot decode, keeps the generic announcement. - A user who changes their own password stays signed in. The session
that made the change recorded the password's earlier epoch, so the check
that ends sign-ins from before a password change ended it too on its next
request, with every other session of the user. A request that resolved
the signed-in user and writes that user's password column through the
model (
save,update, and their transactional forms) now binds its sign-in to the epoch of the values sent to storage once the write commits, so that session continues while every other session and remember-me cookie of the user still ends.EloquentUserProviderrecognizes the written model; a provider of your own implementsUserProvider::written_userto do the same, and a model whose hash lives in another column names it fromAuthenticatable::auth_password_name. A write that bypasses the model, such as a query-builder update, is not seen. - A fresh scaffold is rustfmt-clean.
suprnova newwrote the shared backend templates, the Live kit and the API starter in a layout rustfmt's 2024 style edition rewrites (import order and line wrapping), so a developer's firstcargo fmtchanged files they had not touched. The templates now carry that layout, and a test formats a fresh scaffold of every kind withcargo fmt --check. - The account's own ImageMagick policy applies again. The magick driver
starts ImageMagick with
HOMEnaming its policy directory, which hid the service account's~/.config/ImageMagickfrom its runs, so a policy or configuration the operator kept there stopped applying in 4.0.0. The driver now puts that directory ($XDG_CONFIG_HOME/ImageMagick, else$HOME/.config/ImageMagick) onMAGICK_CONFIGURE_PATHafter the operator's value and before its own directory's last entry: the account's denials and configuration apply as before, and the framework's policy is still the last ImageMagick reads. - The framework's frames below a Live action fit Tokio's default stack. In a debug build the server, the after-response and task-local wrappers, the session middleware and the Live engine used about 1.75 MiB of stack before an action ran, so an action a little deeper overflowed a thread with Tokio's 2 MiB default. The request future is now boxed before each wrapper holds it, as are the Live dispatch and the session handler, and those frames use under 0.8 MiB. A test runs a Live action through the real server on a thread with the 2 MiB default and fails when the frames below the action pass 1 MiB.
- The scroll area's size token is defined. 4.0.2 bounded the region
with
--sn-scroll-area-sizeand left the token undefined, so the shared stylesheet never named it and the engine's token check failed. The shared stylesheet now defines it at 16rem; a page or a region still sets its own.
Changed
- Starter kits ship no translations. React, Vue, Svelte, Live and API
scaffolds include no catalogs, browser translation modules or locale
middleware, and their pages render English text. The framework's
localization is unchanged. An existing application keeps its own files;
one that translates in the browser under server-side rendering renders
raw keys on the server, and the upgrade guide shows the two ways out:
remove the browser translations as new projects do, or translate on the
server with
Lang::getand pass the text in props.
4.0.3 - 2026-10-13
Fixed
- Breadcrumbs sit on one line. The base stylesheet spaces stacked list
items with a top margin, which dropped every crumb after the first below
the first in
suprnova.breadcrumbs. The crumbs now carry no margin and the row aligns them on the baseline. - Avatar group members sit on one row. The same list-item margin
dropped every member after the first in
suprnova.avatar; the members now carry only their overlap.
4.0.2 - 2026-10-13
Added
- A flash region can time its messages out.
flash_regiontakes adurationin milliseconds; a region rendered with one hides each message that long after it appears and holds the timer while the pointer or focus is on the region, as the toast region does. The default, 0, keeps every message until the next document. The region is now wrapped in thesn-flash-regionelement on every branch, which does nothing without a duration.
Fixed
- The horizontal separator has a width inside a grid or flex parent.
A browser's own
hrcarries auto inline margins, which took the free space of the track and leftsuprnova.separatorno width at all; the rule now sets them to zero. - The scroll area scrolls.
suprnova.scroll-areabounded its block size by the measure token, about 640px, so most content fit without a scrollbar. The bound is now 16rem, and a page sets--sn-scroll-area-sizeon the region or an ancestor for another.
Changed
- The tooltip bubble follows the color scheme.
suprnova.tooltipdrew its bubble in the text color with inverse text, a light bubble on a dark page. It now sits on the surface tokens with the border and shadow the popover and the dropdown menu use, so it re-themes with them.
4.0.1 - 2026-10-13
Fixed
- The validation summary shows only while a field or the action is in
error.
suprnova.validation-summaryrendered its red box and title on a form nobody had submitted, and listed nothing after a failed one: its stylesheet hid the section only when it was empty, and the macro always wrote the title inside it. The section now hides until one of its entries shows. The newsummary_entry(name, label)macro, called inside the summary, renders one entry per field the action validates: hidden until that field's validation fails, then a link that focuses the field. The action's own failure shows as the last entry, announced politely. A summary called with no entries still shows the action's failure.
Added
-
The artisan generators. Twenty-one
suprnova make:*commands each write one file from a stub and declare its module insrc/lib.rsand the directory'smod.rs:make:factory(aFactoryfor a model, insrc/factories/),make:seeder(aSeeder,src/seeders/),make:cast(aCast,src/casts/),make:channel(a private broadcastChannel,src/broadcasting/),make:class(a plain struct,src/),make:enum(src/enums/),make:event(anEvent,src/events/),make:listener(aListenerof one event or any event,src/listeners/),make:job(a queuedJob,src/jobs/),make:job-middleware(aJobMiddleware,src/jobs/middleware/),make:mail(aMailable,src/mail/),make:notification(a mailNotification,src/notifications/),make:observer(anObserverof a model,src/observers/),make:policy(a#[policy]with the seven model abilities,src/policies/),make:provider(theregisterfunction the bootstrap calls,src/providers/),make:resource(a JSON:APIDatastruct,src/resources/),make:rule(a validationRule,src/rules/),make:scope(aGlobalScope,src/scopes/),make:test(an integration test intests/, which declares nothing),make:trait(a trait with a default method,src/concerns/) andmake:interface(a trait with required methods only,src/contracts/). A name that is not a Rust identifier is refused with exit status 1, an existing file is kept unless--forceis given, and each command prints the path it wrote.make:factory,make:observer,make:policyandmake:scopetake--model, andmake:listenertakes--event. -
The Live starter kit.
suprnova new --frontend live, or the fourth choice of its prompt, scaffolds an application with no Node toolchain: nofrontend/, nopackage.jsonand no Vite config. Its pages (home, register, sign in, forgot and reset password, verify email, the dashboard, the notes list and one note, and the error page) are server-rendered Live documents in a guest layout or an application layout with the navigation, the signed-in user and the toast. Live components carry the account forms, which show each validation message under its field; the dashboard's note counts, which refresh without a page load when a note is saved; the display-name form; and the notes page, with a search bound to the URL's?search=, a form that writes a note, and a load-more list. The kit keeps the Inertia kits' models, migrations, account flows and route names, and installs the library components its views import undertemplates/suprnova-ui/, recorded insuprnova.toml.suprnova docker:initwrites a Live project a Dockerfile with no Node stage, andsuprnova make:inertiarefuses in one. -
MongoDB connections. The
database-mongodbfeature (off by default) adds theMongofacade on the officialmongodbdriver:MONGODB_URIandMONGODB_DATABASE(orMongoConfig::builder(), with pool options and named connections) configure it, the server and the workers register it at boot, andMongo::connection,connection_named,database,collection::<T>andpingreach it. A missing or malformed URI is an error namingMONGODB_URI, and an unreachable server fails the first call that needs it with aFrameworkError. -
MongoDB queue. With
database-mongodb,QUEUE_DRIVER=mongodbkeeps jobs in ajobscollection (MongoQueueDriver), reserving each with one atomicfindOneAndUpdate, and bringsMongoFailedJobStoreoverfailed_jobsandMongoBatchRepositoryoverjob_batches, whose settlements move the counters with$incin one update and count a redelivered job once. -
MongoDB cache. With
database-mongodb,CACHE_DRIVER=mongodbselectsMongoCacheover thecacheandcache_lockscollections, with TTL indexes on the expiry, atomicaddand counters, tags, and locks shared by every process. -
MongoDB sessions.
SESSION_DRIVERselects the session store:database(the default) or, withdatabase-mongodb,mongodb, which keeps sessions in asessionscollection (MongoSessionDriver) and promotes a two-factor session with one atomic update.Config::initrefuses an unknownSESSION_DRIVER. -
MongoDB document models.
#[suprnova::document(collection = "...")]stores a struct in a collection with the Eloquent calls of theDocumentModeltrait:create,find,find_or_fail,all,query,save,update,delete,fresh,refresh,makeandfill. The key is anObjectIdstored as_idunlessprimary_keynames a field;fillable,guarded,casts,hiddenandvisibletake the#[model]syntax;chronodates are stored as BSON datetimes and decimals asDecimal128;created_atandupdated_atare managed;soft_deletesaddswith_trashed,only_trashed,restoreandforce_delete;#[embeds_one]and#[embeds_many]fields store embedded documents with relation methods;push,push_unique,pull,incrementanddecrementchange one field; the model events reach listeners and aDocumentObserverregistered with#[suprnova::observer]; and the model serializes through serde and binds from routes by its key. -
MongoDB document queries. A document model's
query()answers aDocumentQuerywithwhere_(=,!=,<,<=,>,>=,like),or_where,where_in,where_not_in,where_null,where_not_null,where_between,where_date,where_exists,where_raw,order_by,skip,take,project,get,first,count,exists,pluck,distinct,sum,avg,min,max,paginate,simple_paginate,update,upsert,delete,force_delete,increment,decrement,push,pullandunset, andgroup_bywithcount,sum,avg,minandmaxaggregates.to_filter()andto_pipeline()answer the BSON the builder sends, and a chain MongoDB cannot run as written, such astakebeforeupdate, is an error naming the call. -
MongoDB relations.
relations = { ... }on#[suprnova::document]declaresHasOne,HasMany,BelongsToandBelongsToManybetween documents (the many-to-many kept as arrays of keys on both sides, written byattach,detach,detach_allandsync) andBelongsToModel<M>to an SQL model, and#[suprnova::model]declaresHasManyDocuments<D>andHasOneDocument<D>; each reads through its own store,DocumentQuery::withand the SQLwithandwith_countload them with one query per relation, dotted paths cross the stores, and a relation whose key types cannot match fails the build naming both models. -
Concurrent tasks. The
Concurrencyfacade runs#[concurrent_task]functions (anasync fnwith serde input and output, registered by name) side by side:runanswers eachTaskResultin order,run_namedanswers them by key,with_timeoutends a task that outlives it with an error naming it, anddriverpicks a driver for one call. Thetokiodriver (the default), theprocessdriver (each task in a console process through the hiddenconcurrency:runcommand) and thesyncdriver implementConcurrencyDriver;CONCURRENCY_DRIVERselects the default, andConcurrency::extendadds a driver. -
Deferred concurrent tasks.
Concurrency::deferreturns at once and runs its tasks after the response has been sent, logging a failed task without touching the response; outside a request the returned handle runs them when it is awaited or dropped. -
A guard in use per request.
TestClient::acting_as_with_guardselects the named guard as the oneAuth::user,Auth::id,Auth::checkand the auth middleware without a guard name answer through for that request, as Laravel'sactingAswith a guard callsshouldUse; the configured default guard is untouched outside that request. -
One guard instance per request. Inside a request the auth manager builds one instance per guard name and keeps it, so a custom guard's factory runs once per request and a guard may keep its user on the instance.
-
Factory record batches.
create_manyaccepts a count or per-record attribute maps, with each map overriding the factory definition. -
Custom ULID lengths.
ulid_with_lengthand thelengthmodifier create ULID columns with the length your schema needs. -
Schema SQL previews.
Blueprint::create_sqlreturns the validated CREATE statements for your selected database engine. -
Seeder composition.
callruns children in order with console progress;call_silentsuppresses progress andcall_onceskips completed children. -
Seeder parameters.
call_withpasses an attribute map torun_withwhile existingrunimplementations keep working. -
Root seeders.
register_rootselects the seeder a baredb:seedruns. -
Seeder connection selection.
db:seed --databasescopes default queries and factories to the named connection for the invocation. -
Conditional resource field groups.
merge_whenmerges an object into resource attributes when its condition holds, with sparse fieldsets applied to the merged fields. -
Relation existence flags.
with_existsloads a boolean per parent without loading related models, alongside any requested rows or counts. -
Resources read existence flags.
when_exists_loadedemits loaded true and false values and omits fields whose flag was not loaded. -
Application-wide JSON:API information.
jsonapi_defaultsets boot-time implementation information for every resource document; a response can override it. -
Cursors over several columns. Cursor pages preserve each ordered column and direction, with named typed boundaries available through
Cursor::parameter. -
Page item transformations.
throughchanges a length-aware, simple or cursor page's item type while preserving all pagination metadata. -
Missing-row messages on query builders.
first_or_failnames the model or table, andfirst_or_fail_withaccepts your message while keeping HTTP 404. -
Nested closure transactions. Inner
DB::transactioncalls use savepoints; an inner rollback keeps the outer transaction open. -
Transaction depth.
DB::transaction_level()reports the ambient nesting level. -
Rollback callbacks.
DB::after_rollbackruns compensation for the enclosing rollback and preserves callbacks from successful inner scopes until the outer outcome. -
Guards before transactions.
DB::before_starting_transactionruns listeners before BEGIN or a savepoint and propagates a listener's error without starting it. -
Raw query expressions.
DB::rawsupplies SQL for updates, grouping and aggregate filters while ordinary values and raw-fragment bindings stay bound. -
Table query ranges.
where_between,where_not_betweenand their OR forms accept inclusive bounds, raw expressions and scalar subqueries. -
Table query maximums.
maxreads typed values and returns none for an empty set. -
Table queries ordered by age.
oldestandoldest_byorder rows ascending. -
Seeded random query ordering.
in_random_order()orders rows randomly on both builders, andin_random_order_seeded(seed)repeats an order with RAND(seed) on MySQL and setseed with random() on Postgres; SQLite orders by a seed-derived expression over each row'srowid, then by therowid, on both builders, so the same seed repeats the order for any primary key type, a union and its pages included. -
Inspect applied model scopes.
apply_scopesreturns the builder with its registered global scopes and soft-delete filter applied once. -
Polymorphic existence queries.
has_morph,doesnt_have_morphand their constrained forms query the relation's targets and registered types and aliases; the wildcard covers the targets the relation declares, and wildcard absence includes rows with a null type. -
Delete loaded pivots by their keys. Pivots without an
iddelete their original key pair; morph pivots also keep the type in the predicate. -
Eager limits apply per parent. Has-one, has-many, morph-one and morph-many constraints use a partitioned window for
limitandtake. -
Morph relations fill ownership on writes.
create,saveandupsertset the owner's id and type on morph-one and morph-many children. -
Loaded model lookup by key. Collections find one model, another model's key, or several keys, and return a supplied fallback for a missing key.
-
Constrained loading on model collections.
load_withloads a relation onto existing models with a typed builder constraint. -
Model collection deduplication by key.
unique_modelskeeps the last copy of each model while retaining the first occurrence's key order. -
Model collection differences by key.
diff_modelsremoves matching identities even when the models' other attributes differ. -
Enum collection casts.
AsEnumCollectionreads and writes JSON arrays of the same variant strings asAsEnum. -
Runtime appended attributes.
appendselects registered accessors for every later conversion of one model instance. -
Complete raw original snapshots.
get_raw_originalsreturns every loaded column before casts;get_raw_original_orsupplies absent values. -
Instance visibility changes.
make_hidden,make_visible, and their conditional forms update the lists used by later model conversions. -
A single-server default for scheduled tasks.
Schedule::always_on_one_server()elects one replica per tick for every task;.on_every_server()opts out. -
Interrupt running schedules.
schedule:interruptwrites a shared cache mark. Runs stop before starting another task, and the next run clears it. -
Stored keys for chunk cursors.
chunk_by_idadvances from the raw stored key, so primary-key casts cannot skip or repeat rows. -
A database default scoped to one task.
DB::with_default_connection(name, future)routes default database and model queries to that pool.DB::default_connection()names the current pool, and concurrent tasks keep their own defaults. -
Declared model defaults.
#[model(defaults(field = value, ...))]fills new instances and partial creates while preserving supplied attributes. -
Related records map in chunks.
chunk_mapon belongs-to-many and through relations maps each record in bounded batches and returns values in order, with pivot context on many-to-many records. -
Related records are found or created with their keys.
first_or_createon has-one, has-many and belongs-to-many sets the relation's foreign key or attaches the pivot row, including custom relation keys. -
Relation counters create or increment.
increment_or_createon has-one, has-many and belongs-to-many uses the default for a new record or adds the supplied step and extra columns to an existing record. -
Through relations return an unsaved fallback.
find_or_newsearches the relation's reachable records and returns a new instance when none match. -
Has-one-through compares in one query.
isasks the database whether the relation reaches a model without loading the target. -
Queue worker idle delays.
queue:work --sleepsets the seconds between empty polls beside the existing millisecond--polloption. -
Queue worker attempt controls.
--triesand--timeoutset a worker's attempt budget and timeout without changing the queued payload. -
Queue workers with a stopping point.
--oncesettles one job and--stop-when-emptydrains available jobs before the worker exits. -
Queue worker memory limits.
--memorychecks resident memory from procfs after each job and returns status 12 when it exceeds the limit. -
Filtered queue absence assertions.
assert_not_pushedrejects a captured job that satisfies your predicate. -
Filtered queue assertions.
assert_pushed_on_queuematches the queue and your predicate against the same captured job. -
Commands after the response.
Bus::dispatch_after_responseruns a command after the response body is written and the socket flush succeeds. -
Typed bus capture lists.
dispatched,dispatched_syncanddispatched_after_responsereturn captured commands for iterator filters. -
Markdown responses.
HttpResponse::markdownandmarkdownpreserve your source with a UTF-8 Markdown content type. -
QUERY routes.
query!and the fluent routing methods accept QUERY, andany!includes it with the other supported methods. -
Sign out your other devices.
Auth::logout_other_devicesverifies your password and revokes other sessions and remember credentials while keeping the current browser signed in. -
Typed notification assertions. The notification fake filters recorded notifications by concrete type, recipient route, and notification contents. Existing name-based assertions keep working.
-
Copy files across disks.
Storage::copy_to_diskstreams between disk names or ready-made disk handles and keeps the source. -
Move files across disks.
Storage::move_to_diskcopies the file before deleting the source and reports transfer or deletion failures. -
Forget several disks.
Storage::forgetaccepts one name or a list and reports whether any registered disk was removed. -
Purge one disk or every disk.
Storage::purge(name)drops one named disk andpurge_alldrops every disk. -
Store a ready-made disk.
Storage::setregisters an operator under a name and replaces the previous disk and its public URL. -
Language-specific slugs.
Str::slug_inapplies the named language's ASCII spelling, including Germanäasae. -
Word limits keep markup.
Str::wordslimits space-separated runs while retaining markup and whitespace between words. -
Esperanto and Italian word forms. Plural and singular helpers now use all eight languages from doctrine/inflector, selected by the current locale.
-
Plurals for class names.
Str::plural_studlyandStr::plural_pascalinflect the last word of a class name. -
Counted labels use exact integers.
Str::plural_with_countadds the count in the current locale's number format, preserving every digit. -
Redis environment connections. With
REDIS_URLunset, the default connection readsREDIS_HOST,REDIS_PORT,REDIS_PASSWORD, andREDIS_DB. -
A cache connection for Redis. The
cacheconnection uses the same server and credentials withREDIS_CACHE_DB, defaulting to 1. -
Redis scripts by SHA.
RedisConnection::evalsharuns a loaded script with prefixed keys and unchanged script arguments. -
Raw Redis command lines.
RedisConnection::execute_rawsends a command line with the existing read retry policy and shared-connection guards. -
The built-in custom log channel. Set
LOG_CHANNEL=customandLOG_CHANNEL_DRIVERto a driver registered withLog::extendin the bootstrap. A missing or unregistered driver fails boot. -
Percentages in a named locale.
Lang::percentage_informats in the named locale without changing the current one. -
Precision controls for numbers.
Lang::format_with_max_precisionandLang::percentage_with_max_precisioncap fraction digits and drop trailing zeros.Lang::formatkeeps fixed precision. -
Default number locales.
Lang::use_localesets the default outside request scopes. -
Temporary number locales.
Lang::with_localerestores the previous locale when its closure returns or panics. -
Generated downloads stream as you produce them.
HttpResponse::stream_download(stream, name, content_type)sends each chunk without buffering the export and writes a safe download filename. -
File response headers and dispositions.
HttpResponse::file_withanddownload_with, andStorage::response_withanddownload_with, accept caller headers and a disposition. Your content type and cache policy reach the client. -
Schema dumps without migration data.
schema:dump --without-migration-datawrites the schema while leaving applied migration rows out of the file. -
Named connections for schema dumps.
schema:dump --database reportingdumpsDATABASE_REPORTING_URL; an unknown connection fails with its name. -
Input preparation before authorization. Form and multipart request hooks expose
prepare_for_validation.Request::transform_inputnormalizes text when parsing starts, preserving authorization before the body is read. -
MIME family allowlists.
MimeTypeaccepts entries such asimage/*while retaining content detection and rejecting spoofed image headers. -
Column comparisons take an operator. Both query builders expose
where_column_op(a, op, b), with the existing identifier and operator checks. -
Cross joins take conditions. Both query builders expose
cross_join_with(table, closure); the closure'sONvalues stay bound. -
Equality shortcuts on both builders.
r#where(column, value),db_where(column, value)andor_where(column, value)use=. -
Previous values after a model save.
get_previous(attribute)reads the stored value before the last save changed that attribute, alongsidewas_changed,get_changesand the original-value accessors. -
Precognition with per-route opt-in. Add
Precognitiveto a route or group to validate a draft without running the handler body. A passing request answers204withPrecognition-Success: true; every marked response carriesPrecognition: true, and every response from the route addsPrecognitiontoVary.Precognition-Validate-Onlynarrows rules before every validation stage, including the asynchronous hook. Names match exactly, with*matching one segment; an empty list validates no fields. An unlisted parse failure does not block the answer, and after-validation hook errors are never filtered.- Live validation reads query data for
GETandDELETE, multipart files and fields, and inlineRequest::validate::<T>(). - A marked request neither saves the session nor becomes the previous URL, so live validation leaves flash data for the next page.
- The
422message summarises the first error and the count of the rest, with the count suffix localized through the catalog and the field-keyederrorsbag kept. with_precognition()sends the request header, andassert_successful_precognition()checks the status and success header. The new Precognition chapter covers the Inertia 3.8 Vue, React and Svelte clients, uploads, narrowed rules and side effects.
-
The Svelte kit on Inertia 3.8 and its Vite plugin. The kit pinned
@inertiajs/svelteto the 3.6 client, globbed its pages by hand in both entries, and passedcreateInertiaAppnotitle,serverHeadornonce. It now declares@inertiajs/svelte,@inertiajs/coreand@inertiajs/viteat^3.8.0. The plugin resolvespages: './pages'and wrapssrc/ssr.ts, a singlecreateInertiaAppcall, into the SSR server, whichnpm run build:ssrstill writes tofrontend/bootstrap/ssr/ssr.js. The entry reads itsnoncefrom<meta property="csp-nonce">when the document has one (K01, K05, K18, K19). -
Svelte kit layouts, links and titles. Every page drew its own frame, reached other pages through anchors that reloaded the document, and set no tab title.
layouts/AppLayout.svelteandlayouts/GuestLayout.sveltenow frame the pages throughcreateInertiaApp'slayoutoption and stay mounted across visits. Both layouts show the signed-in user from the sharedauthprop, or sign-in and register links for a visitor, throughcomponents/AccountLinks.svelte. Every navigation is aLink, and sign-out is aLinkwithmethod="post"rendered as a button. The dashboard sets the layout's heading withsetLayoutProps.@inertiajs/sveltehas noHeadcomponent, socomponents/Head.sveltetitles each pageTitle - Appthrough<svelte:head>(K06, K07, K16). -
A flash toast in the Svelte kit. No page read
page.flash, so an action showed no feedback. Both layouts now showpage.flash.toaston the one page that carries it, typed by the generatedflashDataType(K17). -
The Svelte kit's dashboard, notes pages and auth forms. The dashboard now loads its
statswithDeferredand polls them withusePoll, loadsrecent_noteswithWhenVisible, and changes the display name throughuseHttp, showing the new name at once in the page and the layout and putting the old one back with the field's error on a422. The newNotes/Indexpage creates a note with theFormcomponent, remembers its search withuseRemember, scrolls withInfiniteScroll, and opensNotes/Showwith a prefetched, instantLink. The auth pages submit throughForminstead ofuseForm, and Login turns itsremembercheckbox into a boolean withtransform(K11, K12, K13, K14, K15, K21). -
The React starter runs on Inertia 3.8 through its Vite plugin. The kit pinned
@inertiajs/reactat^3.6.1, resolved pages with its ownimport.meta.globin both entries, and passedcreateInertiaAppno title callback, no server head and no CSP nonce. It now declares the adapter,@inertiajs/coreand@inertiajs/viteat^3.8.0, resolves pages through the plugin'spages: './pages', and buildssrc/ssr.tsxthrough the plugin, sonpm run build:ssrstill landsfrontend/bootstrap/ssr/ssr.jsforsuprnova ssr:start. Both entries pass atitlecallback that appends the project's name (fromfrontend/src/lib/app.ts) andserverHead: true; the browser entry passes the nonce of<meta property="csp-nonce">when the document carries one. A newnpm run checkscript type-checks the kit (K01, K05, K18, K19). -
The React starter has persistent layouts,
Linknavigation and page titles. Each page drew its own frame and reached other pages through<a href>, which reloaded the document on every click, and no page set a title.layouts/GuestLayout.tsx(theauth/pages) andlayouts/AppLayout.tsx(navigation and a heading) now come fromcreateInertiaApp'slayoutoption and stay mounted between pages that share them. Both show the signed-in user from the sharedauthprop: the name and a sign-outLinkwithmethod="post"rendered as a button, or the sign-in and register links for a guest. Every application link is aLink, every page sets<Head title>, and the dashboard sets the layout's heading withsetLayoutProps(K06, K07, K16). -
The React starter shows the flash toast. No page read
page.flash, so a sign-in, a registration or a reset showed no feedback. Both layouts rendercomponents/FlashToast.tsx, which showspage.flash.toast, typed by the generatedflashDataType, read from the page on every render, so it is gone on the next visit (K17). -
The React starter demonstrates deferred, optional, polled, optimistic and infinite-scroll pages. The dashboard sent one prop, nothing was paginated, and the auth pages posted through
useForm.Dashboardnow rendersstatswithDeferredand a fallback, polls it withusePoll(10000, { only: ['stats'] }), loadsrecent_noteswithWhenVisible, and changes the display name throughuseHttp, showing the new name at once and putting the old one back witherrors.nameon a422; a saved name reloads the sharedauthprop, so the layout shows it too. The newNotes/Indexpage creates a note withForm, remembers its search withuseRemember, lists the signed-in user's notes withInfiniteScrollover the cursor paginator, and opens a note through a prefetched instant visit to the newNotes/Showpage. Every auth page, the verification resend included, submits throughFormand disables its button whileprocessing(K11, K12, K13, K14, K15, K21). -
Third-party Live component libraries. A library is a git repository with one fixed tree:
library.jsonat its root and, undercomponents/, one directory per component holding itsmanifest.json, the files the manifest names and amanifest.sig. A component can carry the Rust of a Live component as well as a view, a stylesheet and a script.suprnova live:add acme/acme-ui/counterinstalls one by address from GitHub, or from GitLab or Codeberg with the host first, at the newestv<semver>tag or the one@<version>names; anhttps://URL of a component directory and a./pathon disk work too. Every component is signed with Ed25519 over a hash of everything that arrived. The first install pins the library's key insuprnova.tomlonce you confirm on a terminal, and every later version must be signed by that key, or by a new key the pinned one handed over to inlibrary.json'spreviousKeys. Before it writes anything,live:addscans every view, stylesheet, script and Rust file as data, runs none of it, admits only what it can classify, and shows a plan of every file, module declaration, registration and capability. A component reaches a database, the network, files, mail, a queue, a cache, the session, the environment or a process only through Suprnova's API, and you approve each of those nine capabilities by name, on a terminal or with--allow;--yesconfirms a plan and never approves a capability or pins a key.live:addwrites a component's Rust undersrc/live/<namespace>/, registers it in your registry builder, never changesCargo.tomlorCargo.lock, and records the source, version, commit, digests, hash, signature, registrations and approvals insuprnova.toml, whichlive:checknow verifies offline. An install holds a lock on the project and writes a journal before its first write, so a failed or killed install leaves nothing behind, andsuprnova servewaits for it before it builds (suprnova live:wait). Authors scaffold, check and sign a library withsuprnova live:registry new,checkandsign, and move it to a new key withrotate-key;newadds apreview/application that renders each component from where it sits, and keeps the private key in your configuration directory, or whereSUPRNOVA_LIBRARY_KEYnames it. Each library's stylesheets and scripts are served at/<namespace>-ui/{component}/{file}by oneRouter::try_live_ui_assets_for("<namespace>")call, whichlive:addnames at the library's first install. See Installing Live Components and Live Component Libraries. -
Route model binding by type.
#[handler]binds an argument by its type alone (post: Post) whenever the type implementsRouteBinding, which every#[model]does, andOption<T>bindsNonewhen its optional parameter is absent. Routes take{post:slug}segments,#[model(route_key = "...")]sets a model's default column, children bind through their parent's relations (scope_bindings(),without_scoped_bindings()), and routes, groups and resources takewith_trashed()andmissing(). A generic#[handler], and a#[handler]that a closure route, middleware, another handler or amissing()handler calls with the request, binds at the request as the route's own handler does. Such a handler that takes a scoped child without its parent finds it through the parent the route's handler binds; where the router cannot see how the route's handler binds that parent, the request answers 500 and names the parent to take. One that cannot return themissing()response hands it to the middleware or route handler that called it, which answers with it in place of a 404, so the middleware outside that caller sees it as it sees the route's own.Router::bindandRouter::modelregister custom resolution,#[model(custom_route_binding)]withsuprnova::database::resolve_model_route_bindingoverrides a model's own, and#[derive(RouteBinding)]binds a unit-only enum.resource!andapi_resource!build resources from a module's#[handler]functions, nested resources (users.posts) included.route()andtry_route()take bound values, named or as one positional value: a#[model]row, a derived enum, aRouteParam<T>, or any type that implementsRouteValuewith one call tobound_route_value.try_routeis re-exported at the crate root.Router::prepare_bindings()runs the startup checks for a router a test builds. See Routing. -
Serving under a path prefix. Behind a trusted proxy, an application serves under the prefix
X-Forwarded-Prefixnames, or under the path inAPP_URL. Every URL the framework builds for the browser carries that public root once:route()and the signed URLs, redirects and the previous and intended URLs, Inertia's page URL and Vite tags, Live's endpoints, assets and reflected URLs, pagination links, storage URLs and the session, XSRF and remember-me cookie paths.url::root()returns the root for a template, and a third-party component's view may call it before a constant path.RootSharegives every Inertia page the root, and a new scaffold works under a prefix. See Deployment Overview and URL Generation. -
The rest of Laravel's Image API.
Image::orient,using,transform,rotate_with_background,flip,flop,optimize,width,height,to_webp,to_jpg,to_jpeg,to_png,to_gif,to_bmp,to_base64,to_data_uriandstore_as, withColor,ImagePixels,CustomTransformationandregister_transformationfor a step of your own. See Images. -
Running on a Laravel database. A Suprnova application runs on a database a Laravel 13 application created, and beside that application.
jobs,job_batches,failed_jobs,sessions,notifications, the scaffold'susers,features(laravel/pennant) androles,permissions,model_has_roles,model_has_permissionsandrole_has_permissions(spatie/laravel-permission) take the layouts Laravel's and the packages' migrations create. Data those layouts have no column for lives insuprnova_jobs_reservations,job_batch_settlements,suprnova_feature_details,suprnova_role_detailsandsuprnova_permission_details. The framework shipsqueue::migrations::{CreateJobsTable, CreateJobBatchesTable, CreateFailedJobsTable}andsession::migrations::CreateSessionsTable, and each migration leaves a table Laravel or a package created exactly as it is.NOTIFICATIONS_MORPH_KEYandRBAC_MODEL_KEYpickint,uuidorulidkeys, andFEATURES_USER_SCOPEnames the user scope Pennant stores. See Running on a Laravel Database. -
LARAVEL_SHARED_DATABASE. For an application that shares its database with a running Laravel application: the framework and Magnetar write$2y$bcrypt hashes Laravel 13 accepts withHASH_VERIFY=true, a valid sign-in rewrites a$2b$or Argon2id hash as$2y$and fails with the storage error, signing nobody in, when that rewrite cannot be stored, Magnetar no longer upgrades bcrypt to Argon2id, and an unrouted database-queue job is stored on the queuesuprnova, which Laravel's worker does not read.LaravelDatabase::shareturns it on from code. -
Morph aliases.
#[model(morph_type = "App\\Models\\Post", morph_aliases = ["post"])]:MorphTo,MorphOneandMorphMany, direct and eager,has,with_countand the aggregates accept every name; writes store themorph_type. -
Application::run_with_argsparses the given arguments instead of the process's and returns its failures to the caller as aFrameworkError;run()still prints them and exits. -
HasRoles::rbac_model_types()names everymodel_typea model's role and permission assignments are read under: itsmorph_type, its aliases and the Rust type path an earlier release stored. -
Merge props merge at nested paths in either direction.
Prop::append_at(paths, match_on)andProp::prepend_at(paths, match_on)are Laravel'sappend($path, $matchOn)andprepend($path, $matchOn): they take one path or a list, add{path}.{match_on}tomatchPropsOnwhen a field is named, and one prop can append at one path and prepend at another, which the single direction ofmerge_with_pathcould not express..append_at(["a.items", "b"], "id")on a propfeedemitsmergeProps: ["feed.a.items", "feed.b"]andmatchPropsOn: ["feed.a.items.id", "feed.b.id"]. -
Once props take Laravel's options.
untiltakes a moment or a span, as Laravel'suntil(DateTimeInterface|DateInterval|int)does: aDateTime<Utc>, astd::time::Duration, achrono::Durationor whole seconds, through the newOnceUntil.freshtakes abool,OnceOptions::once(false)turns the flag off,Prop::once_with(options)sets the flag, key and expiry in one call (Laravel'sonce($value, $as, $until)), andas_keytakes an enum whoseDisplaynames the key.expiresAtis the expiry in milliseconds counted in whole seconds, as Laravel counts it. The server still refuses a client's cache claim past aDateTimedeadline, which Laravel leaves to the client. -
App::inertia_share_oncereturns the shared once prop, aSharedOncePropthat takesas_key,until,freshandonce_withas Laravel'sshareOncereturns a chainableOnceProp. A shared once prop could not take a cache key, an expiry orfreshbefore; only theInertiaSharedDataprovider could reach them.InertiaRegistry::share_oncereturns the same handle. -
Scroll props take any page-facts provider and can read them from the loaded value. Every
.scrollbuilder andProp::scrolltake aScrollMetadataor anything implementingProvidesScrollMetadata, so.scroll("posts", &page, &page)is Laravel'sInertia::scroll($paginator).InertiaResponse::scroll_lazy,scroll_lazy_withandProp::scroll_lazydescribe a lazily loaded list from the value its resolver returns, as Laravel's callable metadata does, and ship thescrollPropsentry with that value. -
Paginators report the scroll facts Laravel's
fromPaginatordoes. ACursorPaginator's current page is1on its first page, else the cursor it was fetched with (Pagination::cursorrecords it in the newcurrent_cursor,with_current_cursorsets it), else the request's cursor parameter; it was alwaysnull.Paginator(the simple paginator) takes a page parameter name,with_page_name, used by its URLs and itspageName, where it was fixed topage. -
Prop providers, page and shared. A type implementing
ProvidesInertiaPropertiesexpands into props once per render with aRenderContextof the page component and the request, Laravel's interface of the same name. A page takes any number withInertiaResponse::provide, the shared props any number withInertiaRegistry::share_provider; shared providers' keys count as shared keys, andflush_sharedclears them. A page also takes any number of#[derive(Data)]objects withwith_data(andtry_with_data), where it took one, throughInertia::data, with no request or component context. -
A prop value can convert itself with its context. A type implementing
ProvidesInertiaProperty(Laravel's interface of the same name), attached withInertiaResponse::with_propertyorProp::property, is converted when the prop is sent, with aPropertyContextof its key path, its sibling props and the request, so a price can format itself with the page's currency. No value type received its key path, siblings or request before. -
An application-owned Inertia root document. The framework wrote every first visit's whole document itself, so an application had no place for its own favicon, fonts, meta tags or attributes on
<html>and<body>.#[inertia_root(path = "app.html")]declares an Askama template undertemplates/that receives the framework's parts (title,head,body,lang,csrf_token,nonce,ssrandview), checked at compile time, andInertiaConfig::root_templaterenders every first visit through it.root_template_withchooses the template per request, Laravel'srootView(Request), and error pages go through the same choice;InertiaResponse::with_view_datahands the template values of any serializable type that never reach the page props, Laravel'swithViewData. The page JSON is written straight into the template's output: a first visit with a 1 MiB prop allocates 5,386,301 bytes through a template against 5,386,925 through the framework's document, and a 3 MiB page comes back whole. A template that fails to render is an error response, never part of a document.InertiaConfig::mount_idnames the mount element and the page data element,appby default, for a client that mounts on another id. Without a template the first visit is byte for byte what it was. -
Inertia::versionandInertia::get_version. Laravel's runtime setter and getter for the asset version.Inertia::versiontakes a string, a function called on every read, orNone::<String>for the empty version (Laravel'snull), and replaces the installed config's version;Inertia::get_versionreturns the current one. Every page built after the call advertises it, and the version middlewareInertia::installregisters now readsInertia::get_versionper request instead of the version captured at install (RF-05). -
Big integers survive the trip to the browser. JavaScript reads integers exactly only up to 9007199254740991, so a 64-bit id beyond it, 9007199254740993 for one, reached an Inertia page as 9007199254740992. With the new
InertiaConfig::preserve_big_integers(true)setting, orInertiaResponse::preserve_big_integers(true)for one response, every integer beyond plus or minus 9007199254740991 in props and flash, at any depth, is sent as{"$bigint": "<digits>"}and the page carriespreserveBigIntegers: true, so the Inertia client restores it as an exactBigInt, as Laravel'spreserve_big_integersdoes. Off by default; when off nothing is wrapped and the flag is absent (JE-04, JE-05). -
Inertia::back(status, fallback)andInertiaConfig::store_previous_url.backis Laravel'sInertia::back(): the request'sRefererwhen it is a path on this host under the public root, else the session's previous URL, else the fallback, else/(RF-18).store_previous_url(on by default) turns the previous-URL recording of Inertia visits off (MW-06). -
Inertia flash on the facade:
Inertia::flash,flash_many,get_flashed,pull_flashed,clear_historyandpreserve_fragment.flashtakes a string key or any type implementing the newFlashKeytrait, such as an application's enum of toast kinds;get_flashed(&req)returns exactly whatpull_flashed(&req)removes (RF-17, RF-19, RF-08, RF-09). -
Shared data and render settings on the
Inertiafacade.Inertia::share(key, value),share_many,share_data(a#[derive(Data)]object's eager fields) andshare_providertake the forms Laravel'sInertia::sharetakes;get_shared(key, default)andget_shared_all()read shared data back.transform_component_usingrenames components before they render, andInertiaConfig::ensure_pages_exist(withpages_dirandpage_extensions) makes a component with no page file an error naming the component and the directory, for a name given as a string too (RF-02, RF-03, RF-07, RF-15). -
SSR controls on the
Inertiafacade.Inertia::disable_ssr(bool)anddisable_ssr_if(fn)replace the configuration's switch, per request for the function, and can turn SSR on as well as off;without_ssr(patterns)adds exclusions;configure_ssr_request_using(fn)adjusts the request sent to the worker through the newSsrRequest(headers, a bearer token, the timeout), so a worker that needs a token can be reached (RF-11, RF-12, RF-13). -
Inertia::location(url or redirect), Laravel'sInertia::location, besideInertiaResponse::location, both taking a URL or aRedirectthrough the newInertiaLocation(RF-16, HM-04). -
Inertia middleware hooks and the stack on a route group. The
InertiaMiddlewareHookstrait carries Laravel's overridable middleware decisions (version,share,share_once,root_view,url_resolver,on_empty_response,on_version_change,on_redirect_with_fragment), each defaulting to the framework's behaviour;InertiaConfig::hooksinstalls an implementation,DefaultInertiaHooksis the framework's answer to start from, andInertiaVisitis the request anon_*hook answers.Inertia::middleware(&cfg)is the whole stack as one middleware for a route group, andInertiaConfig::register_globally(false)makesInertia::installregister it as the named middlewareinertiainstead of on every route, so an API group carries noVary: X-Inertiaand has no redirect turned into303(MW-08, MW-10). -
The SSR call is a driver you can replace. The
SsrGatewaytrait carriesdispatch,is_healthyand the capabilitiesdisable,exceptandconfigure_request_using, each a default an implementation overrides, as Laravel'sGateway,DisablesSsr,ExcludesSsrPaths,ConfiguresSsrRequestsandHasHealthCheckdo.HttpGatewayis the default;App::bind::<dyn SsrGateway>(Arc::new(..))makes an application's own gateway render every first visit.Inertia::disable_ssr,disable_ssr_if,without_ssrandconfigure_ssr_request_usingact on the bound gateway and log a warning naming the capability it lacks.Inertia::ssr_is_healthy()returns the gateway's health: the HTTP gateway asksGET {url}/healthwithin the SSR timeout, through the request configurator,Some(true)on a 2xx andSome(false)otherwise, andNonemeans the gateway has no health check.detect_ssr_bundleandCONVENTIONAL_BUNDLE_PATHSare Laravel'sBundleDetector(SS-10, SS-13). -
SsrRenderFailed, the event of a failed SSR render. It carries the page's component and URL and the worker's error JSON:error,error_type(anSsrErrorType:browser-api,component-resolution,render,connectionorunknown),hint,browser_api,stackandsource_location. A worker that cannot be reached dispatches it with typeconnectionand the transport error. It is dispatched before the visit falls back to the client, and only when something listens or a fake records it (SS-08). -
SSR through the Vite dev server in development. While the Vite hot file exists, a first visit in development is posted to the dev server's
/__inertia_ssrwithout the bundle check, so no SSR bundle or worker process is needed while developing.suprnova servewrites the dev server's URL topublic/hotwhen it starts Vite and removes the file when Vite stops orserveexits, as Laravel's Vite plugin does, and the full-stack scaffold ignores/public/hot.SsrConfig::hot_url(InertiaConfig::ssr_hot_url) sends every first visit in development to another address, andSsrConfig::hot_file(InertiaConfig::ssr_hot_file, defaultpublic/hot) names another file; the address is the hot URL, else the file's content, else thevite_dev_serverURL. Without the file the visit takes the worker path, whatever listens at the dev server's port, and production never goes hot.suprnova servewrites the file only whenfrontend/package.jsondeclares@inertiajs/vite, the Inertia Vite plugin that serves/__inertia_ssr: without it the dev server serves no SSR, so no file is written and a first visit takes the worker path (SS-05). -
SSR runtime settings.
SsrConfig::runtime(nodeby default, orbun,denoor a path) andensure_runtime_exists(off by default), set withInertiaConfig::ssr_runtimeandssr_ensure_runtime_exists, are Laravel'sinertia.ssr.runtimeandensure_runtime_existsforssr:start. -
Inertia::handle_exceptions_using(callback)decides every error response, Laravel'sInertia::handleExceptionsUsing. The callback receives anInertiaErrorResponsefor each error response the framework renders - a handler's or a middleware'sErr, a panic, the router's404, a middleware's own{"message": ...}answer - for every request type, an API client's included. It readsstatus(),error()(the error report, or the panic's message and location),request(),method()andresponse(), which with debug on is the development error page where that page applies. It returnsrender(component, props)for an Inertia page at the original status,respond_with(response)for any other response, orNoneto keep the response. A callback that panics is a bug the panic boundary reports as the sanitized500with its report, inside the stack and at the server alike. A JSON client's validation422reaches the callback like any other error, as in Laravel; an Inertia visit's validation failure reaches it as the303back to the form, since the error-response middleware sits outside the validation redirect, so an Inertia form still goes back with its errors flashed. A rendered page carries the shared props, the middleware hooks'shareandshare_onceincluded, only afterwith_shared_data().InertiaConfig::error_pageis now the default callback and keeps its rule; an app that sets both gets its callback. A later call replaces the callback, which lives on the active container, so a callback installed underTestContainer::fake()stays in that test (EX-01, EX-02, EX-03, EX-06, EX-07). -
ssr:start,ssr:stopandssr:checkon the application binary, Laravel'sinertia:start-ssr,inertia:stop-ssrandinertia:check-ssr. They read the Inertia configuration the application installed, so they start, stop and check the worker first visits dispatch to; they run both bootstrap hooks, since the scaffold installs Inertia inhttp_bootstrap, bind no port and boot no runtime driver, and fail namingInertia::installwhen nothing is installed.ssr:start --runtimeoverridesInertiaConfig::ssr_runtime, and the command exits with the status its worker exited with (CM-01, CM-02, CM-03, SS-10). -
suprnova ssr:stop [--graceful], the CLI'sinertia:stop-ssr: it runs the application binary'sssr:stop(above) from the project directory, passing--gracefulthrough, so it stops the worker at the URL the application installed (CM-02). -
suprnova generate-typestypes wide integers asnumber | bigintin a project that preserves big integers. Withpreserve_big_integerson, ani64past 2^53 reaches the page as aBigInt, which anumbertype misnames, soi64,u64,i128,u128,isizeandusizearenumber | bigintwhen a.rsfile undersrc/callspreserve_big_integers(..)with anything but a literalfalse(parenthesized or not), such astrueor a variable, or with the new--big-integersflag, whichgenerate-typesandserveboth take andservekeeps for every regeneration on save, andnumberotherwise, as every integer and float was in 3.2.1. Narrower integers and floats staynumber, and a wide map key staysnumber(T03). -
suprnova generate-typeswrites page types and typesusePage(). In 3.2.1inertia-props.tsheld only the props interfaces, so a page picked its interface by hand and typed any shared props inline. The file now opens withimport '@inertiajs/core'and ends withPages, which maps each component to the struct a handler renders it with (read frominertia_response!,InertiaResponse::new(..).with_data(..)andInertia::data, given the struct itself or a local binding or parameter that declares or builds it, with Rust's shadowing applied),SharedProps(rootand the fields of the structInertia::share_datais given or marked#[inertia_props(shared)]),Errors,PageProps<C>, and adeclare module '@inertiajs/core'block settingsharedPageProps,errorValueTypeand, for a struct marked#[inertia_props(flash)],flashDataType, sousePage()is typed with no argument.ErrorsisRecord<string, string>anderrorValueTypeisstring, or both saystring[]when awith_all_errors(..)call undersrc/passes anything but a literalfalse(read aspreserve_big_integers(..)is), since the server then sends every message per field as an array. TheInertiaPropsderive takes the two markers and refuses any other form. A component rendered with two structs, two shared or two flash structs, or a struct named like a generated declaration fails the command with every conflict named and leaves the file as it was (T01, T02). -
A route helper names the page its route renders.
routes.tshelpers returned onlyurlandmethod, so<Link instant>and<Form instant>could not make an instant visit through one. A helper now carriescomponent, Inertia'sUrlMethodPair.component, when its handler names exactly one component as a string literal (ininertia_response!,InertiaResponse::newor theInertiafacade's render calls) or its route is aRouter::inertiaroute. A handler naming none, several, or one it computes gets none. A handler inside animplblock (#[handler(Self = Posts)], registered ascontrollers::posts::Posts::index) is read from its method like a free function, for its component and its request type, and a free function of the same name in the same file keeps its own.Router::inertiaroutes, whichroutes.tsleft out, now get helpers undercontrollers.inertia, andRouteConfigdeclarescomponent?: string(T05). -
suprnova::testing::TestClient, one in-process test client. Every HTTP test copied its own loopback harness - a port, a hyper client and hand-carried session cookies - becausehandle_requesttakes a body only hyper builds.TestClient::new(router, registry)sendsget,post,put,patch,deleteandsend(method, path)requests withheader,json,formandinertia()(an Inertia visit's headers with the installed asset version) over an in-memory connection, never a port, in the task that awaits it, so aTestContainerscope still applies. It carries every cookie a response sets to the next request and drops the ones a response expires, keeps each response's error report, gives everyTestResponsethe session storewith_session_storenames, and fails a request that has not answered after 10 seconds, naming its method and path. Under a public path prefix (APP_URL=https://example.test/billing) a page's url is the public/billing/userswhile the router matches/users, so the client keeps the root each request was served under and replays a reload to the internal path,/userswith the page's query, sending again theX-Forwarded-Prefixheader the page's request sent. See HTTP Tests (TS-01, TS-10). -
Laravel's prop assertions and scopes on
AssertableInertia. It hadhas,missing,where_andcountonly. It now hashas_all,has_any,missing_all,count_between,where_not,where_null,where_not_null,where_all,where_type(string,integer,double,boolean,arrayandnull, joined by|; an unknown name fails),where_all_typeandwhere_contains, andcountcounts an object as well.scope,first,each,has_withandhas_count_withrun a callback over a nested object or array whose failures name the full dotted path (user.name). A scope fails when it ends with a prop no assertion touched, unlessetc()was called in it; the page's top level never checks, as Laravel'sassertInertiadoes not (TS-06). -
Inertia reloads through the client, full and by deferred group. A reload needed a
with_reloadclosure wired to the test's own harness. A page from aTestClientresponse now reloads through that client with its cookies, andwith_reloadstill replaces it for a custom harness.reload()replays the page with no partial-reload header and asserts the same component, url and version;load_deferred_props_of(groups)requests the props of the named groups only, every group for an empty list, and fails naming a group the page does not defer instead of requesting nothing.reload_with,reload_only_with,reload_except_withandload_deferred_props_withrun a callback over the reloaded page (TS-07, TS-08). -
Inertia page readers, the flash a redirect leaves, and big integers in tests.
AssertableInertiagainsmissing_flash,to_page()(withencryptHistoryandclearHistoryonly when the page set them),encrypt_history()andclear_history(), andTestResponsegainsinertia_page()andinertia_props(path). A handler that flashes and redirects leaves its Inertia flash in the session, and the redirect carries no page to assert it on;assert_inertia_flash(key, expected)andassert_inertia_flash_missing(key)read it through the attached session store. A page withpreserveBigIntegerssends integers beyond 2^53 - 1 as{"$bigint": "<digits>"}markers, and the markers in props and flash are decoded before any assertion or reader sees them, sowhere_("id", 9007199254740993_i64)passes against the page the handler built. A marker whose digits fit no 64-bit integer, such as{"$bigint": "18446744073709551616"}, which only a hand-built page object carries, fails naming its path and digits rather than staying an object thatwhere_type("id", "integer")rejects andto_page()shows (TS-12, TS-13, TS-14, TS-15, TS-16). -
InertiaConfig::testing_ensure_pages_exist, on by default.AssertableInertia::component(name)passed for a component with no page file, so a test stayed green while the browser showed a blank page. With an Inertia configuration installed it now also looks for the file underpages_dirwith one ofpage_extensions, the lookupensure_pages_existdoes at render time, and fails withInertia page component file [Name] does not exist., the directory and the extensions it tried.component_exists(name, bool)decides the check for one assertion, and with no configuration installed nothing is checked (TS-03). -
Inertia DevTools records each request. The Inertia DevTools browser extension reads its entries from the server, and Suprnova had no server side, so the extension showed nothing.
InertiaConfig::devtoolstakes aDevToolsConfigwith Laravel's settings, read from the sameINERTIA_DEVTOOLS_ENABLED,_TTL_HOURS,_PRUNE_INTERVAL_SECONDS,_LIMITand_GATEvariables. The application opts in with.devtools(DevToolsConfig::new()), as a new project's bootstrap does. Withenabledunset, it records only whenAPP_ENVis set and nameslocal; an unsetAPP_ENV, which Laravel reads as production, records nothing.enabled(true)andenabled(false)decide outright.Inertia::installandInertia::middlewarethen putDevToolsMiddlewareoutermost in the Inertia stack, and it skips theexceptpaths (_inertia/devtools*and_suprnova/*by default). A failure while recording drops the entry and leaves the response as it was; a write failure is logged atwarnonce and pauses recording into that directory for 30 seconds. See Inertia DevTools (DT-01, DT-10). -
The entry of a request, its headers and the first-visit tag. Each recorded request stores Laravel's entry key for key: a ULID, the tab, batch and visit ids from the extension's headers, the timestamp, method, URL, status, redirect location and server time, the request type (
precognitionfirst, theninitialorhttp,deferred,poll,partial,prefetch,navigate), the request and response headers, the request body (an Inertia write's JSON or form input with uploads summarized, read up to the request body cap) and the response body (the page object, or text up to 256,000 bytes), the route with its handler's type name, and for a rendered page the component, its page file and the render call's file and line, whichInertiaResponse::new,inertia_response!,Inertia::paginate,Inertia::dataandRouter::inertiatake through#[track_caller]. The response carriesX-Inertia-Devtools-Id,-Parent-Out, and-Base-Pathunder a public root, and a first visit's200document carries the id in a<script data-inertia-devtools-id>tag before</body>(DT-02, DT-04, Precognition row 057). -
Prop kinds and their sources in DevTools entries. An entry lists each prop the client received with its kind in Laravel's order (
always,deferonly on the extension's deferred visit with its group,optional,merge,scroll,once),reset,once,mergeDirection,deepMergefor a deep merge or amatch_on, andrescued. A shared key names theInertia::share,share_many,share_dataorApp::inertia_share*call that shared it, and theInertiaConfig::hookscall for a hook share; a render prop names the line that gives its key. Deep paths without metadata are pruned, andpropValuesholds what the client received (DT-03). -
The DevTools entry endpoints.
GET /_inertia/devtools/entrieslists entries newest first, filtered bycomponent,type,exclude,offsetandlimit, andGET /_inertia/devtools/entries/{id}answers one entry, or404 {"message": "Not found."}. AnAPP_ENVnaming thelocalenvironment admits every request; elsewhere, an unsetAPP_ENVincluded, only the user the configured gate ability allows is admitted, else403 {"message": "Forbidden."}. An entry request reflashes the session, never becomes the previous URL, and is never recorded (DT-05, DT-06, DT-09). -
DevTools storage and redaction. Entries are one JSON file each under
storage_path("inertia-devtools"), listed newest first in_meta.json, pruned after 24 hours once the last prune is 300 seconds old, and kept to the newest 100 per browser tab. Before a write, the redaction keys (password,token,api_keyand seven more) and headers (cookie,authorizationand four more) become[REDACTED]in bodies, prop values, headers and URL query parameters, without regard to case, and a header value that is not text becomes[UNSERIALIZABLE](DT-07, DT-08). -
The scaffold's notes: a list, a page and a form over the signed-in user's own notes. A new application had nothing a kit page could scroll, open or write: its dashboard sent one eager prop and no handler paginated anything.
suprnova newnow writes acreate_notes_tablemigration and aNotemodel that belongs to a user (theUsermodel gainshas_manynotes), and three routes behind the dashboard's authentication:GET /noteslists the user's notes 10 at a time withcursor_paginatethroughInertia::paginate, filtered by thesearchquery parameter in title or body without regard to case, and sendssearchback;GET /notes/{id}shows one, and answers404for a note of another user;POST /notesvalidatestitle(1 to 255 characters) andbody(at most 10000), writes the note and flashes a toast. Every handler reads notes throughNote::owned_by, and none lists accounts (K12, K14). -
The scaffold's dashboard defers
statsand leavesrecent_notesoptional. The dashboard sends the user's note count and the notes written today as a deferredstats, and the user's five newest notes as an optionalrecent_notesthe page asks for when it scrolls them into view (K14). -
The signed-in user on every page of the scaffold. A layout had no way to name the signed-in user outside the dashboard. The scaffold now shares
auth, the signed-in user ornull, withApp::inertia_share_lazy, read from the request's session for each response that sends it, andSharedDatainsrc/props/shared.rs, marked#[inertia_props(shared)], addsauthto the generatedSharedProps(K12). -
A JSON handler for the display name.
POST /profile/nametakes{"name": ...}, saves it on the signed-in user, and answers200with{"user": {...}}, or422with the framework's validation body for an empty name or one over 255 characters, for the dashboard'suseHttpform (K21). -
Flashed toasts after every account action. Nothing a new application did told the user it worked: the server sends
page.flash, but the scaffold flashed nothing. AToastinsrc/props/flash.rsis now flashed undertoastafter sign-in, registration, a reset-link request, a password reset, email verification, a verification resend, sign-out and a saved note, and theFlashstruct beside it, marked#[inertia_props(flash)], makessuprnova generate-typestypepage.flash.toastas Inertia'sflashDataType(K17). -
Laravel's route names in the scaffold. The scaffold's routes carry the names Laravel's kits give them:
dashboard,notes.index,notes.show,notes.store,profile.name,login,register,password.request,password.email,password.reset,password.update,verification.notice,verification.send,verification.verifyandlogout(K12). -
The sources and the manual cite the Inertia.js client at 3.8.0. The framework's comments cited the client at 3.6.1 and 3.1.1, and the frontend chapter named 3.4.0. Each rule they cite was read again in the 3.8.0 client, and every citation names its 3.8.0 file and line; the frontend chapter and the CSRF chapter name 3.8.0, and the frontend chapter lists
@inertiajs/vite(K01). -
The Vue kit runs on Inertia 3.8 and its Vite plugin. The kit pinned
@inertiajs/vue3at^3.6.1, found its pages with a hand-writtenimport.meta.globin each entry, and passedcreateInertiaAppno title, no server head and no nonce. It now declares@inertiajs/vue3,@inertiajs/coreand@inertiajs/viteat^3.8.0, andvite.config.tsrunsinertia(). Both entries name their pages withpages: './pages'. The SSR entry is thecreateInertiaApp(..)statement the plugin wraps withcreateServer, sonpm run build:ssrstill writesfrontend/bootstrap/ssr/ssr.js. Because the kit declares the plugin,suprnova servewrites the hot file, and with SSR on, a first visit in development renders through the dev server's/__inertia_ssrwith no worker running. The browser entry passes atitlecallback that appends the application's name, the same name the server'sdefault_titleuses,serverHead: true, and the nonce from<meta property="csp-nonce">when the document has one.npm run check,npm run buildandnpm run build:ssrpass on a fresh scaffold (K01, K05, K18, K19). -
Vue kit pages navigate with
Link, title themselves withHead, and share two persistent layouts. Every page drew its own frame, reached other pages through<a href>, which reloads the whole document, and left the tab untitled. The kit now shipslayouts/AppLayout.vue(navigation, the flash toast and a heading) andlayouts/GuestLayout.vuefor the pages underauth/, applied through thelayoutoption so a layout stays mounted between two pages that share it. Both showcomponents/AccountLinks.vue, which reads the sharedauth.user: the name and a sign-outLinkthat posts as a button without keeping the page's state, or the sign-in and register links for a guest, so the home and error pages never offer a guest a sign-out. Every application link is aLinkbuilt fromroot, every page sets its title withHead, and the dashboard sets the layout's heading withsetLayoutProps, which the next page clears (K06, K07, K16). -
The Vue kit shows the flash toast. The server's
page.flashreached no kit page, so a sign-in, a sign-out or a saved note gave no feedback.components/FlashToast.vuerenderspage.flash.toast, typed by the generatedflashDataType, in both layouts, straight from the page, so it shows once, on the page it was flashed for (K17). -
The Vue kit's dashboard and notes pages use Inertia's client features. The dashboard rendered one eager prop and the kit had no list page, so a new application had nothing to copy for deferred, optional or scroll props.
Dashboard.vuenow rendersstatsinsideDeferredwith a fallback, polls it withusePoll(10000, { only: ['stats'] }), loadsrecent_noteswithWhenVisiblewhen it scrolls into view, and saves the display name throughuseHttpwith an optimistic update that a422reverts while showingerrors.name; a saved name reloads the sharedauthprop, so the layout shows it. The newNotes/Index.vuecreates a note withForm, remembers its search withuseRemember, lists the signed-in user's notes withInfiniteScroll, and opens one as an instant visit to the newNotes/Show.vuefrom a prefetchingLinkwhose page props keep the shared props,rootamong them. The five auth pages submit throughFormin place ofuseForm, readerrorsandprocessingfrom its slot, and keep the sign-in page's remember checkbox, sent as a boolean (K11, K12, K13, K14, K15, K21). -
Signed-route middleware.
ValidateSignaturelets a request with a valid signature reach the handler and answers a missing, wrong or expired one with403andInvalid signature., as Laravel'sInvalidSignatureExceptiondoes. Build it withValidateSignature::new()orValidateSignature::relative(ignore), or registerValidateSignature::from_alias_argsas thesignedalias, which readssigned:relative,utm_source. -
Signature checks that ignore added parameters.
ignore(names)on the middleware, the alias arguments,ValidateSignature::except(names)for the whole application,url::has_valid_signature_ignoringandverify_signature_ignoringleave the named query parameters, such as autm_sourcea mail client appends, out of the verified text.signatureandexpirescannot be ignored. -
The previous path.
url::previous_path(fallback)returns the path of the session's previous URL without its query, the public root or a trailing slash, as Laravel'surl()->previousPath()does. -
Secure URLs with segments.
url::secure_with(path, segments)appends each segment percent-encoded as one path segment and upgrades the URL tohttpslikeurl::secure. It is Laravel'surl()->secure($path, $parameters). -
Error reporting callbacks.
Exceptions::reportableruns your callback for every reported error, or only for errors that wrap the type its closure takes;.stop()keeps later callbacks and theframework errorlog line from running for an error that callback receives. -
Reporting an error you handle.
Exceptions::reportsends an error through your callbacks and then theframework errorlog line. -
Errors that end a job's retries.
Exceptions::dont_retry::<E>()andExceptions::dont_retry_whenname the errors that make the worker fail a queued job at once, whatever tries it has left;Exceptions::should_stop_retriesanswers for one error. -
Error types on the development error page. The page names the wrapped error's type, the
FrameworkErrorvariant, orpanicabove its headline, andErrorReport::type_namereturns the same name. -
Editor links on the development error page. With
APP_EDITORset, each frame's location links to its line in your editor: a Laravel editor name uses that editor's URL format, a value holding{file}is a template, and any other name opens<name>://open?file=...&line=.... -
Required while a condition holds.
RequiredIf::when(condition)takes aboolor a closure answering one, requires the field with the required message while it holds and passes the field otherwise, as Laravel'sRule::requiredIfdoes. -
Image dimensions on uploads.
Dimensions<D>reads an image's width and height from its header and refuses the file withvalidation-dimensionswhen it breaks themin_width,max_width,min_height,max_height,width,heightorratioaDimensionLimitstype sets, or when its size cannot be read. -
The IP address message.
#[validate(ip)]readsThe address field must be a valid IP address.in place of the generic failure message. -
Nested middleware names.
make:middleware Admin/EnsureRolewritessrc/middleware/admin/ensure_role.rsand declares each module on the way. -
Middleware tests.
make:middleware --testwrites a test undertests/that runs the middleware in front of a route throughTestClient. -
make:view.make:view admin.dashboard(oradmin/dashboard) writestemplates/admin/dashboard.htmland a#[suprnova::view]struct naming it insrc/views/admin/dashboard.rs, declares its modules, keeps existing files unless--forceis given, and with--testwrites a test that renders it. -
Nested Inertia pages.
make:inertia Admin/Userswritesfrontend/src/pages/Admin/UsersPage.<ext>,--forceoverwrites an existing page, and--testwrites a test that renders the page and checks its file. -
Trusted hosts. The
TrustHostsmiddleware answers400 Bad request.to a request whose host is invalid or matches none of your patterns.TrustHosts::new()trusts theAPP_URLhost and its subdomains,TrustHosts::at(patterns, subdomains)trusts the regular expressions you list, matched without regard to case, and the local environment trusts every host. -
CSRF tokens in JSON bodies.
CsrfMiddlewarereads a top-level string_tokenfrom a JSON body as it reads one from a form, ahead of theX-CSRF-TOKENandX-XSRF-TOKENheaders, with""and"0"counting as no value. -
Controller middleware. A
ResourceControllerlistsControllerMiddlewarevalues in itsmiddlewaremethod, and a module named byresource!in apub fn middleware(). Each runs on the actionsonlyandexceptscope it to, after the group's middleware, and a name no alias or group carries fails the registration. -
Resource middleware at registration.
ResourceRoutes::middlewareandResourceDef::middlewarescope aControllerMiddlewareto some actions, running before the controller's own list. -
Resources inside groups.
resource!is an item ofgroup!and takes the group's prefix, name prefix, middleware, session block and binding settings. -
Routes leave group middleware out.
without_middleware::<M>()andwithout_middleware_named(name)remove a middleware a route's group or its own registration gives it, by type or by alias; the global middleware still runs. -
route_has. Returns true only when every route name in a list is registered, as Laravel'sRoute::hasdoes. -
Encrypters with their own key.
Encrypter::new(key)encrypts and decrypts withencrypt_string_for,decrypt_string_for,encryptanddecryptunder the key you give it, and leavesCryptas it was. It writes the payloadCryptwrites, so a value either one wrote under a key opens with the other. -
Key generation that returns its error.
EncryptionKey::try_generateandCrypt::try_generate_keyreturn the refusal of the operating system random source as an error, whereEncryptionKey::generatepanics. -
Gate checks for the signed-in user.
Gate::inspect_currentandGate::none_currentcheck the user of the route's guard, the user#[authorize]checks. A guest reaches only the gates defined withdefine_optional, which receiveNone, and every other ability answers the default denial. -
After hooks that see the resource.
Gate::after_with_argumentsregisters an after hook that receives the resource with the user, the action and the running decision, and fills only an undecided result. -
GateEvaluatedevents. Every gate check dispatchesGateEvaluatedwith the user's type, the user's identifier when the check found the user itself, the action, the resource's type and the decision. -
Request guards that receive their provider.
Auth::via_request_with_providerhands the resolver the request and the user provider that the guard's configuration names. -
Rate-limiter hits with a default or a date.
RateLimiter::hit_for_minutecounts a hit in a 60-second window, as Laravel'shit($key)does, andRateLimiter::hit_untilcounts one in a window that ends at a given time; a time that has passed opens no window. -
Guest and user throttle limits.
throttle:10|60,1allows a guest 10 requests a minute and a signed-in user 60, as Laravel'sthrottlereads its first argument. -
Throttle counts that stop at the limit. The throttle middleware checks every limit before it counts a request, then counts each bucket with one conditional increment that leaves a full bucket's count where it was, so a request refused at either step is not counted in the bucket that refused it, and a concurrent burst admits at most the limit. Limits whose keys collide count under the keys the limiter returns, so two limits on one key share one bucket, the bucket
RateLimiter::attemptsreads. -
Conditional increments.
CacheStore::increment_if_belowandCache::increment_if_belowadd to a counter only while it is below a ceiling and answerConditionalIncrement::Incrementedwith the new value orConditionalIncrement::Unchangedwith the value as it stands. The in-memory and Redis stores compare and write in one atomic step; a custom store gets a default that reads and then increments.RateLimiter::increment_if_belowdoes the same for a rate-limiter bucket and opens its window asincrementdoes. -
Named hasher drivers.
hashing::extendregisters a driver under a name andHASH_DRIVERselects it, as Laravel'sHash::extenddoes; it refuses a built-in algorithm's name, a name registered before, and a registration after the first hash. -
ARGON_TIME. The hashing configuration reads Laravel'sARGON_TIMEas the Argon time whenHASH_TIMEis unset;HASH_TIMEstill wins. -
The verified gate redirects by route name.
EnsureEmailVerifiedMiddleware::redirect_to_route(name)resolves the route on each request; a name no route carries fails the request with a500whose error names it. -
Your own verification message.
MustVerifyEmail::send_email_verification_notificationsends the verification link, and a model overrides it to send its own message.EmailVerification::send_linkcalls it, andresendcalls it through the newUserProvider::send_email_verification_notification. The default sends the newVerifyEmailNotification, a mail notification throughNotifythat reads as the mail did, and needs no notification setup. -
Your own reset message.
CanResetPassword::send_password_reset_notificationsends the reset link on the provider path, through the newUserProvider::send_password_reset_notification; the default sendsPasswordResetMailtoemail_for_reset(). -
A timebox on reset links.
PasswordReset::send_linkholds every answer, a refusal and an error included, untilPASSWORD_RESET_TIMEBOX_MSmilliseconds (200 by default) have passed, so an unknown address answers no sooner than a known one. -
A rehash step in the sign-in.
UserProvider::rehash_password_if_requiredruns after the password validates and before the user is signed in, inattempt,onceandAuth::logout_other_devices. -
Attachments compared by content.
Attachment::is_equivalentandis_equivalent_withcompare the name, bytes and content type, andOutgoingMessage::has_equivalent_attachmentandhas_attached_datacheck a sent message with them;has_attachmentstill matches the name only. -
Raw data attachments on the builder.
MailBuilder::attach_data(bytes, name, content_type)attaches in-memory data, as Laravel'sattachDatadoes. -
A mailable's own recipients.
Mailable::to,cc,bccandreply_togive a mailable its own lists; a send or a queue merges them ahead of the builder's, skips an address already present, andMail::always_tostill replaces every recipient. -
Mailables sent alone.
Mail::send,Mail::queue,Mail::later,Mail::on_queueandMail::queue_onsend or queue a mailable to its own recipients and refuse one with none before anything is sent or pushed. -
Boolean mail fake checks.
MailFake::has_sent,has_sent_mailable::<M>()andhas_queuedanswer whether a mailable was sent or queued; a queued mailable does not count as sent. -
Mailable delays.
Mailable::delaydelaysMail::queueandMailBuilder::queue; an explicitlaterdelay wins. -
Notification delays per channel.
Notification::delay(channel)delays that channel's job whenNotify::queuepushes it. -
BroadcastNotificationCreated. The broadcast notification channel dispatches it with the notification's name, the route, the data and the message's queue and connection, after the publish or the push. -
Queued broadcast notifications. A notification that implements
NotificationBroadcast::to_broadcastand is registered withregister_broadcast_renderersupplies aBroadcastMessage; one that names a queue or a connection withon_queueoron_connectionis published by a queuedBroadcastNotificationJob, which the worker knows without registration. -
Notification mail attachments by path.
MailRendering::attach,attach_data,attach_pathandattach_manyattach files, the last two withAttachOptionsfor the name and content type; files are read at delivery, the content type follows the extension, and a file that cannot be read fails the delivery naming the path. -
Delayed queued listeners.
QueuedListener::delay(duration)anddelay_until(|event| ...)delay the listener's job, winning over the job's ownJob::delay. -
Per-connection after-commit.
QUEUE_<CONNECTION>_AFTER_COMMITandQueue::set_connection_after_commitgive a queue connection its own after-commit setting, whichQueue::connection_after_commitreads. -
A job's own after-commit choice.
Job::after_commit_choice()answersSome(true),Some(false)orNone, so a job can push ahead of the commit even when its connection orQUEUE_AFTER_COMMITwaits. -
A Pusher HTTP API client.
PusherClient::new(config, registry)andPusherBroadcastHub::client()query channels and presence users, publish a batch in one request, end a user's connections and send any other signedGET, with channel names through the registry's wire mapping and errors that never quote the secret or a signature. -
Marked console lines.
console::error,console::warnandconsole::infoprint one line markedERROR,WARNorINFO, on the standard error for the first two and the output for the third, styled on a terminal unlessNO_COLORis set and plain text in a test. -
Console verbosity flags. Every command accepts
-qor--quietand-vto-vvvbefore its name, and after it unless it takes raw arguments or declares a flag of that name itself.console::verbosity()reports the level,console::line_atandconsole::error_atwrite only at or above a level, and--quietsilences a command's lines while the error of a failed command still prints. -
Console prompts.
console::ask_with_default,console::secret,console::select,console::select_keyedandconsole::multiselectread one line each, from a terminal or a pipe;secretdoes not echo on a terminal and is never captured, and a menu refuses an answer that is no option by naming the options. -
Answers for menus in tests.
ConsoleTest::expects_choice(question, answer, options)answers a menu and fails the command when the menu offers other options. -
Progress bars.
console::Progressandconsole::progress(label, items, f)redraw a terminal line, and write one plain line such asSync 3/3where the output is not a terminal. -
Console forms.
console::form()chainstext,secret,confirmandselectsteps and returns every answer by name fromsubmit(). -
Up-front console test expectations.
ConsoleTest::expects_output(line)expects exact lines in order,expects_output_to_contain(text)anddoesnt_expect_output_to_contain(text)search one write at a time on both streams, andexpects_confirmation(question, answer)answers aconfirmwith yes or no. -
Exit codes of a command's own.
FrameworkError::exit(code)ends a console command withcode, printed and reported nowhere, andFrameworkError::exit_code()reads the code the console binary ends with;ConsoleRun::assert_exit_code(code)andassert_not_exit_code(code)assert it, and exit code0is a success. -
MaintenanceModeEnabled.downdispatches the event after it records maintenance mode, on a firstdownand on an update alike. -
Prerendered maintenance pages.
down --render <view>renders the Tera template atresources/views/<view>withretry_afterand serves the result; a template that cannot be read or rendered failsdownbefore maintenance mode starts. -
Retry dates.
down --retrytakes a date as well as seconds and sends it asRetry-Afterin the RFC 7231 form; a value that is neither is refused. -
Tasks limited to environments.
TaskBuilder::environmentskeeps a task to the named environments at every tick. -
Tasks in maintenance mode. While the application is down,
schedule:runandschedule:workskip every task that does not askTaskBuilder::even_in_maintenance_mode; a maintenance state that cannot be read counts as down. -
Day splicing on expressions.
CronExpression::with_days_of_weekreplaces the day-of-week field and keeps the others. -
Loaded migrations.
Application::load_migrations_from(list)adds a list thatmigrate,migrate:status,migrate:rollback,migrate:fresh,schema:dumpand the migration on boot run after the application's migrator, each migration name once. -
Registered migrations. A crate registers its own list with
suprnova::register_migrations!(owner, list), and every application that links the crate runs it. -
One list for two-factor migrations.
auth_flows::two_factor::migrations()returns the four two-factor migrations in order. -
Directories that may exist already.
DiskExt::ensure_directory_existscreates a directory unless it is there, and succeeds when it is. -
Upload URLs from your own callback.
Storage::build_temporary_upload_urls_using(disk, callback)answers the disk'stemporary_upload_urlfrom the callback, which receives the path and the lifetime, ahead of the disk's own presigning; a read-through disk and an S3 disk answer from it too. -
Asking a disk about upload URLs.
Storage::provides_temporary_upload_urlsanswers whether a disk has an upload URL callback or presigns writes. -
Faked processes keep their argument list. A recorded process keeps its arguments,
Nonefor a shell line, and its quoted command line;assert_ran_argsandassert_ran_command_linecompare them exactly, whileassert_rankeeps matching the arguments joined by spaces. -
One-side resizes.
Image::resize_width_onlyandresize_height_onlyset one side and keep the other at the size the image has at that point of the pipeline, on theoxideavandmagickdrivers alike. -
Custom transformations with settings.
register_transformation_withregisters a function that receives per-call settings of its own type, andImage::transform_with(name, settings)records a step that hands them to it. The image holds the settings and releases them with its last clone; a step whose settings are of another type fails the image with an error naming the transformation. -
HEAD requests.
Http::head(url)sendsHEAD. -
Global HTTP middleware and options.
Http::global_request_middleware,global_response_middlewareandglobal_optionsapply to every request created after them, andHttp::without_global_configurationcreates requests without any of them. Registered inside anHttp::fakescope they belong to that scope. -
Building the request URL.
RequestBuilder::base_urlgoes in front of a URL without a scheme,querymerges pairs into the URL's query, andurl_parametersexpands{name}placeholders with each value percent-encoded, so a value cannot add a path segment, a query or a host. -
Multipart uploads.
RequestBuilder::attach(name, contents, filename)sends the body asmultipart/form-data. -
A connect timeout per request.
RequestBuilder::connect_timeoutreplaces the shared client's 10 seconds for one request. -
HTTP stubs that stay.
Http::fake_urlanswers every request whose URL matches a pattern,Http::fake_usingasks a callback that may pass withNone, andHttp::fake_sequenceanswers in turn and then with itswhen_emptyresponse, each with aFakeResponse. -
Reading a recorded request.
RecordedRequest::header,has_header,is_json,is_formandis_multipartcompare header names without regard to case. -
Laravel's stray-request names.
Http::prevent_stray_requests(on)andHttp::preventing_stray_requests()move and read the switchfail_on_real_callsmoves, andHttp::allow_stray_requests(patterns)lets a request inside a fake that no stub answers reach the network when its URL matches. -
Vite tags for any page.
Vite::tags(entries),Vite::to_html()andInertiaConfig::vite_tags(entries)render the build manifest's scripts, stylesheets and preloads for any number of entry points, each file once and every stylesheet before the first script, under the public root; a missing manifest is an error that names its path, and a missing entry one that names the entry. -
Entry points beside
entry_point.InertiaConfig::entry_pointsadds entries, such as a stylesheet entry, that the Inertia document andVite::to_html()load with the main one. -
The hot file, readable.
InertiaConfig::hot_file,Vite::hot_file,Vite::is_running_hotandVite::dev_server_urlanswer the hot file's path, whether it exists and the dev server URL it holds; production never reads it. -
The document head.
Headresolves the title (with an inherited prefix or suffix), description, canonical URL and robots directives from the defaults, route groups and routes (with_head), run-time calls and error statuses (Head::errors), field by field;Head::render_htmlrenders the escaped tags andHead::to_arrayreturns them as data. -
The head on Inertia pages. Every Inertia response that a head layer sets something for shares the head as a
headprop of keyed tags, left out of partial reloads and renamed withHead::inertia; the first visit writes the tags once, deduplicated against the SSR head, andHead::inertia_globalsadds tags for the first visit only. -
Head metadata beyond the title. Open Graph values and media, X cards filled from the page, theme colors, application metadata and icons,
pwa, resource hints, locale alternates, feeds, pagination links, custom meta and link tags, and JSON-LD schemas with breadcrumb and FAQ builders. -
Precognition answers from any error bag.
Precognition::after_validation(&request, errors)answers a precognitive request with204or422, and passes an ordinary one or fails it with the ordinary validation error. -
The Precognition selection in hooks.
Precognition::should_validate(field)answers whether a precognitive request listed the field while a form request's, a data object's or a multipart form's after-validation hooks run. -
Fallible CSRF helpers.
try_csrf_token()andtry_csrf_field()return an error that names the missing session. -
Raw cookies.
Cookie::raw(name, value)writes its value without percent-encoding, and refuses a name that is not an RFC 6265 token or a value byte outside cookie-octet;Cookie::is_rawtells the two forms apart. -
Shared view data.
View::share,View::share_for_requestandView::sharedhand values to every checked view through Askama's runtime values; a value shared for one request never reaches another request, the render cache included. -
Inline Markdown.
Str::inline_markdownandMarkdownRenderer::render_inlinerender emphasis, code, links and line breaks with no paragraph around them, and keep block markers such as#as text;Str::markdownrenders a whole document as a string. -
Markdown input choices.
MarkdownRenderergainshtml_input(HtmlInput::Sanitize | Strip | Escape | Allow),allow_unsafe_linksandautolink; a renderer that calls none of them renders as before. -
Fluent strings.
Str::ofreturns aStringablethat chains theStrhelpers,markdownandinline_markdown, and converts to and fromString. -
Purpose-bound string encryption.
Stringable::encrypt,encrypt_for,decryptanddecrypt_forseal and open a value throughCryptunder aCryptPurpose. -
Descending sort.
Collection::sort_descordersOrditems from greatest to least and keeps equal items in their order. -
Ordered key maps.
Collection::map_with_keyscollects pairs into anIndexMapin the collection's order; a repeated key keeps its first position and its last value. -
Dates from text.
Date::parse,Date::parse_inandDate::raw_parseread RFC 3339, dates, date-times, Unix seconds and named relative forms such astomorrow 09:30,+2 daysandfirst day of next month, reading the framework clock, and refuse other text with aDateParseErrorthat names it. -
Priority list controls.
default_middleware_priority,set_middleware_priority,add_to_middleware_priority_beforeandadd_to_middleware_priority_afterread, replace and insert into the middleware priority list. -
Value pipelines.
Pipeline::of(value)sends any value through steps, withthrough,pipe,pipe_all,finally,within_transaction,thenandthen_return; a step is a function, an async closure, or a type that implementsPipelineStep. -
Appending several middleware. The HTTP
Pipeline::pipe_allappends middleware after thosethroughset. -
More catalog directories.
Lang::add_pathmerges a directory afterlang/andLang::add_fallback_pathone before it; the translator the framework binds at boot reads every directory registered before then. -
Namespaced translations.
Lang::add_namespacereads a package's catalogs asnamespace::key, overridden bylang/vendor/<namespace>/<locale>/; the browser catalog holds them asnamespace__key, and the starter kits't()encodes keys the same way. -
Translation sources.
Lang::loaderanswers the directories and namespaces the translator reads, andFluentTranslator::from_sourcesbuilds a translator from them. -
Bindings chosen by environment.
#[service]takesbind(Concrete, env = [...])entries; at boot the first entry whose pattern matches the environment is bound, andimplwhen none does. -
Renamed route parameters.
#[route_param("name")]on a handler argument reads the route parameter of that name, and an argument spelledr#typereadstype. -
Lazy singletons.
App::singleton_lazyandApp::singleton_lazy_if_absent, and the same onContainerandTestContainer, build a singleton on its first resolve and share it; a factory that resolves its own type gets an error. -
AI-assisted development chapter. The manual shows how an assistant reads it as Markdown and through
llms.txt, how to install the Suprnova language server, and how to point an assistant at a project. -
Configuration defaults that never overwrite.
Config::register_defaultregisters a value only when none of its type is registered and answers whether it did;Config::mergemerges a map of defaults under the registered one, the application's keys winning, throughMergeConfig. -
Environment detection that tells unset from named.
Environment::detect_explicitanswersNonewhenAPP_ENVis unset. -
Cache connections by name. With
CACHE_DRIVER=redisthe store runs its commands on the Redis connectionREDIS_CACHE_CONNECTIONnames,cacheby default, and its locks onREDIS_CACHE_LOCK_CONNECTION,defaultby default;CacheConfigBuilder::connectionandlock_connectionname them in code, andRedisCache::connect_namedbuilds the store on them. -
Moving the cache to another connection.
Cache::set_connectionmoves the bound Redis store's later commands to another named connection, and answers an error for a store without one. -
Cache hit and miss events.
Cache::get,hasandmissing, and every read built on them, dispatchCacheHitandCacheMissedwith the store's name and the key; a hit that fetched the value carries it, and itsDebugoutput leaves it out. -
A lifetime read from the cached value.
Cache::remember_with_ttltakes the lifetime of a computed value from a closure over it:Nonestores it for the configured default,Some(Duration::ZERO)returns it unstored. -
MySQL character set and collation. On a MySQL or MariaDB URL,
DatabaseConfigcarriescharsetandcollationfromDB_CHARSETandDB_COLLATION(utf8mb4andutf8mb4_unicode_ci), a URL parameter winning, and every connection sends them withSET NAMES. -
Table character set and collation.
Schema::creategives a new MySQL table the configured character set and collation, andBlueprint::charsetandBlueprint::collationname its own. -
The
Logfacade's level methods.Log::emergencythroughLog::debug, a*_withform of each andLog::logwrite to the default channel throughtracing, and a file or stack channel keeps their own level,CRITICALincluded. -
Logger context.
Logger::with_contextandwithout_contextreturn a logger whose writes carry a context, andLoggerhas a*_withform of every level. -
Shared log context.
Log::share_contextadds a context to every later write of the current request or job, withLog::shared_context,Log::without_contextandLog::flush_shared_context. -
Log listeners. Every write that reaches a channel dispatches
MessageLogged, andLog::listenregisters a callback for each write. -
Placeholders per channel.
LogChannel::replace_placeholders(false)keeps a channel's messages as templates, and a stack gives each channel its own form. -
Log level names.
LogLevel::parsereads the eight PSR-3 names andwarnandtrace, andLOG_LEVELaccepts the PSR-3 names. -
Test client default headers.
TestClient::with_headerandwith_headerssend headers on every request the client builds, a request's own header winning, andflush_headersclears them. -
QUERYrequests in tests.TestClient::query_jsonsends aQUERYrequest with a JSON body and the JSON content type and accept headers. -
Acting as a user in tests.
TestClient::acting_assigns a user into the default guard for every request, andacting_as_with_guardinto a named guard; an unregistered guard fails the request naming it. -
No-content assertions.
TestResponse::assert_no_contentpasses only for an empty204, andassert_no_content_statusfor an empty response of another status. -
Typed queued mailables in the mail fake.
MailFake::queued_of::<M>()andqueued_where::<M>(filter)rebuild queued mailables asM, andassert_queued_mailable::<M>andassert_not_queued_mailable::<M>assert on them; a payload that does not rebuild fails the call, and thetry_*forms return the error. -
Fallible typed pushes in the queue fake.
queue::testing::try_pushed::<J>()returns the decode error thatpushed::<J>()now panics with. -
Workers on the queue fake.
QueueFakeGuard::driver()returns a driver a worker reserves the recorded jobs from, andqueue::testing::reserved::<J>()andtry_reserved::<J>()return each reservation typed. -
Full-text search.
where_full_textandor_where_full_textonDB::tableand the model builder renderMATCH ... AGAINSTon MySQL and MariaDB andto_tsvector ... @@on Postgres, withFullTextOptionsfor the mode, the language and query expansion; SQLite returns an error. -
Full-text indexes.
Blueprint::full_textcreates aFULLTEXTindex on MySQL and MariaDB and aGINindex overto_tsvectoron Postgres, with.language(..), anddrop_full_textdrops it; SQLite refuses both. -
Tests on the configured database.
TestDatabase::refreshmigrates the databaseDATABASE_URLnames once per test process and holds each test in a transaction rolled back when the helper drops;refresh_lazilydoes the same on the first query. -
Migrations rolled back after a test.
TestDatabase::migrateruns the migrations onDATABASE_URL's database and rolls back the ones it ran when the helper drops. -
Seeding test databases.
TestDatabase::seedruns a named seeder andseed_rootthe root seeder before the test body. -
#[suprnova_test]database keys.refreshruns the test throughTestDatabase::refresh, andseedorseed = Pathseeds before the body. -
A Web Push endpoint allowlist. In 3.2.1,
EndpointPolicyofferedStrict, which refuses local and private destinations but passes any public host, andAllowAny, so a tampered subscription could still make the server POST to a public host of the attacker's choice.EndpointPolicy::Allowlisttakes anEndpointAllowlistof push-service origins,https://hostorhttps://host:port, where a leading*.label matches exactly one label, ashttps://*.notify.windows.comneeds. It runs everyStrictcheck and refuses an endpoint at any other origin before the host name is looked up, with the newWebPushError::OriginNotAllowed, which carries the origin and never the path of the endpoint and is not retryable.WebPushChannelsends under that policy, in place of its client's own, whenWEB_PUSH_ENDPOINT_ORIGINSnames one or more origins, and logs a refused endpoint as a subscription that cannot be used.WebPushChannel::newreads the variable and returns aResult: an entry that is not an origin fails it with an error that names the variable.WebPushClient::send_with_policysends under a policy other than the client's own, andEndpointPolicyis no longerCopy. The Web Push chapter lists the origins of the Firefox, Chrome, Safari and Edge push services.
Changed
-
Runtime threads have an 8 MiB stack.
#[suprnova::main]builds its Tokio runtime withthread_stack_sizeset to 8 MiB for the worker and blocking threads, the size Linux gives the main thread, in place of Tokio's 2 MiB default. In a debug build the frames the framework puts under a Live action (the server, the middleware, the session, the render cache and the Live engine) use about 1.75 MiB of a 2 MiB stack, so an action a little deeper, such as a password reset, overflowed it and aborted the server. The size is reserved address space; a thread uses memory only as its stack is touched. -
Typed factory counts.
countandtimesmakemakeandcreatereturn vectors while uncounted factories keep their single-model results. -
Laravel boolean storage. MySQL and SQLite boolean columns use
tinyint(1)and retain false and true when you read their rows. -
Default float precision. Float columns use 53 binary digits on MySQL and Postgres, with explicit precision available through the column modifier.
-
Whole-second zoned timestamps. Postgres uses
timestamp(0) with time zoneby default, and SQLite declaresdatetimefor zoned timestamp columns. -
Production seeding requires force.
db:seedreturns an error in production unless you pass--force;suprnova db:seed --forcepasses the flag through to the console binary. -
Console test assertions check every expectation.
ConsoleRun::assert_successfulfails on a prepared question the command did not ask and on every unmet output expectation, whichunmet_expectations()lists; a question the test did not expect failsassert_successful,assert_failedand the exit-code assertions, naming it, even when the command goes on, andunexpected_questions()lists it. -
The console binary ends with the command's exit code. A new project's
src/bin/console.rsends withExitCode::from(error.exit_code()); an existing project replacesErr(_) => ExitCode::FAILUREwith that arm to end with the code ofFrameworkError::exit. -
A wrong method answers 405. A request whose path a route of another method matches answers
405withAllowand Laravel's message in place of the 404, and anOPTIONSrequest answers200withAllow. Both run through the global middleware; a path no route matches keeps the 404 or the fallback. -
Collection metadata belongs to the collection. JSON:API collections keep their document metadata at the root without merging the first item's metadata.
-
Empty results have page one. Length-aware pagination reports one last page and includes its page-one link when there are no matching rows.
-
Model ordering follows timestamp declarations.
oldestandlatestuse the model's declared creation column, including renamed timestamps. -
Force destruction includes trashed rows.
force_destroyphysically removes matching soft-deleted rows and counts each existing key once. -
Model visibility applies to serde and appends. Array, JSON, and serde outputs share the hidden and visible lists, including appended accessors.
-
Storage::purgetakes the disk name. The zero-argumentpurge()that dropped every disk ispurge_all();purge(name)drops one disk and reports whether it was registered. -
Excerpts trim invisible characters. Cut ends now remove Laravel's invisible character set, including zero-width spaces, while preserving characters inside the excerpt.
-
Redis prefixes typed keys. Typed methods, scripts, blocking commands, and typed pipeline methods apply
REDIS_PREFIX, defaulting to the app name's slug followed by-database-. Raw commands retain their arguments. -
Redis events reach application listeners. Enabled command and failure events now dispatch through
EventFacade, alongside the existing Redis listeners. Pipeline and transaction commands stay outside these events. -
Daily logs keep seven files by default. The
dailychannel andLogChannel::dailykeep 7 files unlessLOG_DAILY_DAYSor.days(...)sets another count; 0 keeps every file. -
Syslog names the application. Datagrams use
APP_NAMEas the ident, withsuprnovawhen unset, and keep each record's facility and severity. -
Percentages round decimal ties half up. Percentages now round
0.12345at four fraction digits to0.1235%. -
Special number spellings. Number formats use
∞andNaNfor values without a finite decimal representation. -
File and disk responses answer byte ranges. A GET range receives
206with the selected bytes andContent-Range; an unsatisfiable range receives416. Responses advertiseAccept-Ranges: bytesand include the file's modification time asLast-Modified. -
Production browser failures show a minimal HTML view. With debug off, a browser's 5xx page shows its status without error details. Inertia visits keep the application error page and JSON clients keep their JSON response.
-
Debug frames show source and separate error traces. Application frames include nearby source lines when the file is readable. Each recorded source error has its own trace.
-
The implicit default disk is local. Without a default named in code or
FILESYSTEM_DISK,Storage::default_disk()returnslocalor an error naminglocalandFILESYSTEM_DISKwhen it is not registered. -
S3 accepts Laravel's AWS variables. Bucket, region, credentials, public URL, endpoint and path-style settings read the AWS names when their S3 names are unset. Each explicit S3 value wins.
-
Nullable-user policies authorize guests. A policy accepting
Option<&User>receivesNonefor a guest and decides whether the handler runs. Policies requiring a user keep the401response. -
Handler authorization accepts enum abilities. An enum variant implementing
Into<String>reaches the same async gate as a string ability. -
Merged validation hook errors. Real form and multipart requests run both after-validation hooks after field rules and return their combined errors.
-
Classic form validation redirects. A failed form that prefers HTML redirects back with errors and old text input flashed to the session.
-
Unsigned MySQL IDs by default.
id()andforeign_id()match Laravel's unsigned keys.unsigned_ids = falsekeeps signed IDs through#[suprnova::main]orSchema::set_unsigned_ids(false). -
Nullable default timestamps.
timestamps()creates nullablecreated_atandupdated_aton every database. The scaffold documents the schema defaults and carries the signed-ID opt-out and model cast setting commented out. -
Query conditions follow SQL precedence. Every
or_helper adds a flatOR, sowhere(a).or_where(b).where(c)isa OR b AND c. The grouped column helpers keep their parentheses, and model scopes still constrain the whole caller condition list. -
Null equality values compile to
IS NULL. Both builders rewrite a nullwhereoror_wherecomparison instead of binding it after=. -
Joined builders update and delete matching rows. Both builders preserve the join when writing the base table; model deletion still honors soft deletes. The model builder also exposes
updateanddelete. -
A clean model save skips the update. Dirtiness comes from the instance's original values in memory, and a clean save runs no update, where 3.2.1 ran the update and fired
UpdatingandUpdatedon every save.SavingandSavedstill fire, whileUpdatingandUpdatedfire only for a dirty save. -
Pivot sync returns the changed ids.
syncandsync_without_detachingreturnSyncChangeswith attached, detached and updated id lists instead of(). -
Pivot sync updates per-id columns. Both methods accept
(id, Attrs)records and update existing rows only when their supplied columns change. Unchanged rows keep their pivot columns and timestamps. -
Pivot filters constrain sync. Both methods honor
where_pivotand its companions for the current set, updates and detachments, leaving rows outside the filter untouched. -
Pivot sync touches a configured parent. A relation's
.touch_parent()or a related model's inverse touch declaration enables the parent timestamp update, in the same transaction as the pivot changes. -
Queue assertions filter unchained jobs.
assert_pushed_without_chaintakes a closure, so a matching job must also carry no chain. -
Queue counts and clearing accept a queue name. You can select one queue on every driver; SQS uses
SQS_QUEUEwhen you pass none. -
SQS accepts FIFO queues. Jobs carry a message group and deduplication ID, with
defaultand a payload digest as defaults, and sends omit delays. -
SQS overflow supports named cache stores.
SQS_OVERFLOW_STOREtakes precedence over the disk, and clearing keeps other queues' payloads. -
Processes remove inherited environment variables. Passing
Nonetoenvremoves the variable before starting the program. -
TTY processes require terminal input and output. An error names the redirected stream; a terminal process captures no output.
-
Process diagnostics quote command arguments. Results and errors use POSIX shell quoting while fake patterns keep the arguments joined by spaces.
-
Stopping a process accepts a signal. The default sends terminate and waits 10 seconds before killing the process and its descendants.
-
Process fake handlers accept closures. You can inspect the pending command, path, environment and input before returning a result.
-
Described process fakes replay mixed streams in order. Each described output or error output line ends with one newline.
-
Process run-count assertions default to once.
assert_ran_timeschecks one run;assert_ran_countaccepts an explicit count. -
Precognition requires the route middleware. A route must carry
Precognitivefor the header to count. Previously every form request answered the header; a route without the middleware now handles it as a real request. -
Inertia DevTools recording is opt-in. 3.2.1 had no Inertia DevTools. An application records requests and serves the entries endpoints only when it passes
.devtools(DevToolsConfig::new())to itsInertiaConfig; without the call nothing is recorded and no entries are served. The scaffold and dogfood application opt in. A configured instance records whenAPP_ENVnameslocal, or as itsenabled(..)says (DT-01). -
The starter keeps an existing notes table. The scaffold's notes migration, new in 4.0.0, checks for the table before creating it, like the users migration, so a project using an existing Laravel database keeps its own notes schema and rows (K21).
-
The built-in image driver's PNG, BMP and WebP codecs come from the eas4ai forks of
oxideav-png,oxideav-bmpandoxideav-webpwhile the upstream pull requests are open (OxideAV/oxideav-png #18 to #25, oxideav-bmp #11 to #17, oxideav-webp #35 to #43). The encoders copy less: a PNG is written into a buffer with room for the metadata added after it, so adding an orientation tag to a 512 x 512 noise PNG does not move its 1 MiB file a second time, and a BMP into a buffer reserved at the file's exact size; lossy WebP is encoded from the converted planes where they lie, and lossless WebP from the pixels, instead of from a copy of each. Lossless WebP chooses its transforms in one pass rather than by exhaustive search: a 1024 x 1024 photo encodes in about half a second instead of 47.8 s in a release build, and processing a 64 x 64 image to lossless WebP allocates 0.76 MB in all instead of 1.23 GB. Its files are at most 8.7 percent larger. The forks carry three fixes of their own, each offered upstream (oxideav-png #26, oxideav-bmp #18 and #19): a PNG is decoded without inflating itsiCCPprofile or XMP packet, whichoxideav-png0.1.11 and later inflated, up to 64 MiB each, beforeIMAGE_MAX_ALLOC_BYTEScould count them (a crafted profile held 118,213,096 bytes under a 4 MiB budget); a BMP is decoded without a copy of its embedded profile (5,242,912 bytes allocated for a 1024 x 1024 RGBA file with a 1 MiB profile, now 4,194,336); and a BMP with a profile is written by an encoder that borrows the profile. An RGBA PNG is also decoded without the second copy of its pixels the crate's RGBA entry made (1 MiB for a 512 x 512 image). The forks follow upstream master, which changes three kinds of output: an image decoded from a lossy WebP, whose colour conversionoxideav-webp0.3 corrected to within one level of libwebp's (pixels move by up to 16 levels); a PNG with more than 1 MiB of filtered data, whichoxideav-png0.1.12 deflates in 1 MiB pieces, so its bytes can differ (a 1024 x 1024 noise PNG is 4,196,716 bytes instead of 4,196,676); and lossless WebP with transparency, written in the simple lossless layout, its alpha declared in theVP8Lheader, rather than behind aVP8Xheader. -
The project file is
suprnova.toml, all lowercase.suprnova servereads its extra dev processes fromsuprnova.toml, andlive:addkeeps its records there. A project that holds aSuprnova.tomlmust rename it: until it does,serveandlive:addrefuse to run and name the rename. -
live:add --manifestinstalls only from a signed library tree. A third-party manifest now sits in a library tree, beside thelibrary.jsonthat names its namespace and key, and installs only with a valid signature. A manifest holds noversion, and the shipped components' manifests dropped theirs. Each component directory's.suprnova-installed.jsonnow keys its digests by the path from the project root, Rust files included;live:addreads a record in the earlier form and rewrites it. -
Scaffolds ignore
live:add's lock and journal. The.gitignoreof a new project lists/.suprnova-live.lockand/.suprnova-live-journal.json; add both lines to an existing project's. -
RouteBindingis the one binding trait, shaped like Laravel'sUrlRoutable:route_key_name,route_key,route_field,resolve_route_binding,resolve_child_route_bindingand their soft-deletable forms.AutoRouteBindingis a second name for it, and<T as AutoRouteBinding>::from_route_param(value)keeps working. A type that implemented the oldAutoRouteBindingby hand implementsRouteBindinginstead. The unusedroute_binding!macro and the oldRouteBindingtrait withparam_nameare gone. -
A
#[handler]inside animplblock names its type, as#[handler(Self = Posts)], so the startup checks can find it. Without it, such a handler is a compile error that names the fix. -
Some string-pair
route()calls need.as_str().route()andtry_route()take bound values as well as strings, so the forms that compiled only because the old slice parameter set the pairs' type or coerced them no longer do: a name or value whose type the parameter inferred (s.as_ref(),s.borrow(),Default::default()), one that reaches&strthrough more than one dereference or through a type of the application's own (&&&str,&Box<String>), a container of pairs reached the same way (&&&Vec<_>,&Box<Vec<_>>, aSmallVec), an array whose pairs mix&Stringand&strvalues, an array of more than 32 pairs holding&Stringvalues, androuteused as afn(&str, &[(&str, &str)])pointer. Write.as_str(),&*or.as_slice(), or a closure in place of the pointer. Every other string-pair call compiles as before. -
A dotted resource name nests.
Router::resource("users.posts", ...)registers/users/{user}/posts/{post}, as Laravel'sRoute::resourcedoes; it registered/users.posts/{users.post}. -
A route key that does not parse answers 404. A key that does not parse, or breaks a
unique_idkey's format, gets the body a missing row gets, naming the model and never the value. On 3.2.1 a key that did not parse answered 400 and repeated the value, and a key that broke aunique_idkey's format was looked up as given and answered 404. -
The bare
x::Modelform no longer binds a soft-deleted row of a soft-deleting#[model]'s table unless the route callswith_trashed(). -
Bound arguments are bound before every other argument, after the route's middleware, so a missing row answers 404 before a form request is validated, whatever the declaration order.
-
The router refuses a route it cannot run, at startup. A handler that reads a parameter its path does not declare, reads the request body twice, names a binding field that is not a parseable column of the bound model, scopes a child through a relation the parent does not declare, or uses a binder that cannot run is an error from the boot path. Two body readers were a compile error; they are now a startup error, except two
Requestarguments, still a compile error. -
URLs carry the public root. When
APP_URLhas a path or a trusted prefix arrives,route(),try_route,route_with_paramsandtry_route_with_paramsreturn the root in front, so an application whose own routes begin with itsAPP_URLpath gets that path twice. Signed URLs cover the root, so a link signed before an application gained a root stops verifying.url::currentandLiveAssetCatalog::urlinclude the root.RenderKeyInputhas a publicrootfield. -
Redirect::intendedignores a stored network-path reference. A stored intended URL that starts with//,/\or\, or that holds a control character, is ignored in favour of the fallback. Store an external destination as an absolute URL. -
Cookies follow the root.
SessionConfig.cookie_pathand the XSRF cookie path default to unset, which means the root of each request. When a request carries two cookies of one name, the framework reads the first. -
Images are upright and carry no metadata. Images are oriented by their EXIF tag on decode (
IMAGE_AUTO_ORIENT, on by default), and processed output keeps only the ICC profile under both drivers: EXIF and GPS, XMP, IPTC, comments, text chunks and date chunks are stripped. Rotation corners and flattened transparency are white in JPEG and GIF, not black, and GIF output is converted to sRGB. -
The image types changed shape.
TransformationandImageConfigare#[non_exhaustive]: build anImageConfigfromdefault()orfrom_env()and set its fields, and give a match onTransformationa wildcard arm.Transformation::Rotate(f32)isRotate { degrees, background }.Image::store(disk, path)is replaced bystore(directory, disk), which stores under a generated name and returns the path;store_as(directory, name, disk)takes a name. -
The shipped migrations upgrade an existing application in place.
failed_jobs,jobs,job_batchesandsessionsmove into Laravel's layouts, andnotifications,features,rolesandpermissionsinto the layouts above, with every row. A queued, delayed or reserved job runs once, a failed job keeps its id, a batch keeps its counts, and no user is signed out. Amigratethat stops part way resumes on the next run. The manual gives the migration that moves an earlier scaffold'susers. -
Workers check
failed_jobsbefore they start.run_workerreturnsResult<(), FrameworkError>. A worker whose failed-jobs store is the database store refuses to start on a table it cannot write, andqueue:workthen exits non-zero. Each failed job gets a freshuuid, and itsconnectionissuprnova:<connection>, so Laravel'squeue:retryrefuses it. -
Laravel's
$2y$hashes verify throughAuth::attemptand Magnetar for passwords of 72 bytes and longer, judged on their first 72 bytes as PHP does. -
Suprnova never writes
users.remember_token. The scaffold'sUserdropsupdate_remember_token, readsidasu64and its timestamps asOption<DateTime<Utc>>. -
The RBAC, feature and notification entities follow Laravel's layouts.
rbac::entity::RoleandPermissionhaveu64ids and nodisplay_name, and the earlier pivot entities are gone.FeatureRowandStoredNotificationtimestamps areOption. Thesession::driver::database::sessionsentity is gone. ThedownofCreateNotificationsTable,CreateFeaturesTableandCreateRbacTablesleaves the shared tables, so a rollback never drops rows Laravel wrote, and a new scaffold'susersandsessionsmigrations leave their table on rollback too. -
Schema-qualified table names. On Postgres,
Schema::create,table,drop,drop_if_existsandrenamereadschema.tableas that table in that schema, and a.becomes_in index and foreign key names. On MySQL and SQLite a qualified name is refused with an error naming it. -
The naive date-time casts read MySQL
TIMESTAMPcolumns. -
Password hashing runs under one process-wide limit.
hash_async,verify_async,hash_with_cost_asyncand Magnetar's sign-in hashing each took a blocking-pool thread with no limit, so a burst of sign-ins could hold up to Tokio's 512 blocking threads at once, and an Argon2id hash under the framework's defaults holds 64 MiB: up to 32 GiB. They now share one limit,HASH_MAX_CONCURRENCY, which defaults to the host's available parallelism; work past it waits as a task holding no thread, so a burst holds at most the limit times one hash's memory. A hash keeps its place under the limit until it returns, even when its caller stops waiting.0or a value that is not a whole number is refused when the hashing configuration loads; a blank value is the setting left unset. The two dummy hashes Magnetar's verifier warms as it is built run under the limit too, instead of inline on the runtime worker that installs the engines (#146). -
A WebSocket upgrade no longer waits behind the shutdown drain. The registry of WebSocket handler tasks sat behind an async lock that the shutdown drain held for up to its 5 s deadline, so an upgrade in flight waited out the whole drain before its handler was registered. The registry is now a synchronous lock held only to reap finished handlers and register a new one, and the drain takes the set out under it and waits holding no lock, still up to 5 s before it aborts what runs. A handler registered while the drain waits is waited for in its turn and aborted with the rest at the deadline; one registered after the drain has closed the registry is not started (#149).
-
A streamed file is one blocking task, not one per chunk. A file above 1 MiB, served by
HttpResponse::file,HttpResponse::downloadorStaticFiles, spawned a blocking-pool task for every 64 KiB chunk, so a 1 GiB download made 16,384 trips through the pool and queued behind every other blocking task at each one. One blocking task now reads the whole file in 256 KiB chunks and hands them to the response over a channel of four: one pool trip per file, a client that stops reading leaves at most five chunks read ahead, and a dropped response stops its reader. The bytes andContent-Lengthare unchanged, and a read error or a file that shrinks still ends the body short (#147). -
The in-memory rate limiter keeps answering while it sweeps. Its buckets sat behind one lock: every request locked the whole map and copied its key into a new
Stringeven when the key had a bucket, and the periodic sweep andpurge_inactiveheld that lock across the whole map, so each sweep stalled every throttled request for a time that grows with the number of keys an attacker can rotate. The buckets now sit in a sharded map: a request locks only its key's shard, a key that has a bucket allocates nothing, and the sweep locks one shard at a time. During a sweep over 200,000 buckets (about 45 ms), no request on another key completed before; about 4,800 do now. Acceptance, rejection and retry-after answers are unchanged, and no request fails with "rate limiter poisoned" any more, since the shard locks do not poison (#148). -
Prop::match_onreplaces the match fields on each call instead of adding to them, as Laravel'smatchOndoes..match_on("x").match_on("y")emittedmatchPropsOn: ["posts.x", "posts.y"]and now emits["posts.y"]; name several fields in one call with.match_on(["x", "y"]). -
untilon a once prop reads an integer as seconds from now, as Laravel'suntil(60)does, where it read an absolute timestamp in milliseconds:.until(60)emittedexpiresAt: 60and now emits the render time plus 60 seconds. Pass aDateTime<Utc>for a fixed deadline (chrono::DateTime::from_timestamp_millis(ms)).fresh()onPropandOnceOptionstakes abool: write.fresh(true). -
Scroll props merge under the wrapper
databy default, as Laravel'sInertia::scroll($value, $wrapper = 'data')does:.scroll("posts", metadata, paginator)emittedmergeProps: ["posts"]and now emits["posts.data"], where a paginator or resource keeps its rows..paginateandInertia::paginateship bare rows and still merge at the prop's root;Prop::scroll_at_root()does the same for any other bare list. A scroll prop'smatch_onpath is now relative to the prop, with no wrapper prefix:.match_on("data.id")onpostsemitsposts.data.id, where a wrapped prop used to prefix the wrapper itself and emitposts.data.data.id. A deferred scroll prop announces its bare key undermergePropson the visit that withholds it and{key}.{wrapper}when the data arrives, where a wrapped one announced{key}.{wrapper}on both. The manual's two divergence entries for these are gone. -
sharedPropslistserrors, and a setting turns the list off. Every response shares the validation errors, as Laravel's middleware does, sosharedPropsnow starts witherrors: a page with nothing else shared carries["errors"]where it carried nosharedProps, and after a failed formerrorsreaches the client's instant-visit carry with the other shared keys.InertiaConfig::expose_shared_props(false)leavessharedPropsout of the page object, Laravel'sinertia.expose_shared_prop_keys; it is on by default. -
suprnova newships a root template in place offrontend/index.html. The server never served that file: Vite builds from the entry module, and the first visit was the framework's own document, titledSuprnovaon every page. A new project hastemplates/app.html, declared asAppDocumentwith#[inertia_root]insrc/bootstrap.rs, which renders every first visit through it and sets the project's name as the default title. The Dockerfilesuprnova docker:initwrites copiestemplates/into the stage that compiles the application, since Askama reads templates at compile time; it copied onlycmd/andsrc/, so that build could not find a root template or a Live view. -
X-Inertiacounts as an Inertia visit for any value PHP reads as true. A request was an Inertia visit only whenX-Inertiawas exactlytrue, so a client sendingX-Inertia: 1received the HTML document where Laravel sends the JSON page object.Request::is_inertiaand theInertiaRequestExtdefault now read the header as PHP's boolean cast does: every value but an empty one and0is an Inertia visit, and JSON responses still carryX-Inertia: true. Every middleware that asksis_inertiafollows the same rule, and so does the development error page, which a visit sendingX-Inertia: 1now gets in place of a JSON error (HD-01). -
The Inertia asset version follows Laravel's order and is empty by default. With no Vite manifest to hash, the page carried the version
1.0; Laravel's carries an empty one. The version now resolves from the newInertiaConfig::asset_urlsetting when it is set (a hash of the URL, as Laravel'sapp.asset_url; it defaults to theASSET_URLenvironment variable, and the builder's value wins), else from the manifest's hash, else to the empty string. An explicit.version(...)or.version_with(...)still wins.MANIFEST_VERSION_FALLBACKstays exported, but no resolver returns it now, and a client that holds1.0from before the upgrade is bounced once (MW-11). -
The asset-version 409 names an absolute URL and the current version.
InertiaVersionMiddlewareanswered a stale InertiaGETwith a root-relativeX-Inertia-Location(/users?page=3) and no version, so the client forced a full reload even for a poll or a background prop load. The 409 now carries the request's absolute URL (http://example.test/users?page=3, scheme and host asRequest::scheme_and_http_hostreads them, a trusted proxy's forwarded host included) andX-Inertia-Versionwith the current version, as Laravel'sonVersionChangedoes. It still answers before the handler runs, and a visit by another method still passes through.InertiaResponse::version_conflict(url), the 409 a handler builds itself, now carriesX-Inertia-VersionwithInertia::get_version()too (MW-02, HD-10, R04). -
Partial reload headers are parsed as Laravel parses them.
X-Inertia-Partial-DataandX-Inertia-Partial-Exceptwere trimmed entry by entry, and an emptyX-Inertia-Partial-Datawas a list that matched nothing, so the client received no props at all. The lists are now split on,with empty segments dropped and nothing trimmed (a, bnamesaandb), and a header that names nothing counts as absent: an emptyX-Inertia-Partial-Datanow returns every propexceptallows, as Laravel's does.X-Inertia-ResetandX-Inertia-Except-Once-Propswere trimmed too and now follow the same rule (HD-03). -
Dotted partial-reload entries narrow literal values only, as Laravel's do.
only: ['users.name']narrowed every prop's resolved value, a resolver's and adefer,optional,mergeoronceprop's included, so the client received{"users": {"name": "Ada"}}where Laravel sends the wholeusers. Dottedonlyandexceptentries now walk literal values alone (a flag-free resolver under a dotted key counts, since Laravel calls it before the walk), and the walk is Laravel's: an entry whose path resolves to nothing yields[]instead of{}, a path walks into lists by index, and a scalar a deeper path reaches ships as it is instead of being dropped. The manual's divergence entry on narrowing is gone (PR-08, HD-04). -
Optional and deferred props resolve on an except-only partial reload. An
optionalordeferprop resolved on a partial reload only whenX-Inertia-Partial-Datanamed it, sorouter.reload({ except: ['stats'] })returned none of them where Laravel returns every one it does not exclude. They now resolve whenever their key passes the only and except lists, a reload withexceptalone or neither list included; a standard visit still leaves them out (PR-07, PT-01). -
mergeandonceinstructions follow Laravel's partial-reload rule. Anyonlyentry that selected a prop also sent its instructions, soonly: ['items.data']against a merge propitemstold the client to append a value it had asked for in part, and a.merge().once()prop the client already held still sent amergePropsentry beside itsoncePropsentry.mergePropsandoncePropsentries now ship only when anonlyentry names the prop or an ancestor of it, so a deeper entry sends the whole prop with no instruction, and a held once prop that is not deferred sends itsoncePropsentry alone. A scroll prop keeps itsscrollPropscursor in both cases (PR-12, PR-13). -
The Inertia page
urlcarries the query as Laravel normalises it.page.urlrepeated the query as the request sent it, so/s?b=2&a=1%20xstayed/s?b=2&a=1%20xwhere Laravel'sfullUrl()sends/s?a=1%20x&b=2, and the client's comparisons of page URLs differed between the two. The query is now parsed as PHP parses it, sorted by key and re-encoded per RFC 3986, as Symfony'sRequest::normalizeQueryStringdoes:+becomes%20, reserved characters stay percent-encoded (a=%2Fxstaysa=%2Fx), a bare key gains an=, a repeated key keeps its last value, anda[]=xbecomesa%5B0%5D=x. The version 409'sX-Inertia-Locationcarries the same query. Aurl_resolver's URL is left as it returns it (RS-07). -
An empty Inertia response redirects back as Laravel's does. An empty
200on an Inertia visit was answered with303to the session's previous URL or/, whatever the method, so aPOSTfrom/formwith no previous URL landed on/. It now goes to the same-originReferer, then the previous URL, then/, with302, and303only forPUT,PATCHandDELETE; a browser follows a302afterPOSTwith aGET, so the blanket303protected nothing (MW-03, R09). -
A redirect with a fragment keeps it on an Inertia visit. A redirect to
/page#sectionreached the client as a plain302, and the fragment was lost inside the XHR that followed it. It now arrives as409withX-Inertia-Redirect: /page#section, which the client visits with the fragment intact, except on a prefetch, whichX-Moz,PurposeorSec-Purpose: prefetchmarks (HD-12, HD-13, R06). -
Inertia visits record the previous URL. The session middleware skipped every Inertia visit, so after Inertia navigation
Redirect::backand a failed validation landed on the last page loaded in full. An InertiaGETthat matched a route now records its URL, unless it is a prefetch, a Precognition request or a partial reload of the component it rendered, and a browser prefetch no longer records one in the session middleware (MW-06, HD-13). -
errorsunderX-Inertia-Error-Bagtakes Laravel's shape. With the header, a visit with no session errors got{"<bag>": {}}and a sessiondefaultbag was dropped for{"<bag>": {}}. It is now{}with no errors,{"<bag>": <default bag>}with a default bag, and the named bags as they are otherwise (HD-08). -
Inertia flash data lives in the session until a page shows it.
App::flashkept its value in the request: a request that answered plain JSON lost it, and one that redirected twice dropped it at the second hop.App::flash,Inertia::flashandInertiaResponse::flashnow write the session entryinertia.flash_data, the next Inertia page emits it underpage.flashand removes it, and every redirect keeps it for one more request (RF-17, MW-05). -
clearHistoryandpreserveFragmentsurvive any number of redirects.App::clear_history()andRedirect::preserve_fragment()flashed a flag for one request, so a logout that redirected twice rendered the login page withoutclearHistory: trueand left the previous user's encrypted history readable. The flags are now the session entriesinertia.clear_historyandinertia.preserve_fragment, which last until a page emits them; a flag an earlier release flashed is still read (RF-08, RF-09). -
A dotted shared key nests when it is shared.
App::inertia_sharestoreduser.ageas a literal key and nested it at render, soshare("user", {"name": "A"}),share("user.age", 3), thenshare("user", {"name": "B"})rendered{"name": "B", "age": 3}. It now nests at share time as Laravel'sArr::setdoes, and renders{"name": "B"}(RF-02). -
SSR exclusion patterns match as Laravel's
ExcludesPathsdoes.ssr_excludematched the raw path with*stopping at/, soadmin/*copied from a Laravel app excluded nothing (/admin/usersstarts with a slash) and/admin/*missed/admin/users/edit. Slashes at either end of a pattern are now ignored,*matches any characters including/, the path is decoded first, and each pattern is also tried against the full URL;**keeps working (RF-12). -
InertiaResponse::locationanswers a hard navigation with a redirect. It always answered409+X-Inertia-Location, which a browser that did not sendX-Inertiacannot follow, so an OAuth or SSO bounce started outside the SPA dead-ended on a blank page. Under the Inertia middleware it now answers an Inertia visit with the409and anything else with a302Location, or theRedirectit was given, as Laravel's does, on every route the server dispatches, the Inertia middleware installed or not;location_for(&req, url)stays for code outside a dispatched request (RF-16).
-
A component's script can no longer replace a built-in. The
live:addscan, new in 4.0.0, refuses a write to a member of a built-in object or function (script-builtin):Object.keys = f,JSON.parse = f,Math.random = f, and a write to a member of a parameter given a built-in member, asfunction f(p) { p.call = g } f(Array.prototype.slice)would change thecallevery other script borrowsslicewith. It refuses such a write in every form it refuses a write to a prototype's member (=,??=,+=,++, a destructuring orforloop target,delete), named directly, through the global object (globalThis.Object.keys,window.JSON.parse), or through a name that holds one: a variable, a parameter's default, or a parameter a call of its function by name hands one. A member read under a built-in method's name from a value the script did not make ([].slice, an element'saddEventListener) counts as that method, and a method ofdocument,locationorhistorymay not be assigned. A built-in is refused where the scan stops following it: passed to anything but a function the script calls by name or a browser API that only calls it back, put in an array or object, written to a member, destructured, returned, thrown or exported. That also names the built-in inObject.defineProperty(Object, "keys", ...)andReflect.set(Math, "random", f), whose calls other checks refuse too. The parameter form through a prototype's member is refused asscript-prototype, as the variable form is. Calls, reads, comparisons,map(Number), constants such asNumber.MAX_SAFE_INTEGER, the page's own properties (document.title,location.hash) and writes to the script's own objects and functions stay admitted. Nineteen bypass fixtures pin it (script-builtin-alias,script-builtin-compound,script-builtin-default-parameter,script-builtin-define-property,script-builtin-delete,script-builtin-destructured,script-builtin-export,script-builtin-function-member,script-builtin-globalthis,script-builtin-handed-back,script-builtin-inherited-method,script-builtin-math-random,script-builtin-namespace-member,script-builtin-page-method,script-builtin-parameter,script-builtin-reflect-set,script-builtin-window,script-prototype-member-aliasandscript-prototype-member-parameter), and theown-membersaccepted fixture pins what stays admitted. A member read off a literal, an operator's result (-1,"a" + b), a constant that holds one, or a class that extends a built-in and does not declare that static is the built-in it inherits, whatever its name, so(0).toPrecision,"".anchor,[].copyWithinand/x/.compileare built-in methods though no list of the scan names them.call,applyandbind, through which every script borrows a built-in method, may be written only on a value the script made, which refuses(0).toPrecision.call = f,Math.random().toPrecision.call = fand an element'srequestFullscreen.call = f.getRootNode()on any node is the page, asownerDocumentis, sodocument.getRootNode().createElement = fis refused,Object(value)is the value, and a method of the page whose name is never ordinary data (62 of them, fromcreateElementandquerySelectortoaddEventListenerandpushState) may be assigned only on a value the script made, which also refuses it through aparentNode, an event'scurrentTarget, an array, a promise, a function that returnsdocument, andthisin a method the page calls as a listener. The windowwindow.openreturns is a global object too, sowindow.open("/x").JSON.parse = fis refused. Writingcallon a value the scan cannot trace (api.call = fon a parameter,this.state.call = c) is refused as well, since the scan cannot tell it from a built-in method's. Eighteen more bypass fixtures pin these cases (script-builtin-literal-number,script-builtin-literal-string,script-builtin-literal-template,script-builtin-literal-regexp,script-builtin-literal-array,script-builtin-literal-name,script-builtin-literal-held,script-builtin-class-static,script-builtin-borrowed-call,script-builtin-borrowed-call-element,script-builtin-root-node,script-builtin-root-node-this,script-builtin-object-of-page,script-builtin-page-method-held,script-builtin-page-method-parent-node,script-builtin-page-method-listener-this,script-builtin-opened-windowandscript-builtin-opened-window-name), and theordinary-writesaccepted fixture pins what an ordinary component still writes:textContent,value,classList,this.state.open,o.callon its own object. -
A handler panic reaches the Inertia error page. The panic boundary wraps the whole middleware chain, so a panic unwound past the error-page middleware: an Inertia visit to a panicking handler got the JSON
{"message":"Internal Server Error"}500and the client's "plain JSON response" modal, even witherror_pageset. The middleware now runs the chain inside it under the boundary's rule, so the same500, with the panic's error report, reaches the error callback, and witherror_page("Error")the visit gets theErrorpage at status500. An API client still gets the JSON500.Inertia::installnow registers the error-response middleware whatever the config says, where 3.2.1 registered it only whenerror_pagewas set, because the callback can be installed after it; with neither a callback nor anerror_pageit hands every request on and changes nothing. -
SSR is on by default, behind bundle detection.
SsrConfig::enableddefaulted tofalse, so an application had to opt in to SSR, where Laravel'sinertia.ssr.enabledistrue. It is nowtrue, with the worker athttp://127.0.0.1:13714, and whileensure_bundle_existsis on (the default) a first visit is sent to the worker only when a bundle is found atssr_bundle_pathor at one of the six conventional paths (frontend/bootstrap/ssr/ssr.js,app.js,ssr.mjsandapp.mjsthere, thenpublic/js/ssr.jsandpublic/js/app.js). An application without a bundle renders on the client as before and never contacts the worker; one with a bundle at a conventional path gets SSR without configuration. Turn SSR off withInertiaConfig::ssr_disabled(), and the check off withssr_ensure_bundle_exists(false)for a worker whose bundle this process cannot see (SS-03, SS-04). -
A missing SSR bundle is no longer logged. With a
bundle_pathset and no file there, every first visit wrote "SSR bundle not found" to stderr or theon_ssr_errorhook. With SSR on by default that would reach the log of every application without a bundle on every first visit, so the visit now renders on the client quietly, as Laravel's gateway returnsnull;ssr:startreports a missing bundle. Theon_ssr_errorhook is for worker failures, and underssr_throw_on_errorsuch a visit now fails with Laravel'sSsrExceptiontext, naming the component and, when the worker gave one, the source location:SSR render failed for component [Dashboard]: window is not defined at resources/js/Pages/Dashboard.vue:12:5(SS-04, SS-08). -
suprnova ssr:startmakes Laravel's checks before it starts a worker. It checked that one bundle path existed and then ranruntime bundlewhatever the application's SSR configuration said: it started a worker with SSR switched off, looked for no other bundle path, never checked the runtime, started a second worker beside a running one, and died of aSIGTERMthat left its worker running. It now runs the application binary'sssr:start, which reads the installed Inertia configuration: it finds the bundle as the SSR dispatch does (the configured path, then the six conventional paths, warning when the configured one is missing and a conventional one runs), refuses a runtime it cannot find whenssr_ensure_runtime_existsis set, asks the worker at the configured URL to shut down first and refuses to start while that worker is still running, forwards Ctrl-C andSIGTERMto the worker as the signal received (a second one kills it), and reports each line of the worker's stderr as an error (CM-01). -
suprnova ssr:checkasks the SSR gateway's health check. It probed/healthwith a client of its own, so its answer could differ from the health check the framework uses, and its messages and exit codes were its own (2 for a URL without a scheme). It now runs the application binary'sssr:check, which asks the installed SSR gateway's health check and prints Laravel's messages:Inertia SSR server is running.,Inertia SSR server is not running., orThe SSR gateway does not support health checks., exiting 0 or 1 (CM-03, SS-10). -
The CLI's
ssr:start,ssr:stopandssr:checkrun the application binary, and the CLI does not link the framework crate. The CLI read its own SSR settings from--bundle,--url,--timeout-msand theSUPRNOVA_SSR_URL,SUPRNOVA_SSR_RUNTIMEandSUPRNOVA_SSR_BUNDLEvariables, so it could start or check a worker other than the one the application's first visits dispatch to. Each command now runscargo run --bin <package> -- ssr:<command>from the project directory, assuprnova serveruns the backend, with--runtimeand--gracefulpassed through: the application's output reaches the CLI's stdout and stderr, and the CLI exits with its status, or 128 plus the signal number when a signal ended it. The application runs in a process group of its own, so a terminal's Ctrl-C reaches it once, through the CLI, which forwards eachSIGINTandSIGTERMit receives to the application and eachSIGHUP,SIGQUIT,SIGTSTPandSIGCONTto the application's process group, worker included, and stops with it at aSIGTSTP, so Ctrl-Z andfgstop and resume them together. The flags and the variables are gone: set the URL, the bundle, the runtime and the timeout withInertiaConfig::ssr,ssr_bundle_path,ssr_runtimeandssr_timeout. The CLI's manifest names the framework crate for its tests only, as in 3.2.1, since the application binary already has these commands (CM-01, CM-02, CM-03). -
The starter kits declare
@inertiajs/coreand readrootthrough the generated types. In 3.2.1 a kit reached@inertiajs/coreonly because its adapter depends on it and npm hoists it, and no page had arootprop. Each kit'spackage.jsonnow declares@inertiajs/coreat^3.8.0beside its adapter, the generatedinertia-props.tsaugments that package, and every kit page that builds URLs fromrootreads it with a bareusePage(), typed by the augmentation. TheErrorpage keeps its inline props, since no handler renders it with a struct. A project upgrading with its owndeclare module '@inertiajs/core'block, in a.ts,.tsx,.mtsor.ctsfile underfrontend/srcsuch asglobal.d.ts, keeps it:generate-typesandservethen writeinertia-props.tswithout the augmentation or itsimport '@inertiajs/core'and print a notice naming that file (serveonce, not on every save), since two augmentations merge key by key and fail the type check on any key they set to different types. Delete the hand-written block and regenerate to get the generated augmentation, withrootand the shared struct typed (T06). -
TestResponse::assert_inertia()reads a first visit. It refused any response withoutX-Inertia: true, so the HTML document a plainGETof a page route returns could only be asserted throughAssertableInertia::from_responseon anHttpResponse. It now reads the page from the document'sdata-pageelement as well, andassert_inertia_with(callback)runs a callback over the page and returns the response for chaining, as Laravel'sassertInertia(fn)does. Both entry points find that element by itstype="application/json"anddata-pageattributes in either order, with others between them or in single quotes, and skip the text of any other script. They looked for<script type="application/json" data-page="only, so the document of a server-rendered first visit, which Inertia 3.8'sbuildSSRBodywrites as<script data-page="app" type="application/json">, failed with "no Inertia page object" (TS-01). -
An image wildcard leaves SVG out. A
MimeTypeallowlist takestype/*wildcards, new in 4.0.0, and a wildcard admits every subtype of its type exceptimage/svg+xml, since an SVG document is markup that can run script, as Laravel'simagerule leaves SVG out unless asked. An SVG passes only when the allowlist namesimage/svg+xml, as in 3.2.1, whose entries matched the type exactly.text/*andapplication/*admit every subtype. -
hasand its kin read a polymorphic owner relation. On aMorphTo,has,or_has,has_count,doesnt_haveandor_doesnt_haverendered a probe that is always false, sohasmatched no row anddoesnt_havematched every row. They now ask every owner type the relation declares, as Laravel'shasroutes aMorphTotohasMorph($relation, ['*']): a row has its owner when its type names a declared owner whose table holds its key under that owner's scopes, anddoesnt_havekeeps every other row, a null type or a type no owner answers to included.has_countcompares the owner count, 0 or 1, with=,<>,!=,<,<=,>or>=and refuses any other operator.where_has::<R, _>,where_doesnt_haveand theiror_forms apply the closure to the owners ofR's type, aswhere_has_morphwith that one type does. -
url::currentis the absolute URL without the query. It returned the path and the query, such as/posts?page=2, where Laravel'scurrent()returns theAPP_URLorigin, the root and the path. It now does the same; useurl::fullfor the URL with its query. The framework's own redirects, the session's previous URL and signature verification still read the path and the query. -
Redirect::gueststores a page to come back to. It stored the request's own URL for every request, so a sign-in after aPOSTor a JSON call sent the browser back to a form submission or an API response. It now stores the request's own URL only for aGETthat does not expect JSON, and the session's previous URL for any other request. It never reads theReferer. -
Errors are reported through
Exceptions. A 5xx response, every failed attempt of a queued job, and a console command that returns an error now run your reportable callbacks before theframework errorlog line; a console command's error is logged as well as printed. -
The frame that created an error shows where. In a build without debug info, the development error page gives the innermost application frame the error's creation site as its location.
-
The numeric max message.
#[validate(range(max = 10))]readsmust not be greater than 10, Laravel's wording; a string'slength(max = ...)keeps its message. -
ImageFileaccepts Laravel's image types. It accepts JPEG, PNG, GIF, BMP, WebP, AVIF, HEIC and HEIF and refuses every other type, TIFF, PSD, ICO and JPEG XL included; an SVG passes only aMimeTypeallowlist that names it. -
Generated middleware passes the request on.
make:middlewarewrites ahandlethat returnsnext(request).await, as Laravel's stub does, in place of a body that printed request timing. -
CSRF checks every method but GET, HEAD and OPTIONS.
CsrfMiddlewarenow checksQUERYand extension methods such asPROPFINDas it checksPOST; aQUERYrequest without a token gets419. -
Regenerating the session issues a new CSRF token.
regenerate_session_id()sets a new CSRF token beside the new id, so a token read before the regeneration gets419after it. -
Request::ajax()compares exactly. It is true only forX-Requested-With: XMLHttpRequest, not for another spelling. -
Request::host()reads the host as Symfony does. It lowercases the host, strips only a numeric port, and returnsNonefor a host with a character no host has, sohttp_host(),scheme_and_http_host()andurl()never carry such a host. -
Deletion cookies follow the session configuration.
Cookie::forget,without_cookieandwithout_cookiestakePath,DomainandSameSitefromSESSION_PATH,SESSION_DOMAINandSESSION_SAME_SITE, so the deletion cookie matches the cookie it deletes; an explicit path or domain given toCookie::forget_withstill wins. -
Denial codes survive
authorize.GateResponse::authorizereturnsFrameworkError::Denialfor a denial built withwith_code, andFrameworkError::code()reads the code after?; a denial without a code maps as before. -
Rate-limiter keys are cleaned as Laravel cleans them.
RateLimiter::clean_rate_limiter_key, and every counter method through it, applies PHP'shtmlentitiesbefore it strips entity markers, socaféandcafecount in one bucket anda&bis stored asaab. -
Named limiters rename shared keys.
RateLimiter::limiterreturns a callback that gives each limit sharing a key with another limit of the same result its fallback key, andthrottle:<name>counts each limit under<name>:<key>from that result, so the middleware and a direct caller read the same buckets. -
One rate-limit header pair. The throttle middleware writes one
X-RateLimit-LimitandX-RateLimit-Remainingpair, the limit with the fewest attempts left, and none when the handler's response already carries an equal or lowerX-RateLimit-Remaining. -
Refused requests are not counted. A request the throttle middleware refuses leaves every bucket's count where it was; the decision still uses the atomic post-increment count.
-
throttle:60,1counts signed-in users by user. The inline throttle keys a signed-in user by the user's identifier and a guest by address, each per path, so one user cannot buy a fresh budget from another address. -
The verified gate answers each request.
EnsureEmailVerifiedMiddleware::redirect_toanswers a request that expects JSON with403Your email address is not verified., and sends any other request throughRedirect::guest, so the intended URL is stored andRedirect::intendedreturns the user after verification.new()still answers403to every caller. -
Verification refusals tell the two cases apart.
EmailVerification::verifyanswers403This action is unauthorized.for a live link of another account or one mailed to an address the account no longer has, and keeps400for an unknown, expired or used token. -
Verifying a verified account keeps its time.
verifyconsumes the token and returns the user ID without a new stamp and withoutEmailVerified. -
Checking a password writes nothing.
validate_credentialsonEloquentUserProviderandDatabaseUserProviderverifies the password and writes nothing, as in 3.2.1, soAuth::validateand a guard'svalidateleave the hash as it is. The sign-in (attempt,onceandAuth::logout_other_devices) rewrites an outdated hash, the one a database shared with Laravel needs included, throughUserProvider::rehash_password_if_required, and a rewrite that fails fails the sign-in. -
One attachment per name and bytes. A message drops an attachment whose name and bytes equal an earlier one's, from the mailable's
attachments()or the builder, on the send and the queued path; two attachments with one name and different bytes are both sent. -
Notification mail without a subject. An empty
MailRenderingsubject is sent as the notification's name in title case (InvoicePaidgivesInvoice Paid) instead of empty. -
Unique queued listeners take the lock. A
QueuedListenerwhose job declaresunique_idpushes throughQueue::push_unique, so a second event while the lock is held pushes nothing and dispatchesUniqueJobSkipped. -
The after-commit decision follows an order. A push waits for the commit by the first of its own override, the job's
after_commit_choice, the connection's setting andQUEUE_AFTER_COMMIT, forpush,push_uniqueandbulkalike, instead of the job'safter_commitorQUEUE_AFTER_COMMIT. -
downprints Laravel's lines. It printsMaintenance mode options updated.when the application was already down, the bypass address asYou may bypass maintenance mode via [<APP_URL>/<secret>]., andFailed to enter maintenance mode: <error>.on a failure. -
Single-server tasks need a cache store. A schedule with an
on_one_server()task and no cache store bound refuses to start in every environment, and a tick with no store skips the task with an error log instead of running it on every server. -
Day helpers keep the schedule.
days,weekdays,weekendsandsundaystosaturdaysreplace only the day-of-week field after a frequency, time orcroncall, so.hourly().mondays()is0 * * * 1; alone they still run at midnight. -
Hour-only and seconds times.
at,try_at,daily_atandtry_daily_atread9as 09:00 and09:30:00as 09:30. -
migrate:statusprints its list. It writes one line per migration withAppliedorPendingto the standard output, where it wrote them to the log. -
make_directorytakes a path without its trailing slash.make_directory("a/b")creates the directory as"a/b/"does; it used to fail on every disk. An empty path and a path that ends in/reach the backend unchanged. -
No image driver receives a zero side.
Image::resize,cover,resize_widthandresize_heightrecord a side of 0 as 1, as Laravel clamps it; themagickdriver failed on the0x0geometry. -
ImagePipelinecarries the settings of its custom steps. The newsettingsfield holds whatImage::transform_withrecorded, and a custom driver runs a custom step withCustomTransformation::apply_with(pixels, &pipeline.settings). A struct literal ofImagePipelineends with..ImagePipeline::default()or names the field. -
A started fake process reveals its output a line at a time. Each
output()orlatest_output()call reveals the next line,output()answering every line so far andlatest_output()the new one; the error output works the same way, andwait()still returns the whole output. -
The HTTP fake records a request as it is sent. The recorded headers include the
Content-Typea JSON, form or multipart body sets, the user agent, and the headers global middleware adds, and the recorded URL has its base URL, URL parameters and query applied. -
Development pages load an existing build when no hot file exists. In development the Vite tags point at the dev server only while the hot file exists, and at the manifest's files while it does not and a manifest exists. A frontend that declares no
@inertiajs/viteand holds a manifest from an earlier build now loads that build instead of the dev server: declare@inertiajs/vite, as every starter kit does, or delete the stale build. -
Database rules in hooks follow the Precognition selection.
AsyncRule::check_async,Exists::check_valueandExists::check_each(selected under<field>.*) skip a field a precognitive request did not list, so they neither query nor fail; errors a hook adds stay unfiltered. -
The CSRF field turns autocomplete off.
csrf_field()rendersautocomplete="off", so a browser does not restore a stale token into it. -
A default middleware priority. The priority list starts as
Precognitive,SessionMiddleware,AuthMiddlewareandThrottleRequestsMiddleware, so a route that listsAuthMiddlewarebeforeSessionMiddlewareloads the session first, and a route-listedPrecognitiveruns before a globalSessionMiddleware. -
lang/vendoris not a locale. The translator skips it as a locale directory; it holds overrides of namespaced catalogs. -
#[service(impl = ...)]parses. The named form beginning withimplwas refused as a keyword; it now registers the implementation. -
An unset
APP_ENVis production. A deployment that sets noAPP_ENVnow runs every production check: debug is off,APP_KEYis required, the SQLite fallback, a mail driver that delivers nothing, plaintext SMTP, the in-memory rate limiter, an unknown queue driver and the mock payment provider are refused, the Inertia shell needs its Vite manifest,on_one_servertasks need a shared cache, anddb:seed,migrate:freshandsuprnova migrate:freshask for--force. No.env.<environment>file loads for an unsetAPP_ENV;.env.localstill does. SetAPP_ENV=local(the scaffold's.envdoes) to keep the old behaviour. -
CacheConfiggainedconnectionandlock_connection. ACacheConfigstruct literal names both fields, or spreads..CacheConfig::default(). -
The Redis cache moves to the
cacheconnection andCACHE_PREFIX. The store runs on thecacheconnection's database (REDIS_CACHE_DB, 1 by default) and its keys areREDIS_PREFIX, thenCACHE_PREFIX(the slug ofAPP_NAMEand-cache-), then the key;REDIS_PREFIXno longer names the cache prefix, andCache::flushdeletes only keys under both prefixes. An upgraded deployment finds its Redis cache empty;REDIS_CACHE_CONNECTION=default, an emptyREDIS_PREFIXandCACHE_PREFIXset to the old prefix (suprnova_cache:by default) keep the old keys. -
MySQL tables default to
utf8mb4_unicode_ci. Tables created before the upgrade keep the server's default collation, and MySQL refuses to compare string columns of two collations; an application whose tables use the server's default keeps it by settingDB_COLLATIONto that collation (utf8mb4_0900_ai_cion MySQL 8). -
File and stream log channels keep
LOG_LEVEL's bare level.single,daily,monthly,stderr,errorlogandsyslogkeep only records at or above it,debugwhen it names none, and a bare level that is no level fails the boot. -
queue::testing::pushed::<J>()fails on a payload that does not decode. It panics, naming the job and the decode error, where 3.2.1 left the push out of the list, so neither the list,assert_pushednor the newassert_not_pushedpasses over a push it cannot read. -
Queue::reserved_jobsunderQueue::fake()answers the fake. It lists the reservations workers made from the fake instead of reading the installed driver. -
The server caps concurrent connections at 10000 by default. In 3.2.1 an unset or blank
SERVER_MAX_CONNECTIONSleft the number of concurrent connections unbounded, so a crowd of slow clients could use up the process's file descriptors. An unset or blank value now caps them at 10000, the newsuprnova::config::providers::DEFAULT_MAX_CONNECTIONS, andServerConfig::builder()andServer::newstart from the same cap. Zero or a value that does not parse still falls back to 10000 with a warning, and an explicit positive value is the cap. No value of the variable removes the cap: a server with no cap is a choice made in code, withServerConfig::builder().unbounded_connections(). A deployment that holds more than 10000 connections at once setsSERVER_MAX_CONNECTIONSto its figure. -
Zero tries is unlimited. In 3.2.1 a job whose
Job::max_tries()returned 0, or a push whoseEnvelopeOverrides::max_trieswasSome(0), reached the worker with no attempt to spend and was dead-lettered before it ran. Zero now means unlimited, as Laravel's$tries = 0and the worker's--tries=0do: the envelope of a pushed, batched or chained job and of a queued notification carriesu32::MAX, so the job is retried until it succeeds and is never dead-lettered for running out of attempts. An error named withdont_retryordont_retry_when, a middleware such asFailOnException, a timeout underfail_on_timeoutand a worker started with--triesstill end it.
Fixed
-
The full-stack Dockerfile copies the localization catalogs. The Dockerfile
docker:initwrites for a Svelte, React or Vue project copieslang/into the runtime image, which 3.2.1's left out, soLocalization::bootstrapfinds the catalogs the pages'langshare and__!lookups read. -
The Laravel parity map holds the Inertia adapter and client.
feature-map/laravel/surface.jsonlheld laravel/framework alone, so no Inertia protocol row (HD-01, MW-06, RF-16 and the rest) could name its Laravel side, and the row ids in these notes were the only link between a row and what shipped. The map now also holds inertia-laravel 3.5.1, read through the same PHP reflection, and Inertia.js 3.8.0, read with TypeScript's parser: classes, facade methods, macros, Blade directives, config keys, every package export and eachX-Inertia*header the client sends or reads, each record tagged with its package. The rows' parity decisions are infeature-map/laravel/inertia-protocol-parity.jsonlforfmap parity-import. -
The error callback sees the error responses from outside the Inertia stack. In 3.2.1,
InertiaConfig::error_pagedecided only what passed through the error-response middlewareInertia::installregisters. A middleware registered beforeinstallthat answers without callingnext-CsrfMiddleware's419,TimeoutMiddleware's503, an outer rate limiter's429- and a panic that only the server's boundary caught never reached it, so an Inertia visit got the plain-JSON modal for them. The server now runs the same decision after the whole stack, the panic boundary and the development error page, for every error response nothing inside the stack decided, at each of the three places it dispatches a request. A page decided there carries the shared registry and the shared providers, but no session data, no detected locale and none of the middleware hooks' shares, since every scope a middleware opened has closed. A JSON client's validation422,{message, errors}, was also kept from it: the error-response middleware sat inside the validation redirect and skipped every422with anerrorsobject so it would not replace an Inertia visit's before the redirect back. It now sits outside the redirect, which turns an Inertia visit's422into the303first, and the422exclusion is gone; the default callback still keeps every422. -
An error page placed outside the Inertia stack follows a fragment redirect. In 3.2.1, with
error_pageset,InertiaErrorPageMiddlewarepassed a response carryingX-Inertia-Locationthrough but not one carryingX-Inertia-Redirect: it read the empty body of the409thatInertiaResponse::redirectbuilds as an error and sent the error page in its place, so the client never followed the redirect. In 4.0.0 that409also carries an Inertia visit's redirect to a#fragment. Inertia protocol responses (X-Inertia,X-Inertia-Location,X-Inertia-Redirect) are never handed to an error callback now, the default one included, wherever the middleware is registered. -
A drop-in Inertia form with a file, and a
GETfilter form, read as the client shapes them. The Inertia client sends a form that holds a file asmultipart/form-dataunder bracketed and indexed names (user[name],photos[0]), and aGETvisit's data asfilters[status]=x&tags[]=a. A form request answered415for the multipart body, and every reader matched names literally, sofilters[status]=xarrived as one literal key and a field declared asuser.nameread nothing. Bracketed and indexed names in a url-encoded body, a multipart body and a query string now decode into nested data as PHP'sparse_strreads them: objects, lists in index order, up to 64 levels deep. A form request andRequest::inputread a multipart body, anUploadedFilefield takes a part that carries a file and runs its validators, and a field that fails is named by its dotted path (user.name,photos.1). A multipart body stays under the form request'smax_body_bytes(8 MiB by default) and the multipart part ceiling (1,000 parts). A multipart body a middleware read first, as a body-keyed rate limit does, is parsed from the buffer where the reader answered400naming a framework bug. -
JPEGs from the built-in driver show the right colours everywhere. The
oxideavdriver wrote RGB samples behind a JFIF header, so libjpeg-based decoders, ImageMagick and most browsers among them, showed the wrong colours. It now writes standard JFIF YCbCr. -
Redirects stay on the origin for a request-target that names another host.
Redirect::refresh_for,Redirect::guestandRedirect::intendedno longer send the browser elsewhere when a request such asGET //evil.example/xorGET /\evil.examplereaches a fallback route, andurl::fullstays on theAPP_URLorigin for it. -
Images are no longer copied on their way through a driver.
Image::from_byteshands the driver the caller's bytes, the built-in driver writes PNG and BMP from the pixels it holds, without the copies the codec registry's encoders made of every frame, and returns the buffer its encoder writes instead of a copy of it (when metadata needs more room than the encoder left, that buffer grows once), and themagickdriver writes an image to ImageMagick's standard input without copying it first and adds the metadata a source keeps (PNG colour chunks, an orientation tag) to ImageMagick's output without copying that either. An ICC profile split across a JPEG's or GIF's segments is read for its header and length where it stands, and joined once, only when the output carries it or converts from it; a WebP's or BMP's profile is carried without a copy, and a profile is written into the output once.IMAGE_MAX_ALLOC_BYTEScharges a profile for what is held: every inflate of a PNG's profile at its declared size, a check of its length included, the compressed copy PNG output makes, and the output's copy, but nothing for a profile that is dropped or lent without being inflated; a refusal names what it charged. Between twomagickruns an RGB profile goes on as the chunk ImageMagick wrote. -
Queue and failed-job table names with capitals or reserved words work. The jobs driver and the failed-jobs store quote each part of the configured table name, as the migrations do.
-
generate-typesreads{post:slug}as the parameterpostand no longer takes a leading bound argument for the form request. -
The Inertia CRUD tutorial compiles: its
inertia_response!calls pass the request, and its handlers bindTodo. -
Live upload and async routes follow the configured endpoint, and the header bar's default brand link carries the root.
-
Batch settlement counts work on MySQL against a
job_batchestable Laravel created:job_batch_settlements, new in 4.0.0, takes that table's collation, so a count never compares two collations. -
On Postgres, a session write for a guest binds
sessions.user_idas a NULL that thebigintoruuidcolumn of Laravel'ssessionslayout, new in 4.0.0, accepts. -
A component's scripts import by relative path only. The
live:addscan refuses a staticimportof an absolute path such as/acme-ui/x/x.js, even to the component's own script, as it refuses a URL (script-import), since an absolute path breaks when the application serves under a path prefix. The refusal says the specifier must be a relative path (./or../) to a script of the component or of a component it depends on. A relative path with one../more than the component is deep (../../../acme-ui/x/x.jsfromacme-ui/x/) is refused for the same reason: the browser resolves it outside the prefix. -
A component's script can no longer reach a built-in prototype through a computed key or a name. The
live:addscan refusesArray.prototype.map = ..., and alsoArray["prototype"].polluted = 1andconst p = Array.prototype; p.polluted = 1;, each of which adds a property to every array on the page. A script may read a member of a prototype (Array.prototype.slice.call(list)) but not keep or pass on the prototype: the scan refuses it in every position where it is a value (an initializer, an assignment, an argument, areturn, an array or object element, a default, a template substitution), under a computed key that traces toprototype, and fromgetPrototypeOf(script-prototype). A write to a prototype's member is refused in every form (=,??=,+=,++, a destructuring orforloop target,delete), as is a method called on the prototype itself (Array.prototype.push(1)), which runs with the prototype asthis, and destructuringprototypeout of an object (const { prototype: p } = Array). Twelve bypass fixtures pin it:script-prototype-computed,script-prototype-template-key,script-prototype-alias,script-prototype-argument,script-prototype-getprototypeof,script-prototype-parameter,script-prototype-destructured,script-prototype-compound,script-prototype-destructuring-target,script-prototype-delete,script-prototype-receiverandscript-prototype-destructured-key. -
A destructuring assignment's defaults, nested keys and shorthand targets are scanned. The
live:addscript scan walks every key and default of a destructuring target at any depth, as it walks any value, soeval, a prototype or any other refused expression is refused in the default of[a = eval("alert(1)")] = []or({ a = ... } = {})and in the keys of a nested target, and a nested or shorthand key gets the property checks a top-level key gets (({ constructor } = [])is refused asscript-eval). A shorthand target (uin({ u } = o)) is a target like any other: after it the scan does not traceuto the constant it held before, since the name holds a value the scan does not follow, and a name the script does not declare is a global write, so({ location } = { location: "javascript:alert(1)" })is refused (script-urlforlocation,script-globalotherwise). Four bypass fixtures pin it:script-destructuring-default-eval,script-prototype-assignment-default,script-destructuring-shorthand-urlandscript-destructuring-shorthand-global. -
The script scan follows a value by the names it was written with. To check a URL, a timer handler or a computed key, the
live:addscan follows a name to its initializer, its assignments and the arguments of its function's calls, and each name in a followed value names the binding it had where it is written, not a name that shadows it where the value is used. Soconst y = "https://evil.example/x"; const x = y;followed byfunction show() { const y = "/ok"; img.src = x; }is refused (script-url), a timer cannot be handed a string that way, and a constant shadowed by a remote URL where it is used is not refused. Thescript-trace-shadowed-initializerfixture pins it. -
The script scan sees the global object through an expression. The
live:addscan refuseswindow.localStorage, a global it does not admit, and its rules about the global object's members see through a sequence's last expression, a conditional's branches, a logical expression's sides and an assignment's value. So(0, window).localStorage,(0, self)["localStorage"]and(0, globalThis).fetch = f, which would replace a browser API, are refused as the bare form is (script-global), and(flag ? window : self).localStorageand(w || globalThis).localStoragenamelocalStoragein their refusal. A write through such an expression does not make a global of the script's own. Thescript-global-sequencefixture pins it. -
Writing a browser global no longer unlocks reading it. A name a script writes on the global object does not become a global of its own that it could read back. So
try { window.localStorage = 1 } catch {}, whose write throws into acatchthat swallows it, does not makewindow.localStoragereadable: the read, which would return the browser's storage, stays refused, and thelive:addscan refuses the write too. Thescript-global-write-unlocks-readfixture pins it. -
Magnetar's API documentation builds without the
two-factorfeature. The doc comments onLockoutFields::IDENTITY_IS_EMAILandLockoutService::without_user_locklinkedtwo_factor::lockout_identity, which exists only with that feature, so rustdoc failed on two broken links under Magnetar's default features. They now name it as text, with the feature that provides it. -
API documentation writes ranges in words. The docs of
PhoneNumber::new,PaymentMethod::Card'sexp_month,Batch::progressandSseEvent::keep_alivewrote their ranges with an en dash; they now read "8 to 15", "1 to 12", "0 to 100" and "15 to 30 seconds". -
A prop holding
<!--<script>no longer breaks the first Inertia page. The first visit's page JSON escaped/but left<and>raw inside its<script>element, so a prop such as<!--<script>put the HTML tokenizer into its escaped script state: the real</script>no longer closed the element, the mount element<div id="app">became script text, and jsdom found no#appand a page JSON it could not parse.<and>are now written as\u003cand\u003ebeside the/escaping, in the same single buffer, as Laravel'sJSON_HEX_TAGand Inertia 3.7.1 do (JE-01, H02). -
An Inertia page that cannot be encoded answers an error. A failure to encode the page object answered
200with{}as the page, as JSON for an Inertia visit and inside the first visit's document, so the client mounted an empty page. It now answers500throughFrameworkError, as Laravel'sJsonResponsethrows (JE-03). Encoding aserde_json::Valuepage does not fail today, so this closes a path rather than one seen in use. -
An empty SSR answer renders on the client. A worker answer of
{}, or an object without abody, was inlined as an empty body, so the first visit's document had neither the page data element nor the mount element and the client could not start. An answer whose JSON is empty,null,falseor not an object, that has no non-emptybodystring, or that is not JSON at all, now renders on the client from the page data, as Laravel returnsnullfor it, and is not reported as a failure (SS-02). -
SSR workers at
httpsURLs are reached. The SSR client was hyper's plain-HTTP connector, which refused anhttpsURL, so a worker behind TLS was never contacted and every first visit fell back to the client. The client now speaks TLS through rustls, the stack the HTTP client facade uses, and keeps the 5 second whole-call timeout over headers and body, the 8 MiB response cap and the refusal of an oversizedContent-Length(SS-14). -
DevTools redacts a flattened key by its parts. A multipart field keeps its flat name, so
user[password]=hunter2is stored under that name, and a dotted prop path such asauth.passwordkeeps its ownpropValuesleaf beside the nested page value. A key is sensitive when the whole name, or any part of it split on[,]and., names a redaction key, at any depth of the entry and in query parameter names alike, so both values are redacted; a longer word such aspasswordsis kept (DT-07, DT-08). -
DevTools redacts the URLs in headers and bodies. The query of every string that is a URL (it holds a
?and starts with a scheme,/or?) is redacted wherever the entry holds it, not only under aurlorredirectLocationkey, so a response'sLocation: /reset?token=abcandX-Inertia-Location, a request'sReferer, and aredirect_tofield carrying?token=never reach the entry file as sent. In both header bags so is the whole value ofLocation,X-Inertia-Location,RefererandContent-Location, each<...>target of aLinkand the target of aRefresh; a header that is not a URL is stored as sent (DT-07, DT-08). -
A lost DevTools index no longer drops the entries it listed. The index,
_meta.json, is rebuilt from the entry files whenever it is missing, empty or not a JSON list, before a rewrite as well as a read, so the older entry files stay in the list and under the 24-hour prune and the per-tab limit. Each rewrite writes a new file and renames it over_meta.jsonunder a lock on_meta.lock, so an interruption leaves the previous index in place, never an empty one (DT-07, DT-08). -
A commented-out augmentation no longer hides the generated one.
generate-typesandserveread a project's files as TypeScript tokens when they look for its owndeclare module '@inertiajs/core', with//and/* */comments and the text of'...',"..."and template literals set aside, so only a declaration in code counts. Afrontend/src/global.d.tsholding only// declare module '@inertiajs/core' {}keeps the generated augmentation and itsimport, and a comment betweendeclare,moduleand the name hides no real one (T02). -
A DevTools entry and
Request::route_namename the route that matched by its method. The router kept one process-wide table from name to pattern, and a request's name was looked up by its pattern alone, soGET /usersnamedusers.indexandPOST /usersnamedusers.storeboth reported whichever name the table listed first, and an unnamedPUT /usersreported one of them too. The router now records each name against the method and pattern it was given for, through.name(..), a route group's names and a resource's names, and the server sets the matched route's name on the request, so each method reports its own and an unnamed one reports none. A request that never went through dispatch still falls back to the pattern lookup (DT-04).MatchedRoute::name, which aRouter::bindresolver reads, reports the name the request carries too. -
A hook-shared prop names a file and line.
InertiaConfig::hookstakes its caller's location through#[track_caller], and every key the middleware hooks'sharesupplies names that call's file and line as itsshareSource, a place the extension can open (DT-03). -
A page whose document fails is recorded as the error the client got. The render hands DevTools its page only once the response is built, after the JSON encoding, the SSR dispatch and the root template. When any of those steps fails, the entry records the
500the client got and its body as a response with no page, nocomponentand no prop values, never the page object orpropValuesthe client did not receive (DT-03, DT-04). -
Every render prop has a
renderSource. A render prop's source is the line below the render call that names its key. When no such line exists, as for a page rendered withInertiaResponse::new("Home").with_data(props)whose struct is defined in another file, or in a deployment without its Rust sources, the prop names the render call's own file and line (DT-03). -
DevTools reads a request body as the handler would. The recorder reads a request body up to the request body cap (8 MiB by default), with or without a declared length, so a long or chunked body is recorded; PAR-072 allows an omission for the response body only. A body over the cap records
too-largeand reaches the handler whole: unread when its length is declared, else as the bytes read and the rest of the stream, the newBodyState::Partial. A failed read recordsunreadableand leaves its error in the newBodyState::Failed, which the handler meets only when it reads the body (DT-02, DT-10). -
A DevTools JSON request body is recorded whatever it parses to. A parsed JSON body is present in the entry whatever its value,
{},[]andnullincluded, one that does not parse is kept as its text, and only a body of 0 bytes isempty(DT-02). -
DevTools no longer reads an upload before its authorization. The recorder does not read a multipart body itself: the multipart extractor hands DevTools a summary of what it parsed, after
MultipartRequestHooks::authorizehas passed the upload. An upload no extractor read recordsnot-read, and one whose parse failed, such as one without its closing boundary, recordsunparsed, both with the declared length assize; the raw text, which redaction does not look into, is never stored. A name sent more than once, or one that ends in[], is the list of its parts, so all three files of aphotos[]field are recorded (DT-02, DT-10). -
The DevTools id tag finds a closing body tag in any case. The tag goes before the closing body tag, found in any case and with space before its
>, so a first visit whose root template closes with</BODY>or</Body >carries it, and a document with none gets the tag at its end (DT-02). -
A tagged first visit no longer carries the untagged page's length. A
Content-Lengththe handler set on its page is dropped when the tag is added, and the server sends the tagged document's length, since the untagged length on the longer document breaks the HTTP/1 framing in a release build and fails hyper's assertion in a debug build (DT-02, DT-10). -
A console command whose boot fails is reported. A failure before the handler runs reaches
Exceptions::report: a bootstrap that panics, asDB::init().await.expect(..)panics when the database does not answer, and a framework boot that returns an error, such as a log channel nothing defines. The console dispatcher and the application binary's commands catch a panic in the bootstrap, report the failure, so the callbacks the bootstrap registered before it failed see it, and then print it and stop the supervisors, as Laravel's console kernel reports a failure of its bootstrap. The application binary's commands report their own errors as the console's do; a silent error is not reported (PAR-111). -
schedule:interruptboots the cache it writes its mark to. The command, new in 4.0.0, boots the storeCACHE_DRIVERnames, after the MongoDB connections withdatabase-mongodb, and keeps a store the bootstrap bound, so it writes its mark in a real process whose bootstrap binds no store (PAR-089). -
A queue driver installed in the bootstrap survives the boot. The server and the worker commands ran
queue::bootstrap_from_envafter the application's bootstrap, and it replaced the driverQueue::set_driverhad installed with the oneQUEUE_DRIVERnames, so the manual's failover example did not hold.bootstrap_from_envnow keeps a driver the application installed and does not readQUEUE_DRIVERthen; it still registers theQUEUE_CONNECTIONSentries beside it, and still replaces a driver an earlier call installed. A test that boots the queue from the environment empties the slot first with the newqueue::testing::forget_driver(PAR-017). -
Every Live engine type a public signature names is named through
suprnova.live::testing::request_cancellation_for_testreturned the Live engine's cancellation flag,AdjustableTestClockimplemented the engine's clock trait with its clock error, andStitchSlotDescriptor,LiveNestedSegment::into_segment, the RenderCache stores, lease stores and instance record stores named engine typessuprnovadid not re-export, so an application could not write those types down.suprnova::livenow re-exportsClock,ClockError,ClockErrorKind,CancellationFlag,BuildId,ComponentName,ContentDigest,IslandSlot,RouteIdentity,DocumentMountKeyandMountedDocumentPath, andsuprnova::live::ledgerthe instance record store contract (InstanceRecordStore,InstanceRecordKey,PromotionRecordKey,StoredRecord,CasOutcome,LedgerError,LedgerErrorKind).suprnova::render_cachere-exportsRenderCacheError,RenderCacheErrorKind,RenderKey,Segment,ShellIsland,SlotFailurePolicy,AuthorizationConsult,GenerationLedger,GenerationSet,LeaseStoreandLeaseAttempt, andsuprnova::render_cache::storethe L1 store contract (RenderStore,PublicationFence,PublishOutcome,StoreInspection,StoredEntry). -
The Inertia DevTools gate's
GateEvaluatedevent names the signed-in user. The DevTools entry endpoints check their gate with the user asGate::inspect_currentand#[authorize]do, so the event carries the user's own type name and identifier, for a user type that registered no gate or hook too. -
where_relationon aMorphTorelation matches the owners.where_relation,where_relation_opandor_where_relationon a polymorphic owner relation built the generic probe, which has no table to read, so they matched no row. They now go through the morph engine, ashasandwhere_hasdo: the condition runs against every owner type the relation declares, under each owner's own scopes, as Laravel'swhereRelationreacheshasMorphthroughwhereHas(PAR-121). -
cursor_paginatekeeps the query's order. It replaced every ordering with the primary key, ascending, so a newest-first query such aslatest()came back oldest first. Every ordering is now kept and carried in the cursor: a descending order walks downward, the primary key breaks ties, and a query with no order still walks the primary key ascending. An ordering the cursor cannot carry, such asorder_by_rawalone, fails with a 400 error instead of being dropped, and so does an ordering on a joined table's column, such asowners.id. In a joined query the primary key that breaks ties names the model's table, and the query quotes the columns it orders by, as it quotes its other references to the model's table, so an ordering on a table whose name has capitals works on Postgres (PAR-080). -
#[model(timestamps = true)]without the columns fails the build. An explicittimestamps = true, or the baretimestampsflag, on a struct with neithercreated_atnorupdated_atwas accepted and managed no timestamps. It is now a compile error that names both columns, as#[suprnova::document]reports it. The default andtimestamps = falsecompile as before (PAR-183). -
An Inertia visit the fallback route answers records the previous URL. An Inertia
GETthe fallback answered left the session's previous URL where it was, where Laravel'sshouldStoreCurrentUrlreads a fallback route as a matched route. The fallback route's request now carries a fallback mark,Request::is_fallback_route, which the Inertia middleware reads beside the route pattern when it records a visit; the request still has no route pattern and no route name, so RenderCache, the debug page and DevTools see no routed match (PAR-048). -
Request::full_urlandurl::fullnormalise their query as Laravel'sfullUrldoes. They returned the query as it arrived, where Laravel'sfullUrl()andurl()->full()sort the pairs by key and re-encode them per RFC 3986 through Symfony'snormalizeQueryString:/s?b=2&a=1is now/s?a=1&b=2, and a query that normalises to nothing leaves no?.full_url_is, the SSR exclusion patterns, theInertiaVisita hook receives and the DevTools entry URL read the normalised URL, as Laravel's do. The previous URL a page load or an Inertia visit records is normalised too, as Laravel'sStartSessionand InertiastoreCurrentUrlstorefullUrl(), so the session holds the query as the pageurland the version 409's location spell it.full_url_with_queryand signed URL checks keep the query as the client sent it (PAR-056). -
simple_paginatetakes a page name, andcursor_paginaterecords its cursor.Builder::simple_paginate_using(page_name, per_page)reads the page from that query parameter and sets the paginator'spage_name, so its URLs and the Inertia scroll metadata'spageNameuse it, aspaginate_usingdoes for the length-aware paginator. Acursor_paginatepage keeps the cursor it was fetched with incurrent_cursor, which the scroll metadata reports as the current page (PAR-052). -
A CLI built between two releases pins the framework commit it was built from.
suprnova newpinned a new project'ssuprnovadependency atv<CLI version>even when the CLI was built from a later commit, as onmainbetween two releases, whose templates can use API the last tag lacks, so such a scaffold could failcargo checkuntil the next release. The CLI's build script now records the commit it is built from and whether the tagv<version>names that commit. Only then does the scaffold pintag = "v<version>". The script reads the tag from its own checkout, or, when the checkout has none, from anoriginon the same machine, so a release installed withcargo install --git --tagpins the tag: Cargo's checkout carries no tags, and the script reads the release tag offline from Cargo's git database. Anoriginreached over the network is never asked. With the tag on another commit, or in a checkout with no tag information, such as a shallow clone, the scaffold pinsrev = "<commit hash>", which at the release names the same source as the tag. A build where git cannot answer pins the tag.templates::framework_pinreturns the choice, andtemplates::cargo_toml_pinnedandtemplates::api::cargo_toml_pinnedrender a manifest with a pin you give. -
What the script scan learns from member writes does not depend on statement order. A member a class writes on
thisis the instance's own, a name a script writes on an object of its own may be its method rather than a browser API's, and a write on the global object (window[key] = value) is refused under the name its key traces to. Thelive:addscan settles those names after its first walk has met every name and every call, so a computed key's name, a name the script defines further on and a function's later calls count wherever they stand: a script is admitted or refused in any statement order, and a read of a global name nothing wrote is refused.eval,Workerand every other property refused by name are refused in any order. -
The script scan refuses every write to a member of the global object. As REG-032 requires, the
live:addscan refuses a write to a member of the global object, or of the windowwindow.openreturns (script-global), whatever the name, in every form of write,deleteincluded, so a component cannot overwrite a name the application or the Live runtime keeps onwindow. That covers a capitalised name the browser does not define (window.AcmeState = {},globalThis["Acme" + "State"] = 1), which does not become a global of the script's own, names the scan's lists do not hold (window.onload = f,window.name = "x") anddelete window.fetch, and a later read of the name is refused as a read of any global the scan does not admit is. A component keeps its state in its module scope. The shippedcomboboxno longer writesglobalThis.SuprnovaCombobox: its script's function returns the stale-suppression decisions, and the fixture that evaluates the file takes them from the script's completion value. -
#[derive(MultipartRequest)]reads indexed and bracketed part names. The derive matched a part's name to#[field(...)]letter for letter, so the Inertia client'sphotos[0]andphotos[1]never reached a#[field("photos[]")]list anduser[name]never reached a field. A part now goes to the field its name addresses, read as a form request reads it (PAR-055):photos[0]andphotos[]fill the list declared asphotos[]orphotos, in index order, anduser[name]fills the field declared asuser.name. A name sent exactly as declared still matches. A failure is named by the index the part was sent under (photos.3), andmax_countand the file checks that run while the body streams apply to every part the field takes, whatever name it was sent under. Parts are read in the order they were sent, as PHP reads them: a later part sent under a parent name, such asuseror a barephotos, replaces whatuser.nameorphotos[]held, and a lateruser[name][first]orphotos[0][caption]makesuser.nameor that element an array, which fails as the wrong kind of value. -
suprnova generate-typespairs a page built with the builder. In 3.2.1generate-typeswrote noPagesmap, and a field a handler deferred or marked optional was written as required, though the first response leaves it out (PAR-068). The component named in the first call of a chain (InertiaResponse::new,Inertia::paginate,Inertia::data,Inertia::try_data) now pairs with the struct.with_data(..)gives anywhere in it, and a key the chain passes to.defer(..),.defer_with(..)or.optional(..)after it gives the struct is optional in the struct's interface. -
A database session read keeps a session another request refreshed.
DatabaseSessionDriver::readfound a row idle past the lifetime and then deleted it by id alone, so a request that loaded and refreshed the same session between that read and the delete lost its write, and the next read found no session. The delete now matches the row only while itslast_activityis still older than the lifetime, as the MongoDB driver's does; the read that saw it expired still answers no session (PAR-188). -
The Laravel-database tests run each SQLite test on one connection. The SQLite fixture of the Laravel-database tests holds one connection. sqlx returns a released connection to the pool on a spawned task, so with more than one connection a test that awaits every statement in turn can still spread the fixture, the migrator's
CREATE TABLEand a model's first write over connections the runtime chooses, and run that write on a connection other than the one that created its table.kit_scaffold_notes_belong_to_laravels_users_sqlitechecks that the fixture holds one (PAR-080). -
The
Inertiafacade shares a once prop. In 3.2.1 onlyApp::inertia_share_onceandInertiaRegistry::share_onceregistered a shared once prop, so Laravel'sInertia::shareOnce($key, fn () => ...)had no facade form (PAR-052).Inertia::share_once(key, resolver), beside the facade'sshare,share_many,share_dataandshare_provider, makes the same registration and returns the sameSharedOnceProp, which takesas_key,until,freshandonce_withas any once prop does. -
The component allowlist refuses test fakes, app-wide hooks and installs. The
live:addscan of a component's Rust refusesHttp::fake,Queue::fake,Mail::fake,Storage::fake,Process::fakeand their siblings,Http::global_optionsand the global request and response middleware,Queue::set_driver,Cache::set_connection, theinstallof a service, and the test container and clock, whatever capability the facade's chapter grants, so a component grantednetworkcannot rewrite every request the application makes or swap a driver for every caller (REG-030). The allowlist generator refuses them by name, and the embedded allowlist carries the refusal. -
Every Live and Magnetar type a public signature leads to is named through
suprnova. A public signature ofsuprnova, or of an engine item it re-exports, names only types an application can write down; 330 of them had nosuprnovapath.suprnova::livere-exports the 212 Live engine types those signatures lead to: the typed identities, input limits, upload inspection, finalize evidence and field policy, the host context, component hooks and child composition, snapshot schemas, model state and proposals, the update protocol, the asynchronous stream contracts and the mount failure, with the engine registry's error kind asEngineRegistryErrorKind;suprnova::live::actionthe action table, its dispatch and the registered emissions;suprnova::live::metadatathe component, field, action, event and effect metadata;suprnova::live::validationValidationBagErrorandValidationSelection; andsuprnova::render_cachethe render key input and variance,Generation,QueryUnknown,ResponseSignalsand the snapshot key ring. The 118 Magnetar types are re-exported undersuprnova::magnetar_integration: the factor gate, sessions, schema, storage, password verifier and lockout, passkey ceremony, lifecycle event, first email proof and two-factor types, and withmagnetar-oauththe OAuth ceremony, error and verified identity types, the broker error and Apple's ID token claims. The Live engine exportsValidationBagError, whichErrorBag::from_issuesandValidationMessageId::parsereturn. -
Web Push refuses endpoints that resolve to private or local addresses. In 3.2.1,
EndpointPolicy::Strictchecked the shape of a subscription endpoint (https, a host name in place of an IP address, and a list of local and cloud metadata names) but not where the name resolved, so an endpoint whose name resolved to127.0.0.1, a private network or a metadata service was sent to, and the transport looked the name up again when it connected, or handed it to a proxy set on the builder or named byHTTPS_PROXY, which resolved it itself. A client passed toWebPushClient::with_clientsent underStrictonceallow_unconfined_redirectswas called. APushServiceRejectedalso kept up to 8 KiB of the push service's response body, whichWebPushChannelput in the error aNotificationFailedlistener received. The strict policy now resolves the name and refuses the send withWebPushError::RefusedDestinationwhen any answer is a loopback, private, link-local, multicast, unspecified, documentation, reserved or cloud metadata address; the error names the class (AddressClass), never the address, and a failed lookup returns the retryableWebPushError::Lookup. The transportWebPushClient::newandWebPushClient::with_client_builderbuild connects to an address that was checked, keeping the name for TLS and theHostheader, and does not look the name up again; it sends through no proxy, so neither a proxy on the builder norHTTPS_PROXYcan resolve the name past the check. A strict send over a client passed towith_client, which resolves the name itself, returns the newWebPushError::UnpinnedTransportbefore anything is sent, until the caller accepts that by name withWebPushClient::allow_unpinned_destinations, which keeps the address check.PushServiceRejectedcarries the status and theRetry-Afterhint and no part of the body, whose first 200 bytes go to the debug log, andWebPushChannelnames the status alone and logs a refused destination as a subscription that cannot be used. -
The same-origin WebSocket policy compares the scheme. In 3.2.1,
OriginPolicy::SameOrigin, the default policy of a WebSocket route, compared theOriginhost and port with theHostheader and ignored the scheme, so a page athttp://app.example.comcould open a socket on the application served athttps://app.example.com. It now compares the complete origin: theOriginscheme, host and port against the request's public scheme (Request::scheme, which readsX-Forwarded-ProtoandX-Forwarded-Sslfrom a trusted proxy only), its host (Request::host) and its port (Request::port, or 443 forhttpsand 80 forhttp). It refuses the upgrade with403when the public scheme cannot be determined: a trusted proxy that sends neither header or names a scheme other thanhttporhttps, or either header from a peer that is not a trusted proxy. The check reads the request the handler receives, so a malformed handshake is now answered400before its origin is checked. -
The dogfood application's password reset reports success only when both revocations succeed. In 3.2.1, the dogfood application's
POST /auth/password/resetcalledPasswordReset::complete, which discards the outcome of revoking the user's other sessions and remember-me tokens, and redirected to/?reset=okonce the password was written. It now callsPasswordReset::complete_with_outcome, as the scaffold's controller does, and redirects only when both revocations succeeded. A failed revocation is logged at error level with the user's id and answered with a500through the framework's error path; the password stays changed. -
A password reset whose revocation fails queues a retry. In 3.2.1, when the provider path of
PasswordReset::completeorPasswordReset::complete_with_outcomecould not revoke the user's other sessions or remember-me tokens, it logged a warning, reported the error in the outcome, and nothing tried again. The reset token was spent and the password changed, so a stolen session or remember-me cookie kept working. Both now push the newRevokeUserCredentialsjob for the user before they return. A queue worker runs it until both stores confirm the revocations, with no bound on the tries: the first retry after about 10 seconds and each later one twice as long, up to an hour between tries, with a 60-second timeout per try. The job reachesfailed_jobsonly when the worker's--triesbounds it or a try returns an error that ends retries. It is idempotent, so running it again, fromqueue:retryor by hand, is always safe, and the framework registers it with the worker.PasswordResetOutcomehas arevocation_retryfield, aRevocationRetrythat says whether the job was queued (Queued) or not needed (NotNeeded). When the push fails too, both return an error instead of the outcome: it says that the user's password changed, names each failed revocation with its error and the push's error, and asks forRevokeUserCredentials::new("<id>")to be queued once the queue works. The framework logs it at error level with the user's id, and that reset sends noPasswordChangedMailand dispatches noPasswordResetCompleted. An application can queueRevokeUserCredentialsitself after any other credential change whose revocation failed. The dogfood application logs the queued retry with the user's id before it answers its error, and answers a failed push with its500too. -
Static files and Live UI assets are read through the directory they were checked in. In 3.2.1,
StaticFileschecked a request's canonical path against its root and then opened the file by name, and opened an extensionless file a second time to sniff its type; the Live UI asset routes oftry_live_ui_assets()andtry_live_ui_assets_for()compared canonical paths and then read the file's size and its bytes by name. Someone able to rename entries under the served directory could swap a directory for a symbolic link between the check and the open, and the server sent a file from outside the root, or a script past the 1 MiB bound. Both now walk the path one directory at a time through held directory handles, opening every entry withO_NOFOLLOWas a local disk does, and take the type, the length and the bound from the handle they read the bytes from.StaticFilesstill follows a symbolic link that stays inside its root, and either root may itself be a link. A link whose relative target climbs above the root is refused even when it leads back in, andStaticFilesanswers 404 for a FIFO instead of holding the request open. On a platform withoutopenatthe two servers serve nothing, since no check by name holds there. -
The
magickdriver names the coder it hands ImageMagick. In 3.2.1 themagickdriver named the coder only for PNG, JPEG, WebP, GIF and BMP. It handed every other input to ImageMagick on a bare-, so ImageMagick chose the coder from the upload's bytes: an MVG or MSL document ran as a script, and the host'spolicy.xmlwas the only barrier. In 4.0.0 the driver also recognises HEIC and the other HEIF images, AVIF, TIFF and BigTIFF, PSD and PSB by their leading bytes, and reads them asheic:-,avif:-,tiff:-,psd:-andpsb:-. It refuses any other input before ImageMagick starts, with a 4xxFrameworkErrorthat says the format is not one Suprnova names, inprocess,dimensionsanddominant_coloralike. Autodetection is an opt-in by name:IMAGE_MAGICK_AUTODETECT=true, held asImageConfig::magick_autodetect, hands unrecognised input to ImageMagick on a bare-as before. Theoxideavdriver is unchanged. -
A request body that stops arriving is abandoned. In 3.2.1 the server bounded only the request head (
SERVER_HEADER_READ_TIMEOUT): every read of a request body waited for each piece with no deadline, so a client that sent complete headers and then sent the body a byte at a time, or stopped sending it, held its connection, and withSERVER_MAX_CONNECTIONSset a connection slot, for as long as it liked (HRD-001). Every read of a request body now waits at mostSERVER_BODY_READ_TIMEOUT(default 30 seconds) for the next piece andSERVER_BODY_TOTAL_TIMEOUT(default 3600 seconds) for the whole body, counted from when the server read the request head:body_bytes,json,form,input, the form request and multipart extractors, the multipart parsers, the middleware that read a body before the handler, and a handler that reads the raw stream fromRequest::into_partsitself. A body that misses either deadline is abandoned: the read fails with408 Request Timeout, and the server closes the connection after the response. A body nothing reads, such as one a handler keeps while it waits on other work, is abandoned at the total deadline and its connection closed. Every408response carriesConnection: close. Zero or a value that does not parse falls back to the default, as for the header deadline.ServerConfighas the fieldsbody_read_timeoutandbody_total_timeout, whichServerConfig::builder()andServerset.BodyState::StreamingandBodyState::Partial, whichRequest::into_partsreturns, hold the newsuprnova::http::TimedBody, the body under its deadlines, where they held hyper'sIncoming, andcollect_body_with_capandcollect_bodytake either. -
New projects install the timeout middleware. In 3.2.1 no bootstrap
suprnova newwrote installedTimeoutMiddleware, so in a new project a slow handler or a hung query held its connection until the client gave up. Every bootstrap now installsTimeoutMiddleware::default(), a 30-second ceiling on the time to a response that answers503. The Inertia kits install it afterInertia::installand the Live kit after its error page, both afterSessionMiddlewareand beforeCsrfMiddleware, so the503renders as the error page in the visitor's session and locale and the deadline bounds the CSRF body read. The API kit installs it first. -
A session or remember-me cookie from before a password change stops working. In 3.2.1, a password reset ended the user's other sessions and revoked their remember-me tokens at once, and nothing checked a session or a remember-me cookie against the password again: when the session store or the token table refused the revocation, a stolen session or cookie kept working until it expired. In 4.0.0, every sign-in issued through a user provider records the user's auth epoch:
Authenticatable::auth_epoch, or, when the model returns none, a digest of the password hashget_auth_passwordreturns. Every request that resolves the user from the session or a remember-me cookie compares it with the user's current one. On a mismatch, that guard's identity leaves the session, the remember-me row it holds is deleted and its cookie cleared, and the request continues as a guest's, soAuthMiddlewareanswers401or redirects to the login page; the framework logs the user id and dispatches noLogoutevent. Eachremember_tokensrow is bound to the epoch inside its hash, with no column added. A user whose model returns neither records no epoch and is not checked.Auth::login_id,session::set_auth_userandTwoFactor::complete_challengeask no provider themselves, so the request that signs in reads the epoch through the default guard's provider beforeSessionMiddlewarestores the session; when the provider fails that read, the sign-in is not stored and a warning is logged.BasicAuthMiddleware::new(), which in 3.2.1 let a session pass on its stored identity alone, now lets it pass only after the guard has resolved the user and compared the epoch, so a session from before the change gets the401challenge unless the request carries valid credentials. Each remember-me credential is bound to the epoch the guard's provider read for the sign-in, and aSessionGuardbuilt by hand under a name theAuthManagerdoes not know, which in 3.2.1 issued remember-me credentials, issues none: its login completes without a remembered session and logs a warning that names the guard. A remember-me cookie issued by 3.2.1 carries no epoch: once its user has one, it fails verification once, its row is deleted and the cookie cleared. A session signed in by 3.2.1 is checked from the user's next sign-in.Auth::logout_other_devicesbinds the current session and remember-me cookie again when it rehashes the password. With the Magnetar engine installed, the default guard keeps Magnetar's own epoch check. No signature changed;suprnova::auth::remember::issueandverify_and_rotatenow bind and check the default guard's epoch, andverify_and_rotatedeletes a row whose verifier fails. -
The
magickdriver runs ImageMagick under the framework's own policy. In 3.2.1 every ImageMagick run read the host'spolicy.xmlalone, so on a host with ImageMagick's default policy, which denies nothing, the script, network, text and Ghostscript coders and every delegate stayed open: PostScript or PDF on a bare-started Ghostscript. In 4.0.0 the driver writes apolicy.xmlof its own before each run, at.config/ImageMagick/policy.xmlin a directory it makes once per process under the system's temporary directory, open to its owner alone; it checks the file byte for byte and writes it again when it differs. The policy denies the URL, HTTP, HTTPS, FTP, MVG, MSL, TEXT, LABEL, CAPTION, PANGO, SCREENSHOT, X, EPHEMERAL, PS, PS2, PS3, EPS, PDF and XPS coders, every delegate, and@filepath reads, whether or notIMAGE_MAGICK_AUTODETECTis on;MagickCliDriver::POLICYholds its text. ImageMagick reads everypolicy.xmlit finds and applies the last entry that matches, and it reads$HOME/.config/ImageMagickafterMAGICK_CONFIGURE_PATH, its own configuration directory and$XDG_CONFIG_HOME/ImageMagick. So the driver starts it withHOMEnaming the policy directory, and withMAGICK_CONFIGURE_PATHnaming the directory that holds the file first and last, around anyMAGICK_CONFIGURE_PATHthe operator set. The framework's policy is then the last ImageMagick reads, and it outranks every other policy on the host, the system, XDG and user files and an entry markedstealth="true"included, while the host's denials still apply. Apolicy.xmlin the service account's own~/.config/ImageMagickno longer applies to the driver's runs. Before the first run of each process, for each binary and operatorMAGICK_CONFIGURE_PATH, the driver checks that order under the same environment:magick -list policymust show the last entry that matches each denial denying and the framework's file as the last one read, and one MVG probe, a one-line MVG script read asmvg:-, must be refused by ImageMagick's security policy. A check that fails refuses every run, with or withoutIMAGE_MAGICK_AUTODETECT, with a 5xxFrameworkErrorthat names the cause and the file, until the host is fixed and the process restarts. A listing or probe that cannot be had refuses the run, and the next run asks again. A directory the driver cannot make, or a policy file it cannot write and check byte for byte, refuses the run before ImageMagick starts, naming the path and the cause.
3.2.1 - 2026-10-05
Fixed
- A console binary builds in release again. The console dispatcher
awaited the application's bootstrap inline, so its whole state machine
sat inside the dispatcher's, next to the process boot that 3.2.0 added
there. A console
mainover a substantial bootstrap, the dogfood app's included, failed to compile in a release build with "queries overflow the depth limit!" while debug builds passed. The dispatcher now holds the bootstrap boxed, asApplication::runholds its own.
3.2.0 - 2026-10-04
Added
- Second-factor attempt limits.
TWO_FACTOR_MAX_ATTEMPTS(default 5) andTWO_FACTOR_LOCKOUT_MINUTES(default 15, at most 43,200) set the sliding window in which second-factor failures lock an account's second factor;TwoFactor::unlockand Magnetar'sTwoFactorService::unlocklift it. Password and second-factor lockouts count separately, so a password reset no longer lifts a second-factor lock.Authenticatable::auth_epochlets a provider carry the epoch it read with the password hash through sign-in. Lang::reload.Lang::reload().awaitreloads the translation catalogs and, when their text changed, makes RenderCache pages built from the old translations miss; dev hot reload does the same. Call it from a deploy hook instead ofTranslator::reload, which left cached pages in the old language until their TTL.- Action directives pass arguments.
live:click="remove(42)"andlive:click="rename('draft', true)"send literal arguments to the action's parameters in declared order; before, every action directive sent none, so an action with parameters could not be called from a template. Only literals are accepted (numbers, quoted strings,true,false,null), andlive:checkreports a wrong count or a literal of the wrong type at its line and column. The island root lists each action's parameter names indata-suprnova-live-actions. - OAuth identities carry the account's picture.
OAuthIdentityhasavatar_url: the picture URL the provider reports, or none. Google fills it frompicture, TikTok fromavatar_url, Facebook frompicture.data.urland X fromprofile_image_url; Apple reports none, and an empty value, or one of an unexpected shape, is none and never fails sign-in. Treat it as untrusted profile data, and check its scheme and length before you render, fetch or store it. A provider supplies it throughOAuthProvider::avatar_url, which returns none unless the provider implements it, so a provider written before it compiles and signs in unchanged (#140). - An asynchronous multipart hook.
MultipartRequestHookshasafter_validation_async, for checks that need the database before the handler runs. A multipart request runsauthorizebefore it reads the body, then extraction with its field validation,after_validation,after_validation_asyncand the handler, each only after the one before succeeded. A hook that returns errors answers 422 with them, and an empty set of errors is success. An override needs#[async_trait](#139). - Unsigned keys on every database. A model field declared
u64orOption<u64>, its key and foreign keys included, reads and writes on SQLite, Postgres and MySQL through the newAsU64andAsOptionalU64casts: the whole range on MySQL's unsigned columns, and0toi64::MAXon SQLite and Postgres, which store it signed. There a write of a larger value is refused before anything is sent, as a database error that names the column in the log, and a negative stored value fails to read the same way. A read by such a value answers what is true of every row:findreturns none, so a model bound from a route answers 404,find_manyskips the id, and a filter on the key or any narrower integer field matches as it would on MySQL.DB::tablecompares and writes such a value the same way. Au64-keyed model binds from a route,chunk_by_idandlazy_by_idwalk the wholeu64range on MySQL, and the built-in user providers sign in a user whose id is au64(#137). - Settings that match Laravel's schema. In a package's
Cargo.toml,[package.metadata.suprnova.model] datetime_cast = "native"makes everyDateTime<Utc>field of that package's models without a cast of its own, the managed timestamps included, useAsNativeDateTime, for a time-zone-aware column, and"naive"usesAsNaiveDateTime, for the time-zone-free columns Laravel creates on Postgres. In the binary's package,[package.metadata.suprnova.schema] unsigned_ids = truemakesid()andforeign_id()create unsigned columns on MySQL in every migration the binary runs, and changes nothing on Postgres and SQLite;#[suprnova::main]installs it, andSchema::use_unsigned_ids()does the same for a program without it. An unknown key or value fails the build. New applications carry both settings commented out (#137).
Changed
- Empty form fields are null, and a repeated name keeps its last value.
In a
MultipartRequestand in url-encodedFormRequest,req.form(),req.input()andRequest::query_into, an empty field is now a key holding null, as Laravel's defaultConvertEmptyStringsToNullleaves it: a requiredStringfails, anOptionisNone, a#[serde(default)]field is null, and a map orserde_json::Valuekeeps the key, so it can tell a cleared field from one never sent. An empty value used to pass as""or fail to parse as a number. AHashMap<String, String>target now fails on an empty field; useOption<String>values orserde_json::Value. A list keeps a null element in its place:Nonein aVec<Option<T>>, andvalidation-requiredunder its index, such asids.1, in aVec<T>.#[derive(MultipartRequest)]acceptsVec<Option<T>>, and a list of files still leaves out an empty file input. A field name sent more than once keeps its last value, where multipart kept the first part (even an empty one) and url-encoded forms answered 422 for a duplicate field; names ending in[]still collect every value. A url-encoded or queryboolreads1/0,true/falseandon/offin any case, as a multipart one does; JSON stays stricttrue/false. A url-encoded, JSON or query field that is missing or does not parse answers as a validation failure naming every such field (validation-required,validation-integerand the like), where it was a bare 422 with noerrors, so an Inertia form gets the usual redirect with each error under its input. CSRF checks the form's_token(its last value) beforeX-CSRF-TOKENandX-XSRF-TOKEN, as Laravel orders them, and an empty or0value counts as absent; a form body larger than 64 KiB has its_tokenread up to the server's request body limit, where it used to fail CSRF. The requests and CSRF manuals list what still differs from Laravel. - The session, remember-me, auth-flow token and ceremony entities read
whole rows on every column type. Their time fields are the new public
suprnova::StoredDateTime, which readsDATETIME,TIMESTAMP,timestamp,timestamptzand SQLite text, instead ofNaiveDateTime, which failed onTIMESTAMPandtimestamptz. Set them with.into()and read them with.naive_utc()or.and_utc(). - Magnetar rotations and second-factor lockouts. Magnetar's
re_enrollkeeps the confirmed second factor gating sign-in until a code from the new secret confirms the rotation; the rotation waits in newauth_two_factorcolumns,pending_secretandpending_recovery_codes, whichdefault_schema::migrateadds.TwoFactorRowgains those two fields, and a customTwoFactorStoreimplements the newconfirm_rotation. A second-factor lock or unlock never touches anapp_usersrow (LockoutFields::IDENTITY_IS_EMAIL,LockoutService::without_user_lock), so an account registered astwo-factor:{id}is never locked or unlocked by it. An account holds the framework's TOTP or a Magnetar second factor, never both: enrolling or confirming either answers 409 while the other exists, and disabling either one recovers an account that already has both. A custom host attachesFrameworkTotpEnrollmentto itsTwoFactorServicethroughwith_other_second_factor. - Live field and argument names must be ASCII and at most 128 bytes.
Such names used to panic at registration or fail later. A view-visible
field may be named
component; the view then reaches the component ascomponent_(or the first ofcomponent__,component___that no field takes). A field or argument may be named likesuprnova_live_count. - Cron steps count from the first value.
*/Nin the day-of-month and month fields counts from 1, as cron and Laravel do, so*/2means odd days and schedules using it shift; the timezone display now agrees with the scheduler. Ranges with steps (1-15/7) and mixed lists parse. - Workflow steps are named by module path and function name, so same-named steps in different modules are different steps. Runs recorded with bare names still replay.
TestContainerGuardcan no longer be built directly; useTestContainer::fake().dispatch_argv_with_initboots the process and waits for queued listeners after the command;dispatch_argvdoes neither.saveandupdaterefuse a model that was never inserted. A replica, or a new model fromfirst_or_neworfind_or_new, still has its reset key, andsaveupdated the row with key 0. It now returns an error namingpersist(), which inserts the model and returns it with its new key. Laravel'ssaveinserts such a model;savehere takes&selfand cannot hand the new key back, which the Eloquent manual explains.- The broadcast fanout no longer uses sea-streamer.
SeaStreamerBroadcastHubkeeps its name and runs on the framework's own Redis client, andsea-streamerandsea-streamer-redisleft the dependency tree. It supportsredis://,rediss://andmemory://, a stream shared by hubs in one process;stdio://is an alias formemory://and no longer reads or writes stdin and stdout.kafka://andfile://, which were never compiled in, now give a clear error, andnew_loopbackbehaves likenew. An event published after the constructor returns always arrives. Stream entries keep theirmsgfield, so hubs of the earlier version on the same stream interoperate during a rolling deploy. - New applications' session, remember-me and auth-flow token tables use
DATETIMEon MySQL, so these columns stay writable past 2038-01-19. Postgres and SQLite are unchanged. - The features table holds times after 2038 on MySQL. A new
featurestable usesDATETIMEon MySQL and MariaDB. Addsuprnova::features::migrations::FeatureTimestampsToDatetimeafterCreateFeaturesTablein your migrator: it converts an existingTIMESTAMPtable, keeping its UTC times and defaults, and does nothing on Postgres and SQLite. - Two-factor needs two new migrations. Add
suprnova::auth_flows::two_factor::migration_attempts(thetwo_factor_attemptstable) andmigration_rotation(thetwo_factor_rotationstable) to your migrator. Without the first, every two-factor proof path answers 503 and names the migration; without the second,TwoFactor::re_enrollanswers 503. A pending rotation keeps the confirmed secret gating sign-in untilconfirmpromotes the new one,enrollcannot replace a pending rotation, anddisablediscards it.enrollanswers 422 for a user id longer than 255 characters. Auth::password().registerreturns aRegistration:Created(user)orAccepted, never the existing account. TheMagnetarPasswordAuthEngine::password_registertrait method returns it, and a custom engine gainsadmit_host_sign_inandissue_host_session, which refuse with 503 by default. The API starter answers every registration with one generic 202.- Magnetar's second-factor lockouts have their own table. The default
schema's migrate creates
auth_second_factor_lockouts(DefaultSecondFactorSchema), andTwoFactorService::newtakes a lockout service over it.TwoFactorStore::set_confirmedtakes the enrollment snapshot that was checked, and the MySQL migration failures (SwapFailure,MySqlMigrationFailure) are boxed. Cache::tags_putwithout a TTL appliesCACHE_DEFAULT_TTL, asCache::putdoes. A tagged value that must never expire uses the newCache::tags_forever.DiskExt::temporary_upload_urlreturns aTemporaryUploadUrlwithurl,methodandheaders, instead of aString. An S3 disk with server-side encryption signs headers such asx-amz-server-side-encryption, and an upload that did not send them was refused. Use.urland send.headerswith the upload. ItsDebugoutput redacts the signature and header values.Queue::bulkhonours debounce. Every copy of a debounced job pushed throughQueue::bulkused to run. A debounced burst now collapses onto its last job, and a job declaring bothdebounce_forandunique_idis refused, asQueue::pushdoes. Laravel'sbulkskips debounce; the queues manual explains the difference.- Multipart failures answer as validation errors under the field's input
name. A missing field, a text part that does not parse as its type or is
not UTF-8, a part of the wrong kind, and a file a validator refuses (too
large, not an image, a type
MimeTypedoes not allow) answer 422 witherrorsunder the form input name, so the second file of afiles[]field isfiles.1, and the Inertia validation middleware shows each error under its field. Before, a text part that did not parse answered 400, a file overMaxSize413, and the others 422 withouterrors. The messages come from the validation catalog (validation-required,validation-max-fileand the rest), so an application'slang/<locale>/validation.ftloverrides them. A file overMaxSizestops the body at the chunk that crossed the limit and leaves no temporary file. A field'smax_countanswers 413 with the other request-wide limits, instead of 422, and so does a text part longer than the in-memory spill threshold (2 MiB by default), instead of 400, as Laravel answerspost_max_size. A file validator checks only the file parts its field takes: a text part sent where a file belongs fails asvalidation-file, and a later part for a field that holds one file is ignored without being read into memory or a temporary file. For a field that holds one value, its first part decides it, valid or not, so several failing parts report one error; an empty part does not decide a field that is not aString, so the next part of its name can. AnUploadValidatorreturnsFrameworkError::invalid_uploadfor a validation failure, and its other errors keep their status. Aboolfield accepts1,0,true,false,onandoff. An empty part, which Inertia sends fornull, is none for an optional field that is not aStringand missing for a required one, and a part of the wrong kind sent to an optional or list field fails instead of being ignored.MultipartValue, which the streaming parsers return, has a newNonUtf8Textvariant for a text part that is not UTF-8, so amatchover it needs an arm for it (#139). #[model]takes the key type from the key field. Withoutkey_type, the key type is the type of the fieldprimary_keynames; it wasi64whatever the field said. Akey_typethat disagrees with that field fails to compile, naming both (#137).pluck,valueand the aggregates read every key type, and say why a value does not read.pluck,pluck_keyed,value,value_or_fail,sole_value,sum,min,maxandDB::scalartake any type that implements the newColumnValuetrait, which every type SeaORM reads already does, andu64, which they now read on SQLite and Postgres too. A generic caller bound byTryGetableneedsColumnValueinstead.avgreads anf64or arust_decimal::Decimal(the newAvgValuetrait); another type no longer compiles. Postgres and MySQL average exactly, so aDecimalaverage is exact there. SQLite averages as a REAL, so there theDecimalholds the shortest decimal that round-trips SQLite's floating-point answer.pluck,pluck_keyedandvalueused to drop a row whose value did not decode, sopluck::<u64>returned an empty list; they still skip a NULL, and any other value that does not decode is an error naming the column (#137).- The combobox submits the chosen option's value. A selection used to
write the option's label into the one bound field, so the value each
option carries never reached the server.
suprnova.comboboxnow binds two fields:nameis the chosen option's value, held by a hidden input that a selection fills and an edit of the text clears, and<name>_queryis the typed text, which a remote listbox answers. The macro takes the island's value asvalue, and the script marks that option selected. Bind the query field where you boundnamebefore, and read the choice fromname. - Live's limits are settings sized for large pages. Every limit Live
applies is a
LIVE_*key in the application's.envfile or aLiveConfig::builder()method, and a value outside a key's range fails boot with an error that names the key. The browser runtime had smaller limits of its own: it refused an island render over 32 KiB and a morph past 10,000 nodes or one second while the server allowed 1 MiB, and an action whose island root passed 1 MiB failed. The bootstrap now writes every limit into the page's configuration element and the browser applies those values, so it never refuses what the server allows. Requests, responses and island HTML default to 16 MiB; a morph takes up to 1,000,000 nodes and keys with no deadline; an upload sends 8 MiB chunks of a file up to 1 GiB; an open document holds and replays up to 4,096 asynchronous events; and a session streams to 64 open tabs, where it was 8. A replay log holds up to 4 MiB per subscription and 256 MiB across the process, dropping its oldest entries first, and a reconnect that needed a dropped entry renders fresh. A tripped limit's message names the limit, the measured and configured values and the key, in the browser console and in the server log.suprnova live:inspectprints every limit by its key, and the Live chapter lists them with their ranges.live:checkandlive:inspectspeak tooling protocol 2 and fall back to protocol 1 with an application built before it. - Framework payments, features and RBAC models carry
DateTime<Utc>timestamps. The SeaORMModelof the six payments entities, offeatures::entity, and of the RBACRoleandPermissioncarriesDateTime<Utc>(Option<DateTime<Utc>>forcanceled_at,paid_atandprocessed_at) where it carriedString, because their migrations create native timestamp columns. Code that read those fields as text needs the date-time type. - A mail message is checked on the dispatch path, and a refusal is a
500.
Mail::send,Mail::raw,Mail::html, the queue worker and the notification mail channel check the message beforeMessageSendingfires and before any transport sees it, including a transport bound withMail::set_transportand the one behindMail::fake.Mail::queueandMail::latercheck it when they push. A refusal is an internal error, a 500 with the detail in the log, where it was a 400 that echoed the address. Headers the message structure owns (To,Cc,Bcc,From,Sender,Reply-To,Return-Path,Subject,Date,Message-ID,MIME-VersionandContent-*) are refused as caller headers. Postmark refuses a second tag, and SES refuses a tag or metadata it cannot carry, instead of dropping them. The address and header serializer is public assuprnova::mail_wirefor transport authors. - The framework registers its own mail and notification jobs. A worker
dispatches
SendMailJobandSendNotificationJobwith noregister_jobline. Registering the same job type again is quiet; only a different type taking over a job name still warns. - A full Live instance ledger evicts instead of refusing mounts. At
LIVE_LEDGER_MAX_INSTANCES, a new mount or promotion removes the instance that expires soonest, preferring one with no claim in flight, and the evicted page's next action getsrefresh_requiredand reloads fresh. Before, a full ledger refused every mount on the site until records expired, and anyone who could mount in a loop could keep everyone else out.CapacityExceedednow means only a record over a codec bound. A customInstanceRecordStoreimplements two new methods,soonest_expiring_instancesandcompare_and_remove; the memory, SQL and Redis stores ship them. - Live form controls match the density of the suprnova.app forms.
Controls read at 14px through
--sn-density-control-font-size(16px on a coarse pointer), fields are 40px tall, labels are 12px and sit 6px above their control, legends are 14px, and hints and errors are 12px. A textarea shows three rows and is at least two control heights tall.--sn-density-field-gapputs 12px between fields, checkboxes, switches and groups, and a group's options sit 8px apart. To pick it up in an application, runlive:addagain forbutton,checkbox,combobox,datatable,date-picker,field,fieldset,input-otp,label,load-more,pagination,radio-group,switch,textareaandupload. - Content negotiation treats
q=0as a refusal.accepts,accepts_json,prefers,wants_json,expects_jsonandacceptable_content_typesleave out anAccepttype weightedq=0, as RFC 9110 says, even beside*/*; the most specific matching range decides. Laravel lists such types as acceptable. - Vendor HTTP clients no longer follow redirects, and SQS overflow
payloads move. Pinecone and the HTTP mail drivers treat a 3xx as an
error. SQS overflow payloads live under
sqs-payloads/<queue>-<digest>/, soSQS_OVERFLOW_FLUSH_ON_CLEARno longer deletes a same-named queue's payloads from another account, region or endpoint; payloads written before still read, butclearno longer sweeps them. Qdrant ids"01","+1"and non-canonical UUID spellings no longer map to the point of"1"or the canonical UUID, so items stored under such ids must be written again. A caller's version 5 UUID id is hashed like any other string, so it can never name a point a derived id holds; items stored under v5 UUID ids must be written again too. Resend tags go out astag_<i>name and value pairs, and a tag Resend cannot carry is refused before sending.DynNotificationgainsas_any, with a default. build_docsrefuses chapters that would overwrite each other. Two chapters with the same file name, or one namedcatalog.md, now fail with the newContentError::DuplicateChapterSlugorContentError::ReservedChapterSlug, naming the files, so an exhaustivematchonContentErrorneeds the two arms. The same file listed twice is still allowed.IMAGE_MAX_ALLOC_BYTESbounds the whole decode, and defaults to 1 GiB. It used to bound only the decoded RGBA size, so a decoder could allocate several times the limit while it worked. It now covers every buffer a decode and its source read hold, measured per format (the cost table is inmanual/images.md), and the default rose from 256 MiB to 1 GiB so a 48-megapixel photo in any 8-bit format still decodes. JPEGs decode throughzune-jpeg(pinned at0.5.16-rc2, the first release that decodes every Huffman and arithmetic sampling correctly); lossless JPEGs still decode throughoxideav-mjpegand are refused by name above 67 million samples.- Guard names, verification links and the default auth schema. A guard
name other than the default session or token guard may not contain
:or be empty, because a non-default guard's principal is now<guard>:<id>, and a default-guard id that contains:is now the principal:<id>in Live gates, uploads, subscriptions and memberships, Pusher'suser_idand the RenderCache key, soadmin:9on the default guard is never guardadmin's user 9. Ids without:are unchanged. A token guard other than the default no longer copies its user into the defaultAuthview, soAuth::has_user()stays false for it. Email verification links issued before this change are refused and must be sent again. The default auth schema enforces one account per email with a unique index, so a migration over anapp_userstable that already holds duplicate emails stops with an error until they are merged. New, with defaults:TokenGuard::named,UserProvider::verification_email,UserProvider::mark_email_verified_forandTwoFactorStore::withdraw_enrollment.
Fixed
- Unsigned keys, relation min and max, and raw bindings on every engine.
with_minandwith_maxread 32- and 16-bit integer columns on Postgres, and dates, text and times on every database, without an error;_min_ofand_max_ofreturnSome(None)for a value that is not a number, and the new<rel>_min_as::<T>()and<rel>_max_as::<T>()read the value itself.DB::table, raw fragments and joined-table columns compare au64abovei64::MAXas the database does for the stored data, including a REAL held in an INTEGER column on SQLite, andDB::tablewrites store such a value exactly in numeric and text columns while integer columns, and NUMERIC columns on SQLite, refuse it.attach,attach_with(extras included),detachandsyncbind pivot ids by their column's type: on Postgres and SQLite au64abovei64::MAXis refused, naming the column, before anything is sent; on MySQLsyncno longer duplicates unsigned pivot ids, andBelongsToManyandMorphToManyget()load rows whose pivot column is unsigned, where they returned none. On Postgres, a raw fragment sent first with an integer and later with a value abovei64::MAXno longer fails with "incorrect binary data format". Modelupdate_allandupsertof such a value to a field that is neither an integer nor text follow the column, asDB::tablewrites do (#137). - Durations too long for a date are errors, not panics. A workflow lease
or retry backoff too long for a date is refused at boot:
WORKFLOW_LOCK_TIMEOUT_SECSabove 253402300799, orWORKFLOW_RETRY_BACKOFF_SECStimesWORKFLOW_MAX_ATTEMPTSabove it, stops the worker at start with an error naming the setting, and lease refreshes return an error for such a lease.Queue::laterand its variants, a job'sdelay(), and requeues in the default, SQS and database drivers return an error naming the delay, where they panicked or, past a chrono duration's range, requeued with no delay at all. - A refused cookieless request stores no session.
CsrfMiddlewaremarks a new, untouched session for storage only when the response succeeds or redirects. An anonymous request that creates a session and is refused with 401, or any other 4xx or 5xx, gets noXSRF-TOKENand writes no session row, so it no longer turns into a 500 when the session store is unavailable; a session that was loaded or changed keeps its token. A cookieless JSON orHEADbootstrap that succeeds still gets its token with its session.SessionMiddlewaremarks every session thatSessionStore::readreturns as loaded from the store, so a custom store that builds its sessions withSessionData::newno longer gets a write on each successful request throughCsrfMiddleware. - Live uploads, private responses and tooling. Finalized uploads free
their pending slots when finalization commits, so a session no longer runs
out of upload capacity until restart, and are reclaimed when they expire.
A finalization that failed or stalled is reclaimed at expiry, and an app
without a finalizer leaves uploads Ready instead of stuck in Finalizing.
Cleanup deletes only temporary and uncommitted bytes; bytes finalization
committed as output are never deleted. Every RenderCache response without
shared-cache permission, public pages without
s-maxageand zero-slot composites included, isprivate, no-cache. Making room for a file-store publication reads only the entries it evicts. A Live tooling timeout kills every process the helper started, and Ctrl+C still reaches the helper. A Live action withvalidate = "arguments"and a typed#[validate(action = ...)]hook compiles without a component-level#[validate]hook. Generated route helpers handle optional parameters ({id?}) asroute()does, leaving an empty one out of the URL. Schema dump and load reach Postgres over a Unix socket named in the URL host (postgres://%2Frun%2Fpostgresql/db). - Scaffolded apps on MySQL 8.4 and Postgres, and dates past 2038. The
auth-flow token table's hash is
VARCHAR(64); MySQL 8.4 refused the UNIQUE key on the oldTEXTcolumn (error 1170), so a new app's migration stopped at the fourth step and the app could not boot. Runmigrateagain on an app that stopped there. The--apistarter'sapp_userstime columns aretimestamp with time zoneon Postgres andDATETIMEon MySQL, which itsUsermodel and Magnetar read; an existing API app on Postgres converts them with theALTER TABLEin the CLI chapter. The notifications and RenderCache ledger migrations createDATETIME, so writes keep working after 2038-01-19 on MySQL; tables created before keepTIMESTAMPand still work, and the newNotificationTimestampsToDatetimemigration moves an existing MySQL or MariaDBnotificationstable toDATETIME, keeping its UTC times. A remember-me, auth-flow token or ceremony lifetime too large for a date is an error instead of a panic. - Generated routes and types, Inertia props and JSON:API.
generate-types --routesappliesgroup!path and name prefixes, gives each repeated-handler alias its own helper, percent-encodes path values likeroute(), and uses serde's input keys in request interfaces; helpers for a second route of one handler get a new params interface name. An SSR exclusion glob such as**/foo/*matches where**spans a repeated literal. The redirect back for an empty Inertia response keeps the handler's cookies, security headers and error report. Replacing a lazy prop drops its?include=gate, a later dotted prop wins over an earlier lazy parent, andApp::inertia_shared("users.0.name")reads into shared lists. A JSON-styleinertia_response!prop that fails to serialize returns an error instead of panicking. JSON:API documents no longer repeat primary resources inincluded, an empty collection refuses unknown includes with 400, a requested include always returns anincludedarray, and error pointers are escaped per RFC 6901.i128andu128route-parameter fields in Data DTOs extract instead of answering 422, and DTOs with route-parameter fields compile without a directurldependency. Live route intents can target resource routes, androute()andtry_route()fill a catch-all{*rest}by the namerest, keeping its slashes. Numericexpect!matchers fail on NaN and other unordered values. Schema dump and load accept every TLS parameter spelling the application's connection accepts and pass the Postgres password throughpassword=. TheIdempotency::rememberexample key includes the authenticated user. Live component names, views and action text that mention development crate names compile, action arguments namedtargetorrequestno longer break generated code, and#[session]Live fields load from and persist to the visitor's session once the action's outcome is accepted (they needSessionMiddleware). - Workers, the console and process lifecycle. Queue, schedule and
workflow workers, the
queue:*commands and console commands boot the#[injectable]and#[service]inventory, so a job or command that resolves an action no longer fails withServiceNotFound. The console also boots the runtime drivers and#[policy]gates, warns on stderr and goes on when a driver cannot boot, and waits for queued listeners before it exits. Workers, the queue and maintenance commands and console commands cancel and drain the supervisors the bootstrap started before they exit, with the same 5-second grace asserve, and so does any command or console that fails after the bootstrap ran;down,upandschedule:listrun the application's bootstrap hook, and the hook's docs name the migration commands that skip it.schedule:workstops on SIGTERM while an inline task runs, stopping a task still running after the 30-second grace. A panickingTerminablehook no longer skips the hooks after it, and a graceful shutdown waits up to 5 seconds for hooks still running.Context::getandContext::hidden_getno longer deadlock when a customDeserializewrites to the context. ATestContainerGuardorTestQueryGuarddropped on another thread clears only what it installed. Binding an#[injectable]by hand before boot no longer requires the dependencies only its generated constructor reads.db:seed --class=<Name>fails with not-found on an empty registry, and a poisoned registry fails instead of reporting nothing to run. A supervisor spawned during or after shutdown no longer starts outside the drain. A secondinit_telemetrywhile the first guard lives no longer takes over the global meter provider.start_workflow!accepts imported, re-exported,crate::,self::andsuper::paths, andworkflow:workon a database other than Postgres exits with an error at startup instead of retrying forever. - Relations and soft deletes.
destroy,delete_quietly,delete_or_failand trait-dispatcheddeletepermanently deleted soft-delete rows; they now tombstone them, anddelete_or_failon an already trashed row is a 404.with_countand thewith_sumfamily counted trashed rows and rows hidden by global scopes; they now cover exactly the rowswithloads.with([..])andwith_count([..])on one relation no longer panic, a count no longer makesload_missingskip the rows, and a failed or cancelled nestedload_missingno longer erases relations already loaded. Relations declared withlk = "..."read and write by that column, and anlknaming no field is a compile error. Eager many-to-many honoursrelated_key, a relation'spivot_tableoverride is used when loading pivot context, and eagerHasManyThroughskips rows reached through a trashed intermediate. Eager loads of awith_tx(&tx)oron(name)query run on that transaction or connection,MassPrunabledeletes on the connection its dry run counted, and factory inserts of plain SeaORM rows join the surroundingDB::transaction.with_minandwith_maxof an integer column read on Postgres.has,where_hasanddoesnt_havework on models whose primary key is notid, and join a many-to-many on its declaredrelated_key. LazyHasManyThroughandHasOneThroughgetandcountapply the target model's global scopes, as eager loads do. A pivot model's own global scopes and soft-delete filter no longer drop attachments from many-to-many reads; as in Laravel, they apply when the pivot model is queried on its own. A softdelete()setsupdated_atalong withdeleted_at, anddelete_or_failtouches the owners named intouches, asdelete()does. ABelongsTodeclared without an owner key finds its owner by the owner model's primary key instead ofid, in lazy and eager reads, counts and aggregates,hasand owner touches.has,where_hasanddoesnt_haveon aMorphedByManyrelation work; they named a pivot column that does not exist. Every relation key default now comes from the models' primary keys, never a literalid:HasManyThroughandHasOneThroughwithoutsecond_local_keyjoin on the intermediate model's primary key,MorphManyandMorphOnereport their parent key or the declaredlk, and aMorphToreports its targets' primary key, through the morph registry when the targets differ;MorphTypeEntrygains aprimary_keyfield. - Magnetar hashing and sign-up races. Magnetar password hashing runs on Tokio's blocking pool instead of stalling async workers. A magic-link or passkey sign-up that loses a race for a new email address answers as the existing account instead of failing.
- RenderCache stays coherent under cancellation, races and flags. A
write that was cancelled at its generation advance, including a bulk
write,
increment, a soft delete, restore or force delete, could commit while cached pages stayed current; the write and its advance now share one transaction. An unrelated successful write no longer resumes serving pages whose invalidation failed: the missed invalidation is applied first, and an advance that lands clears only the failures recorded before it began, so a newer failure for the same tables keeps pages suspended until a later advance covers it. A process that wrote before installing RenderCache advances generations after the install. Pages rendered with a flag's compiled default refresh when the first rule for that flag is stored, and a page rendered duringset_flagorreloadno longer stays cached with the old answer.DB::unprepared,DB::statementandstatement_onwith a batch that begins withSELECTinvalidate cached pages. Pages built fromEntityExtorQueryBuilderreads, relation counts and aggregates, or through-relation loads refresh when those tables change, and lazyHasManyThroughget,firstandcountandHasOneThroughgetrefresh when an intermediate row changes. The payments webhook advances its mirror tables, and its receipt insert, retry error clear and failure record, in the transaction that writes them, so a request cancelled during COMMIT no longer leaves them committed but cached pages current. A write on a named connection that is dropped during its COMMIT suspends serving until a later advance repairs it.RenderCache::advance_epochreaches the next request even with another request's authority read in flight. A rebuild that fails after the stale-on-error window closed returns its error instead of the expired entry, a node runs at most one background refresh per key and at mostRENDER_CACHE_MAX_BACKGROUND_REFRESHESacross keys (new, default 32 per CPU, 0 turns background refresh off; past it a stale hit serves the stored copy and starts nothing), a cancelled L1 publish can no longer overwrite a newer entry, and L1 sweeps no longer scan the whole store. SQL Live record cleanup no longer deletes a fresh instance or reservation another node just created. Renewing an async subscription from an evicted position is refused, so the membership degrades instead of claiming continuity, and a degraded delivery lane replays what it missed from the subscription's log, or retires the transport when the log no longer holds it, instead of streaming on past the gap. A finalized direct-storage upload is retired through the application's direct upload provider when cleanup reclaims it. The Live tooling helper's timeout ends the call even when a process it started keeps its output open or the helper wrote a complete exchange and kept running. - Query builder, pagination and Eloquent. Paginating, ordering and
taking
firstof a union works on every engine, andtotalcounts its rows; as in Laravel, ordering, limit and offset set beforeunionapply to the first query and those set after it to the whole union.count,sum,avg,minandmaxwork afterselect(...), after an ordering, on a union and withhaving.in_random_orderworks on MySQL, andskiporoffsetwithoutlimitworks on SQLite and MySQL.chunk_by_id,lazy_by_id,cursor_paginateandPagination::cursorvisit every row once whatever the query was ordered by, and apply an offset once.chunk,chunk_map,each,chunk_by_idandlazy_by_idhonour the query'slimitas a cap on the whole walk and itsoffsetas a one-time skip, so.limit(5).chunk_by_id(2, ..)visits 5 rows instead of the whole table.cursor_paginateon a union pages the whole union.count,sumandavgreturn 0, andminandmaxreturnNone, when an offset skips the aggregate's row or a grouped query has no rows, instead of failing with "aggregate query returned no row".filter_json_containsworks on Postgres and MySQL with strings, objects and arrays.create_or_firstinside a Postgres transaction returns the existing row, and a lost race creating a Live record no longer aborts the host's Postgres transaction.UniqueandExistsinsideDB::transactionsee the transaction's own rows and no longer wait on its connection.Collection::sort_byand the by-valueDistinctrule compare integers above 2^53 exactly. Index and foreign key names holding a backtick or double quote create and drop.decrement(col, i64::MIN)subtracts instead of panicking.UniqueIdKind::Ulid.is_validrejects strings that overflow 128 bits.QueryExecuted::to_raw_sql()returns the SQL unchanged when a binding is missing or left over, andQueryBuilder::countandPagination::length_awarereport theCOUNT(*)they ran toDB::listenand the query log. Inertia infinite scroll asks for the paginator's own page or cursor parameter. ConcurrentSchema::dumpcalls to one path each write a whole file.test_database!()with no argument compiles and uses the crate's ownmigrations::Migrator. - Typed counts, union walks and decimal relation minimums. Typed
QueryBuilder::countkeeps the whole count under a limit and returns 0 past an offset,existsasks about the rows the limit and offset leave, and aPagination::length_awaretotal counts every match, as Laravel does, andDB::table(..).count()keeps the limit and offset the same way.QueryBuilder::offset(n).all()andfirst()with no limit run on SQLite and MySQL instead of failing with a syntax error.chunk_by_id,lazy_by_id,lazyandcursorover a union visit each row once and finish; the cursor bounded only the first query, so the batches repeated forever.<rel>_min_as::<Decimal>()and<rel>_max_as::<Decimal>()read aNUMERICorDECIMALminimum or maximum exactly on Postgres and MySQL, and::<String>()reads its decimal text. - Overlapping drains of queued listeners wait for each other. A
second
EventFacade::drain_queuedrunning while another drain held a listener reported the dispatcher drained at once, so a console command could return, and a shutdown could finish, with a queued listener still running. It now waits for that listener, and counts it if its deadline passes. - Debounced jobs, queue events, log subscribers and process timeouts.
Overlapping debounced dispatches keep the one that armed last: each takes
its place from an atomic counter in the cache, so a newer push is never
dropped for an older
Queue::bulk, and a stalled dispatch does not also run. When max wait runs out inside oneQueue::bulk, the bulk's last job runs at once instead of being dropped as superseded. A debounce id ending in:first_dispatched_atno longer shares a cache key with another id's first-dispatch stamp, which failed that id's dispatches.JobProcessedfires whenever the job's pipeline returns without an error, as Laravel's worker fires it: after middleware deletes the job, thenJobAttempted; after middleware releases it, beforeJobReleased; after a middleware failure without an error; and after a debounced dispatch is dropped as superseded, betweenJobDebouncedandJobAttempted. The worker raises the rest of its lifecycle events in Laravel 13.27's order for every outcome too:JobAttemptedafter a retry and after a release by middleware;JobExceptionOccurredafterJobFailedfor an error or panic on the last attempt, for a job already out of attempts, and forFailOnException;JobFailedbeforeJobTimedOut, with noJobAttemptedafter a timeout; andJobProcessingfirst for a job already out of attempts. Building a log subscriber withlogging::build_subscriberchanges nothing until it is used: each subscriber writes file lines in its own format, and building no longer resets the default channel, so a caller that relied on that callscheck_channels. A process timeout's kill can no longer reach a process or group id that the owner reaped in the meantime. - Docs reading order, memory fanout streams and the image budget docs. A
docs chapter listed twice in the table of contents keeps one place in the
previous and next chain, its first listing, and every catalog entry for it
matches its JSON file. A
memory://fanout stream is freed when its last hub drops instead of staying registered until the process exits. TheImageConfigdocs give the real 1 GiB default forIMAGE_MAX_ALLOC_BYTES. - Rate-limit identities, RBAC races, email verification and second
factors. A request that names more than one identity in its query or
body is also refused by, and counted against, each identity's own bucket.
Creating a role or permission and granting one succeed when two requests
make the same one at once, on every engine. Email verification stamps only
the address the link was mailed to, even if the address changes while
verifyruns; a custom provider closes the remaining window by overridingUserProvider::mark_email_verified_for, as its docs explain.session::destroy_all_for_userdestroys only the sessions of the default guard's user, so a password reset for web user 7 no longer signs out admin 7, and the newdestroy_all_for_guard_userdoes the same for another guard; every Live membership issued under a destroyed session now ends, whichever guard's user held it. On Postgres, a user id abovei64::MAXbinds by the column type of the table the lookup actually reads. A framework TOTP enrollment and a Magnetar enrollment that race each other leave the account with one second factor; in a tight race both answer 409 and the user enrolls again. - Sessions and remember-me tokens restore on MySQL and MariaDB. A
scaffolded application's session, remember-me and auth-flow token time
columns are
TIMESTAMPthere, and the framework read them as a type the MySQL driver decodes only fromDATETIME. Every session read failed: a form POST answered 419 and the next page 500, the remember-me cookie never signed anyone back in, and verification and reset links could not be used. The notification inbox and the ceremony store failed the same way, and on Postgres each failed on atimestamptzcolumn. They now readDATETIME,TIMESTAMP,timestamp,timestamptzand SQLite text, and existing tables need no migration. A notification whoseread_atdoes not decode is an error instead of unread. On MySQL, an expiry past 2038-01-19 03:14:07 UTC is stored as that moment. - A new application registers and signs in on every database. The
userstable andUsermodel thatsuprnova newwrites disagreed on the time column type, so registering failed on MySQL 8.4, MariaDB and Postgres. The migration now uses.date_time()and the model namesAsNaiveDateTime. An existing application gives itsUserthe casts for its columns: the native casts on MySQL and MariaDB, the naive ones on Postgres. See Authentication, "The scaffolded User model". - Two-factor flows on every engine. A framework login completed with
TwoFactor::complete_challengestays signed in under the Magnetar engine. The two-factor credentials table and the attempt-counter migration create on MySQL and MariaDB. Concurrent second-factor admissions no longer deadlock across users on MySQL. On Postgres, a correct Magnetar second-factor code, every ceremony state change, passkey registration and removal, and account unlinking answered 500; they work. A committed two-factor confirmation is reported as confirmed even when its attempt record cannot settle. A password reset keeps an encrypted column that changed while it ran, and stores the new hash verbatim whatever the model's mutators. - Cache, maintenance mode and read-through disks.
Cache::remember_foreverandCache::searno longer expire afterCACHE_DEFAULT_TTL, anddownwithMAINTENANCE_DRIVER=cacheno longer ends by itself after it. On Redis,Cache::flushmatchesREDIS_PREFIXliterally, so a prefix holding*,?,[or\no longer deletes other applications' keys or misses its own, and a value extended withCache::touchis still removed byCache::flush_tags. Tag indexes no longer grow without bound for tags written often and rarely flushed. Concurrentdownruns with the file driver no longer publish a half-written down file. The production guard foron_one_server()checks the bound cache store instead ofCACHE_DRIVER; a custom sharedCacheStoreoverrides the newlocks_are_sharedto returntrue. The cached feature-flag evaluator sees an admin change made during a concurrent miss and holds at most 4096 entries. Read-through promotions stream into the primary instead of holding the object in memory, unpromoted reads fetch only their range, and a delete or move during a promotion is not undone, on the same node or another one: a promotion asks the fallback again just before it publishes and after, a cancelled read still finishes that check, and a withdrawal deletes only the exact version the promotion wrote, never a writer's newer object. An equal length no longer counts as proof that the fallback object is unchanged: a fallback without an ETag, version or modification time, such as the in-memory disk behindStorage::fake(), is checked by content, so a same-size overwrite is never promoted as the old bytes. On a primary without versioned deletes (local, memory, and unversioned S3, Azure Blob and GCS) the promotion keeps its copy and logs a warning instead, so a delete on another node that lands between the last check and the publish can leave that copy behind. Versioned and conditional reads reach the fallback, and a refused move keeps the fallback copy. Ranged reads stop at the requested range: a server that ignoresRangecan no longer make a small read buffer the whole object, and S3, Azure Blob and GCS refuse a response that is not the requested range before reading its body, open-ended ranges included. - Queues, events and processes. Cancelling
Transaction::commit()while its COMMIT was in flight could drop itsafter_commitcallbacks andpush_after_commit_with_txjobs although the rows committed; they now always run. A queued listener that dispatches another queued event no longer hangs queued event dispatch,drain_queuedwaits for and counts listeners admitted while it drains, andEventDispatcher::deferbuffers only its own dispatcher's events. A debounced dispatch claims its window only after its envelope is queued, so a failed or cancelled dispatch can no longer get queued work dropped as superseded, andmax_debounce_waitlonger than the debounce token's lifetime forces a run again. Batches on thesyncdriver finish and fire their callbacks, a batch whose dispatch failed part way firescatchandfinallyonce its queued jobs settle, and two concurrent first batch dispatches no longer lose one batch's tracking.JobAttemptedfires for jobs that fail or time out terminally. A cache error whileThrottlesExceptionsclears its counter no longer fails a completed job, and one while it counts a failure no longer replaces the job's own error or turns a backoff release into a failed attempt. A cancelled memory-queuepop, delayednackorreleasekeeps the job.FailoverQueueDrivercounts a driver registered under two labels once. An after-commitpush_uniquewhose job fails to serialize releases its lease. A started process whose child left its group can no longer have its timeout,stop()or drop signal an unrelated process group. - A Fluent message named
NUMBERorDATETIMEkeeps the function callable. Such a message broke everyNUMBER(...)orDATETIME(...)call in its catalog. The message keeps its key and the functions still format. - Presence channels and WebSocket upgrades. A presence channel whose
last member left stayed in memory, so parameterized presence channels grew
with churn; empty channels are now removed. A connection aborted at
shutdown or cancelled during a re-subscribe left its presence member
visible and its forwarder tasks running; cleanup,
presence.leftincluded, now runs on every exit. Headers middleware adds to a successful WebSocket upgrade, such as a sessionSet-Cookie, now reach the client on the 101, and terminable middleware runs for upgrade responses with status 101 or the refusing status. WebSocket route parameters are percent-decoded like HTTP ones, subprotocol negotiation echoes the client's own spelling as RFC 6455 requires, andsse::last_event_idreturns Unicode event ids instead ofNone. - Each named middleware runs once per route. A middleware group included
by two sibling groups, an alias listed twice, or a middleware named both
through a group and on the route itself ran twice per request, so a
throttle there counted each request twice. A route now runs each named
middleware once, identified by its alias and parsed arguments, at its
first occurrence, as Laravel's
uniqueMiddlewaredoes. Middleware added by type with.middleware(M)is never dropped. - Gates, OAuth starts, CSRF bootstraps and registrations. A gate
callback that calls
Gate::defineno longer deadlocks the request. An OAuth start that is the browser's first request (JSON or POST) sets the session cookie, so the callback binds instead of answering 400. A cookieless JSON or HEAD request that receivesXSRF-TOKENalso receives its session, so the next POST no longer gets 419. Two registrations racing for one email create one account. - Images decode correctly at the sizes the framework allows. JPEGs above
about 22 megapixels decoded on no driver; they now decode up to the
budget. JPEG colours were off by about 6 levels, arithmetic-coded,
odd-sized 4:2:0 and 4:2:2, 4:4:0 and 4:1:1 JPEGs decoded wrong or not at
all, and small progressive JPEGs could fail. GIFs from ImageMagick and
Pillow decode, and the GIFs the default driver writes open in other
software. The
magickdriver processes and sizes only the first frame of an animation, as the default driver does, and reports a GIF's logical screen as its size. - Localization.
Accept-Languagenegotiation honours q-values:en;q=0.1, frpicksfr, and a language sent withq=0is never chosen.DATETIME()formats in the catalog's own locale. A catalog edit saved during a reload is picked up by the next one.Lang::hasis false for a message that has only attributes, matchingLang::get. A Fluent term and a message with the same name both resolve on the server, as in the browser. - Logging. A custom driver's failed write or flush, and a file channel
that cannot flush (a full disk), are reported once on stderr instead of
dropping lines silently.
LogChannel::stack([...]).level(...)filters every channel the stack lists. A refused secondinit_subscriberorinit_telemetryno longer changes the live file format or the default channel.Log::forget_channelafter rotation reopens the file in every stack that lists the channel. A default stack with several stdout channels writes an event when any of them keeps its level. Nested spans that share a field name log the inner value in the message and the context. - Markdown heading ids are unique, and process output keeps its
characters. A heading titled like a numbered duplicate (
Overview 2) no longer shares an anchor with a repeatedOverview. Streamed process output no longer drops a character split across reads after an invalid byte, andwait_untilsees a final incomplete character. - Payments, mail, notifications and queues.
PhoneNumberandCountryCodevalidate when deserialized, where invalid values were accepted anddigits()could panic.MailFake::assert_not_outgoingfails when the mailable was sent, not only queued. Thefilemail driver never overwrites a preview written in the same millisecond. Tagged Resend mail is accepted by Resend. Notification mail renders from the notification itself, sodata()no longer has to hold every fieldto_mailreads. An SQS overflow job whose first send went unanswered keeps its payload when the retries are refused, and when SQS took both an unanswered send and its retry, each message now carries its own payload copy, so acknowledging one no longer leaves the other unreadable. The Redis queue and the broadcast fanout work withredis://user:password@...andrediss://URLs, taking credentials, database and TLS from the URL. - Middleware, sessions, uploads and test helpers. A middleware group
reused by two sibling groups no longer fails with
CycleDetected. ARateLimitercounter that expired in the middle of a hit gets its expiry back, where it could refuse every later request until cleared. Flash keys containing_flash.new.or_flash.old.survive the next request, andSessionData::decrement(key, i64::MIN)saturates instead of panicking. A form body sent asApplication/X-WWW-Form-Urlencoded(any case) is read byRequest::input, CSRF, Pusher channel auth and identity rate limits.set_global_upload_spill_threshold(usize::MAX), the documented way to keep uploads in memory, no longer panics. The Inertia error page comparesAcceptqvalues to three decimals. A redirect on a route without a session keepsApp::flashvalues for the current response.TestResponse::assert_cookiematches only cookie names, not attributes such asPathorHttpOnly. - A Live page with several islands on SSE keeps its updates. When an
island's first event arrived before its subscribe answer, the browser
treated it as traffic for an unknown subscription, retired the shared
stream and showed every island on the page as "Updates degraded". Such an
event is now held, counted against
LIVE_ASYNC_MAX_QUEUED_EVENTS, and applied once that exact answer arrives, or dropped if the subscribe is refused; the same holds for the replacement subscribe that follows a failed island. A WebSocket transport still fails closed, as before. A document whose held and queued events pass the limit now reports the breach with the limit's key and reconnects, instead of degrading every island. - Payment webhooks, feature flags and RBAC work on Postgres, MySQL and
MariaDB. Their models used a text cast for native timestamp columns, so
every payment webhook answered 500,
set_flagand the feature admin failed, andRoleandPermissioncould not read a row the RBAC helpers wrote. They now read and write the native columns; text written on SQLite still reads back. - Job batches settle on Postgres. The documented
job_batchesschema declaresINTEGERcolumns, which Postgres stores as 32-bit, and the repository read them as 64-bit, so every settlement failed: the job ran again after each visibility timeout and the batch callbacks never fired. The repository reads either width, and the documented epoch columns are nowBIGINT; tables created from the earlier schema keep working. - The MariaDB vector store works against a real server.
similarlooked for the vector index in a form MariaDB never prints, so every call failed, and the tableensure_table_sqlemits could not be created because its key was too long for a vector index. The id column is nowVARBINARY(254), which also compares ids byte for byte as the other drivers do. - Native JSON columns have their own cast. The structured casts bind and
read text, which Postgres refuses for
jsonandjsonband MySQL forJSON, although their documentation said those columns worked. The newAsNativeJson<T>andAsOptionalNativeJson<T>store any serde type as JSON. TheAsBooldocumentation now names aBIGINTcolumn and sends a native boolean column to a plainboolfield. - SMTP mail goes out from the return path. A return path reached SMTP only as a header, so bounces still went to the author; the envelope sender is now the return path.
- Queued mail and queued notifications send. Nothing registered their jobs with the worker and the manuals never said to, so every one failed as an unknown job and dead-lettered, and with the sync driver the push itself failed.
- Queued and notification mail fire
MessageSendingandMessageSent. Only a direct send fired them, so switching toqueueor sending through a notification cut off audit and metrics listeners. - A Live primary button looks like the primary action. A
type="button"button with the default primary variant rendered as a secondary control, and so did dialog, sheet and drawer triggers. sumandavgof an integer column read on Postgres and MySQL. Postgres answersnumericand MySQLDECIMALfor them, whichsumandavgcould not read, so they failed there while passing on SQLite. They now read either: an integer sum exactly, refusing a fractional or out-of-range sum with an error that quotes it, andsum::<f64>of an integer column now reads on SQLite too.with_sumandwith_avgstored0.0on Postgres and MySQL; they now hold the value, and a value that is not numeric is an error instead of a silent zero.- Facebook sign-in receives the email. The Facebook provider requested a
bare
/me, for which the Graph API returns onlyidandname; it now namesid,name,emailandpicture. X requestsprofile_image_urlamong its user fields (#140). live:checkfinds unescaped output wherever a template writes it. It read|safefrom an expression's text and skipped{% let %}, so{% let y = x|safe %}{{ y }},x|safe|lowerandescape("none")passed. It now reads the parsed template and follows a raw value throughletandset, macro arguments, macros called as expressions, caller content, inherited blocks andsuper(), loops,if let, let chains andmatch, to the place it is written. A filter outside Askama's builtins and the framework's, a Rust macro in an expression, and a dynamic value in an unquoted attribute, anon*attribute orscriptorstyletext are reported as unproved, so a view that passed before can now need a change.live:checkhandles views with many conditionals. It counted every combination ofifblocks, so eight independent ones exceeded its limit; each conditional's branches are now checked once. Its limits are sized for real templates (4 MiB of source, 262,144 nodes) and configurable.live:checkreports the real column. Directive and markup diagnostics reported column 1; they now point at the attribute or tag, in the template that wrote it.- An action can dispatch more than 128 events. An action's outcome
refused more than 128 flash messages, events or effects; it now takes as
many as
LIVE_MAX_RESPONSE_ITEMSallows, 65,536 by default. - Reordering a long keyed list morphs in linear time. The morph looked up each keyed element in the list of moved elements, so reordering every row took time quadratic in the row count; 10,000 rows took about 67 ms and now take under 20 ms.
Security
- Input-only relationships stay out of JSON:API output. A relationship
marked
#[data(input_only, allow_include)]was linked and includable in responses; it is now never sent. - The environment is written only where that is sound.
Config::initandconfig::load_dotenvrefuse to write the process environment inside a Tokio runtime or after#[suprnova::main]loaded it, where another thread could read it mid-write. A failed load restores the real system values and registers no config. - Route bindings and pivot extras respect what models declare.
RouteParam<Model>ignored global scopes on models withoutsoft_deletes, so a guessed id of another tenant's row bound to the handler; the binding now applies every global scope, and a hidden row is a 404.attach_withwrote pivot extras past the pivot model's casts, so anAsEncryptedcolumn was stored as plaintext and anAsHashedone unhashed; extras now go through the pivot's casts and mutators, and an extra that does not decode into its field is a validation error. - RenderCache never stores or reuses a personalized page as shared. Work
a handler joined beside an identity-bound island mount (
tokio::join!) had its principal, session and table reads dropped from the stitched shell's report, so a personalized shell could be stored as public; those reads now count.PrivateCachedresponses sendCache-Control: private, no-cacheinstead ofprivate, max-age, which let a browser show the previous account's page to the next account on the same browser. Oversized Redis hint payloads are dropped before they are copied or queued. - Redis credentials stay out of the boot log. When Redis was unreachable
at boot, the cache error held the whole
REDIS_URL, password included, andCacheConfigandCacheConfigBuilderprinted it when debug-formatted. The error now names only the host and port or socket path, and the configurations print the URL asredis://<redacted>. - Second-factor codes are rate limited and single use.
TwoFactor::verifyandconsume_recovery_codeignored the account lockout, so a caller with the password could guess TOTP codes without limit; both now refuse while the second factor is locked, and every framework login is refused before it spends a code. A confirmation code and a TOTP code straddling a timestep are accepted once, andconfirmconfirms only the secret whose code was checked, in the framework and in Magnetar. Second-factor failures are counted in a table that no password identity can reach, so a decoy account named after the second-factor key can neither clear nor lock it. A password reset during the password check cancels the sign-in or challenge. HTTP Basic once,Auth::onceandonce_using_idrefuse an account with a Magnetar second factor, and Magnetar's password, magic link, passkey and OAuth sign-ins refuse an account with framework TOTP. A remembered framework login is refused before it issues a credential, and account flows write only the verified-at or password column. - Local disks stay inside their root. On Unix, a directory inside a local disk root swapped for a symlink during an operation could redirect a read, write, copy, rename, delete, listing or publish outside the root. Every path is now resolved one component at a time without following symlinks, and each operation runs relative to the directory it resolved.
- Cached feature flags stay per identity. Two identities whose user and team strings joined to the same text could share a cached flag decision. The cache key now keeps each part separate.
- Fanout URL errors no longer print credentials. A broadcasting fanout URL that failed to parse was copied into the error message, password included. The error now names the problem without the URL.
- A JSON login is rate limited by its address.
identity_keyandnames_identityignored JSON bodies, so a JSON login was keyed on the caller's IP and a?email=decoy opened a fresh per-address bucket on each request. A top-level string field of a JSON object body now names the identity under the same query-versus-body rule as a form field. - An SVG allowlist accepts only SVG. A
MimeTypeallowlist namingimage/svg+xmlaccepted any non-markup text declared as SVG, script included, and refused real SVG files. A part now passes only when its root element is<svg>; anything else declared as SVG fails as the wrong type. - A route uses the guard that authenticated it. Behind a guard other
than the default, the email-verified gate, the role and permission
middleware, the Live principal and render-cache identity reads all used
the default guard's user, so a verified or privileged default-guard user
let another guard's user through, and a page built for one guard could be
served from cache to a visitor without that sign-in. A second token guard
over another provider answered with the first guard's user. Each now reads
the user of the route's own guard through that guard's provider. Live
gated actions, uploads and subscriptions,
EmailVerification::verifyand the Pusher user and presence endpoints do the same: behindAuthMiddleware::for_guard(name)they act for that guard's user, as<guard>:<id>(default-guard principals are unchanged), a named guard's logout ends that guard's Live memberships, and a stream with a:principaltopic is refused behind a non-default guard. - Encoded cookie names cannot stand in for prefixed cookies. A cookie
named
%5F%5FHost-suprnova_sessionresumed the__Host-session; a prefix that appears only after decoding is now dropped. - A verification link verifies only the address it was sent to. Changing the account's email no longer lets an old link verify the new address.
- Password reset checks the token before hashing. A dead or made-up
token made the server compute an Argon2id hash first, in the framework's
reset flow and in Magnetar's
PasswordManagementService. - A session that loses its Magnetar authority ends its Live memberships on this node, so it stops receiving events.
- An image cannot allocate past its decode budget. A crafted PNG
inflated past
IMAGE_MAX_ALLOC_BYTES, a lossless WebP's prefix-code tables were unbounded, a JPEG could be measured at one frame header and decoded at another, and path and disk sources were read into memory before the size check. Each is now counted against the budget before the memory is taken. - A JPEG's Extended XMP cannot hold a core. A JPEG whose Extended XMP
segments would make the decoder's reassembly read more than
IMAGE_MAX_ALLOC_BYTESis refused before decoding; 100,000 stalled segments used to hold a core for minutes. - The mock payment provider refuses unsigned webhooks outside
development. It accepted them when the application registered a
production or staging
AppConfigin code withAPP_ENVunset; it now requires both the configured environment andAPP_ENVto be local, development or testing. - Queued notification events carry only
data(). The queuedNotificationSending,NotificationSentandNotificationFailedevents carried the whole serialized notification, including fields kept out ofdata()such as reset tokens. - Vendor API keys stay with their vendor. Pinecone and the HTTP mail
drivers followed redirects, forwarding
Api-Keyandx-postmark-server-tokento another origin. Web push transport errors no longer carry the subscription endpoint URL into logs andNotificationFailed. - CORS patterns anchor every alternative.
allow_origin_patternsanchored only the first and last alternative of a pattern such asa|b, sohttps://app.example.evil.testmatchedhttps://app\.example|...and got a credentialed allow. Every alternative must now match the whole origin. - Rate limits cannot be sidestepped. On the Redis limiter, a
shorter-window quota sharing a key with a longer one deleted the longer
quota's history; history now lasts for the longest window used on the key,
as the memory driver already did. An identity-keyed limit read the query
string or the body, so
?email=decoyor a blank?email=reached a body address under a fresh quota; both are now read, and a request that names two different addresses shares one{prefix}:{field}-ambiguousbucket. MimeTypesniffs before it trusts the header. Script text, or markup hidden after 16 KiB of whitespace, passed an image allowlist on a spoofedContent-Type. The header now counts only for types without magic bytes, such astext/csv.- An Inertia validation redirect stays on the host. A same-host
Referersuch ashttps://app.test//evil.test/xsent the redirect to another host; it now falls back to the previous URL. - Signed URLs sign the order of a repeated parameter. Swapping the
values of a repeated key (
?mode=a&mode=bto?mode=b&mode=a) kept the signature valid while changing what the handler read. URLs minted before still verify. - Mail headers and recipients cannot be injected. Postmark and Mailgun
received recipient lists joined from unquoted display names, so a name
such as
attacker@example.com, Victimadded a recipient, and SMTP and the file transport wrote header names carrying CR, LF or NUL verbatim. Every transport now builds addresses and headers through one validating serializer: an address is exactly one RFC 5322 address with its display name quoted when needed, a header name follows the RFC 5322 grammar and is at most 76 bytes, and a header value, the subject included, refuses control characters other than tab.
3.1.0 - 2026-10-03
Added
- Heap profiling. With the framework's
heap-profilingfeature an application profiles its heap with dhat: the framework installs dhat's allocator,#[suprnova::main]starts the profiler, and a command that finishes or a server that shuts down gracefully writesdhat-heap.json, or the fileSUPRNOVA_HEAP_PROFILEnames, for DHAT's viewer, and prints the bytes allocated, the peak and the heap left at the end. Without the feature no dhat code is compiled. The workspace and new applications have aprofilingCargo profile, the release profile with debug symbols, and new applications aheap-profilingfeature that turns on the framework's. - The in-memory cache sweeps its expired entries. The cache the
framework binds removes every entry whose time is up every
CACHE_SWEEP_INTERVALseconds (60 unless set; 0 turns it off), so keys written once and never read again no longer stay for the life of the process.InMemoryCache::with_periodic_sweepbuilds such a cache, andCacheConfig::sweep_intervalsets the interval in code. - Schema dumps.
suprnova schema:dumpwrites the database's schema and its migration ledger todatabase/schema/<engine>-schema.sql, withpg_dump,mysqldumpormariadb-dump, or straight from SQLite.migrate,migrate:fresh,serveandTestDatabase::freshload it into a database that has run no migration, then run only the newer migrations;--schema-pathnames another file.--prunedeletes the migrations the dump records and keeps each name as aPrunedMigration, which fails with an error if a database ever needs to run it. - Strings and numbers.
Str::slug,Str::mask,Str::limit,Str::limit_wordsandStr::excerptwork in characters, never bytes.Str::pluralandStr::singularfollow the language of the current locale with doctrine/inflector's rules for English, French, Norwegian Bokmål, Portuguese, Spanish and Turkish, English for any other, and keep the word's case.Lang::percentagewrites a percentage as the locale does, andLang::abbreviateshortens a number to1.23Mwith the locale's digits. - A Redis facade.
Redis::connection("default")reachesREDIS_URL, andRedis::definenames other connections in the bootstrap, orRedis::define_clientwith a client built elsewhere. A connection opens on its first command and opens again after the server drops it;Redis::purgeandRedis::connectionsmanage them. The common commands are typed methods (get,set,incr,hgetall,lrange,zadd,scanand the rest),commandruns any other and returns aRedisValue, refusing, as pipelines and transactions do, those that would change the shared connection (SUBSCRIBE,MULTI,SELECT,CLIENT REPLYand the like), andclient()gives therediscrate's connection, now re-exported assuprnova::redis. Reads are sent again after a lost connection, asREDIS_COMMAND_RETRIESsays; writes never are. A subscription the server closes subscribes again.rediss://URLs connect over TLS, for the facade and for the cache, queue and rate limiter URLs; the framework installs rustls'sringprovider unless the application installed one.pipelinesends its commands before reading a reply andtransactionwraps them inMULTIandEXEC.subscribe,psubscribeand the blocking commands (blpop,brpop,blmove,brpoplpush,bzpopmin,bzpopmax) each run on a connection of their own. WithRedis::enable_events,Redis::listenandRedis::listen_for_failureshear every command outside a pipeline or a transaction. - Log channels.
LOG_CHANNELnames the channeltracing's events go to, stillstdoutunless set:stderr(orerrorlog),single(storage/logs/suprnova.log),daily(a file a day, keepingLOG_DAILY_DAYS, 14),monthly(keeping 3),syslog(the local socket,LOG_SYSLOG_FACILITY),null, andstack(the channelsLOG_STACKlists).Log::defineadds a channel in the bootstrap andLog::extenda driver, through theLogSinktrait.Log::channel,Log::stackandLog::buildreturn a logger with Laravel's eight levels and a JSON context whose values fill{key}placeholders; a broken channel in a stack stops none of the others. File channels flush at once for errors, within a second otherwise, and onLog::flushand shutdown.MAIL_LOG_CHANNELroutes thelogmail transport. A channel that does not exist fails boot.logging::build_subscriberbuilds the subscriber the server installs, for an application or a test that installs its own. - A Process facade.
Process::command(["git", "status"])runs a program with its arguments, each passed as it is through no shell, andProcess::shell("npm ci && npm run build")runs a command line through the system shell, as Laravel runs a string command.runreturns the exit code and the captured output; a nonzero exit is a failed result, andthrowmakes it an error.path,env,input,quietly,tty, an output callback, a timeout (60 seconds unless set) and an idle timeout are options. A timeout, an idle timeout,stop, or dropping a started process or the future ofrunkills the program with every process it started: its process group on Unix, its tree for attyprocess and on Windows. A started process's timeouts hold whether or not anything waits on it. Results keep the raw bytes as well as the text.startreturns the program running;Process::pool()runs processes side by side with an optional concurrency limit, andProcess::pipe()feeds each output to the next input.Process::fake()stops every process in a test, answers by pattern,describeand sequence, and records each run for the assertions. - An SQS queue driver.
QUEUE_DRIVER=sqsqueues jobs on Amazon SQS standard queues, configured by Laravel's variables:SQS_PREFIX,SQS_QUEUEandSQS_SUFFIXbuild the queue URL,AWS_DEFAULT_REGION(orAWS_REGION) names the region, andAWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEYsign the requests, or the default credential chain of AWS when they are not set.SQS_ENDPOINTpoints it at LocalStack or ElasticMQ, andQUEUE_CONNECTIONSand failover acceptsqs. A job goes to the queue it names, and a worker receives from the queues--queuelists, or fromSQS_QUEUE. Anackcounts an attempt and a release does not, as on the other drivers, and a delay longer than the 15 minutes SQS allows still holds. WithSQS_OVERFLOW_ENABLED=true, a job of 1 MiB or more is stored on a disk and SQS carries a pointer to it. The boot fails with no region, with a queue name and noSQS_PREFIX, and for a FIFO queue. A receive waits up toSQS_WAIT_TIME_SECONDS(default- for a message, a throttled or failed request is tried up to three times,
and
SqsConfigwithSqsQueueDriver::newbuilds a driver in code for a second connection.SqsQueueDriver::callsends any other SQS action. The driver is behind thequeue-sqsfeature, on by default.
- for a message, a throttled or failed request is tried up to three times,
and
- A default disk.
Storage::default_disk()returns the diskStorage::set_default_disknames in code, or elseFILESYSTEM_DISK. When the named disk is not registered once the bootstrap has run,filesystem::bootstrap_from_envfails and the server does not boot. With nothing named there is no default, anddefault_disk()returns an error that namesFILESYSTEM_DISK. Calls that name their disk are unchanged. What to check when you upgrade:FILESYSTEM_DISKwas not read before, so an application that carriesFILESYSTEM_DISK=localfrom a Laravel.envnow refuses to boot unless it registers a disk namedlocal: register it, or remove the variable. An application that callsfilesystem::bootstrap_from_envin its own bootstrap calls it after it registers its disks and sets the default. - A failed request's error report reaches
TestResponse. A response the framework builds from an error carries anErrorReportin its in-process extensions: the error and each of its sources, or, for a panic the panic boundary caught, the panic message and the location it was raised at. That covers aFrameworkErrora handler or middleware returns, a panic on an HTTP route or in a WebSocket upgrade's middleware, the 5xx the framework's session, session lock, throttle, rate limit, login throttle, timeout, and RenderCache middleware answer a failure with, and the 5xx of the payment webhook route and of the Live endpoints when the endpoint holds the error. The report never reaches a header or the body, so what a client receives is unchanged; with debug on, a 5xx body still carriesdebug_messageas before. The newTestResponse::from_responsebuilds from the responsehandle_requestreturns and keeps the report, and every failing assertion then ends with anerror report:section, so a 500 says why it happened.assert_inertia()and theAssertableInertiaassertions print it too, and the Inertia error page and validation redirect keep the report of the response they replace.TestResponse::error_reportandHttpResponse::error_reportexpose it. The report belongs to its own response, so two requests in flight in one test process never mix their errors. To find a panic's location, the framework wraps the process panic hook once and calls the hook it replaced. This landed on main after thev3.0.0tag. - A development error page. With debug on, a 5xx the framework
built from an error or a caught panic, sent to a browser (an
Acceptthat liststext/html) or an Inertia visit, becomes one HTML document with the same status: the error chain or the panic message and location, the stack frames recorded where the error was created, and the request's method, path, query, headers, matched route pattern and request id. The application's frames are shown; the frames of the framework, the async runtime, other dependencies and the standard library are collapsed behind a count. TheFrameworkErrorandAppErrorconstructors, theFromconversions intoFrameworkError, theabort_with,abort_ifandabort_unlesshelpers and the#[domain_error]conversions are now#[track_caller], so the page names the line that called them even in a build without debug info; a call from insideResult::map_errnames that line of the toolchain, and the frames name the handler. Without debug info, the handler and middleware the framework's dispatch polls are the application's frames. The page redacts theAuthorization,Proxy-Authorization,CookieandSet-Cookieheaders, every header and query parameter whose name containstoken,secret,password,keyorsignature, every such parameter in any other shown value (aRefererorX-Original-URIthat repeats the URL), and the password of a URL, and it never shows the request body, environment variables or configuration values. It loads nothing and runs no script, so it renders when the frontend build, the Vite manifest or Inertia is what failed, and it carriesCache-Control: no-storeand aContent-Security-Policythat allows no script. For those responses it takes the place of the app's Inertia error page. A JSON client keeps the JSON body withdebug_message, a 4xx and a 5xx built without an error are unchanged, and with debug off the framework records no frames, captures nothing about the request, and sends every response as before. This landed on main after thev3.0.0tag. - A Pusher-protocol broadcast driver.
PusherBroadcastHubpublishes broadcasts through the REST API that Pusher Channels, Soketi and Laravel Reverb share, and still delivers them to in-process subscribers, so aws!broadcasting route keeps working.PusherConfig::from_env()reads Laravel'sPUSHER_*variables, andfrom_env_prefix("REVERB")reads Reverb's.pusher_channel_authandpusher_user_authanswer Laravel Echo's authorization requests for private, presence and end-to-end encrypted channels. The newChannel::visibilitypicks each channel's Pusher name and defaults to private, so a channel that restrictsauthorizecan never leak through a public Pusher channel. A name that would read as another channel's Pusher name, and an encrypted presence channel, are refused rather than published, and an invalid configuration fails when the hub is built. Publishing to an encrypted channel without a master key is an error, never a plaintext send. This landed on main after thev3.0.0tag (#130). InertiaPropsandDatafollow serde's field names. Both derives honor#[serde(rename_all = "...")]on the struct, andrename,skip,skip_serializingandskip_deserializingon a field, including the splitserialize = .., deserialize = ..forms; any other serde attribute is a compile error. The names reach everything the client sees: Inertia props and partial reloads, the?include=allowlist, JSON:API members, request input, route-parameter injection, andsuprnova generate-types. Validation errors of aData,#[derive(FormRequest)]or#[request]struct are keyed by the input names at every nested level, soPrecognition-Validate-Onlymatches what the client sent, and a message labelsunitPriceas "unit price", as Laravel does. A raw identifier such asr#typeis sent and read astype. A plain nested#[derive(Deserialize, Validate)]struct registers its names with the new#[derive(suprnova::InputNames)]. This landed on main after thev3.0.0tag (#124). Two consequences for existing code. A#[serde(...)]attribute on anInertiaPropsorDatastruct used to compile only next to another derive that registersserde(such asschemars), and did nothing there; it now takes effect, and an attribute the derive does not apply is a compile error. A localized validation message labels every key snake-cased, so a hand-written keyuserIDreads "user i d", as in Laravel; snake_case keys read as before. A#[json_resource]struct may no longer send an attribute or relationship namedtypeorid, which JSON:API reserves: a struct with a customid_fieldand a field namedid, or a fieldr#type(sent asr#typebefore), is now a compile error that asks for a#[serde(rename = "...")].- The schema builder covers the rest of a Laravel migration.
unsigned_id()andunsigned_foreign_id()create Laravel'sBIGINT UNSIGNEDkeys on MySQL, so a new table can point a foreign key at an existing Laravel table, and a model reads them withkey_type = "u64". New columns:tiny_integer, theunsigned_integers,medium_text,long_text,enumeration(Laravel'senum) andremember_token. New modifiers:.unsigned(),.index(),.primary(),.precision(n),.use_current()and.after(column).t.primary(&[..])makes a composite primary key,t.foreign(column)a foreign key on a column declared on its own,.name(..)names a key, anddrop_constrained_foreign_iddrops a key with its column. The actions have Laravel's shorthands,cascade_on_delete()and the rest. Where the databases differ the builder does what Laravel does:unsignedandafterapply on MySQL only, and an enumeration is a string with aCHECKoff MySQL. This landed on main after thev3.0.0tag (#122). - Native date-time columns for models.
AsNativeDateTimeandAsOptionalNativeDateTimestore aDateTime<Utc>in a column that keeps the zone (timestamp with time zoneon Postgres,TIMESTAMPorDATETIMEon MySQL);AsNaiveDateTimeandAsOptionalNaiveDateTimestore the UTC wall clock in one without a zone, the shape Laravel'stimestamps()creates on Postgres. The schema builder gains Laravel'stimestamps_tz(),soft_deletes_tz(),datetimes()andsoft_deletes_datetime()to create them. Automatic timestamps,touch(), soft deletes and the touch of an owner all store through the declared cast, and query comparisons (filter,where_between,where_date,update_all,where_has) bind through it, so Postgres gets a native parameter. A model may declarecreated_atandupdated_atasOption<DateTime<Utc>>for a table another application leaves NULL.suprnova generate-typesnow emits chrono's date and time types asstringinstead ofunknown. This landed on main after thev3.0.0tag. - Laravel's
exists,accepted,digits,date_format, date comparison,prohibited,missingandexclude_ifrules.Existschecks that a value names a row, scoped withwhere_eq;check_valuebinds a typed id, which Postgres needs for an integer column, andcheck_eachchecks every element of an array, one query per distinct value, with each failure underfield.<index>.Accepted,Digits,DateFormat(chrono's format syntax, checked by a round trip like Laravel's),After::new,AfterOrEqual::new,Before::newandBeforeOrEqual::new(against a fixed date,Now,Today,Tomorrow,Yesterdayor another field, with.format(..)for a field that is not ISO 8601),Prohibited,Missing,ExcludeIfandExcludeUnlessjoin the built-in rules.validate!now runs a row's rules in order, each expression evaluated once, and stops at an exclusion, as Laravel does. This landed on main after thev3.0.0tag. - A Data Object runs
validate!and database rules. The derive writes a Data Object'sFormRequestimpl, so it had no place for cross-field rules or forUniqueandExists.#[data(after_validation = "fn")]and#[data(after_validation_async = "fn")]name the functions that impl calls, and the impl afrom_route_paramfield selects now runs the async stage too. That impl now calls the hooks through the trait, so an inherentafter_validationmethod on such a Data Object, which it used to call by accident, no longer runs: name it with the attribute. The derive refuses both attributes on a struct that gets noFormRequestimpl. This landed on main after thev3.0.0tag. - Joins and the remaining
wherehelpers on both query builders.DB::tableand model queries gainjoin,left_join,right_joinandcross_joinwith table aliases; closure conditions combiningon,or_on,whereandor_where;join_subandleft_join_subagainst another builder;where_existsandwhere_not_exists;where_any,where_allandwhere_nonewith theiror_forms; subqueries inwhere_inandwhere_not_in; theor_where_*family; andreorder. Every value stays bound and every identifier is quoted for the backend, so reports and exports no longer need raw SQL. A joined model query selects its own table's columns, so the joined table'sidnever overwrites the model's, and its soft-delete filter names its table.DB::tablenow quotes identifiers in every statement, so on Postgres a mixed-case name is case-sensitive, as in Laravel. An update or delete on a query with a join is refused rather than run without the join. This landed on main after thev3.0.0tag (#125, #128). - File and download responses.
HttpResponse::fileshows a file inline,HttpResponse::downloadsends it as an attachment, andHttpResponse::download_bytessends generated bytes;Storage::responseandStorage::downloaddo the same for a path on a named disk, through the disk's path guard. Files stream, the content type comes from the extension, a missing file answers 404 and a path the guard refuses 403. EveryContent-Dispositionfollows RFC 6266, with an ASCII fallback transliterated as Laravel does and afilename*for the full name, soCertificat·Joan Pérez.pdfarrives intact and no name can inject a header. This landed on main after thev3.0.0tag (#126). - A configurable Inertia page lookup.
inertia_response!reads an optional[package.metadata.suprnova.inertia]table from the application'sCargo.toml:pages_dirmoves the pages directory, andpage_filemaps a component name to its file with{dir},{name}and thelower,kebabandsnakefilters. Angular and other layouts keep the compile-time page check, and a missing page names the exact path the macro looked for. Without the table nothing changes. This landed on main after thev3.0.0tag (#129). - The queue fake can let jobs through and records raw pushes.
Queue::fake_exceptandQueueFakeGuard::exceptrecord every job but the named ones, which reach the real queue.Queue::push_rawpushes an envelope's JSON form, and under the fakeraw_pushesandpushed_rawread those pushes back.assert_pushed_without_chainfails for a job pushed with a chain. A chain whose first jobexceptnames runs on the real queue, and each later link is recorded unlessexceptnames it too. This landed on main after thev3.0.0tag. - Declarative authorization on handlers.
#[authorize("update-post", post)]on a#[handler]checks the gate against the model the route binds topost, and#[authorize("create-post", Post)]checks it against the type, for the user of the guard the route authenticated with. The check runs after route model binding and before the request body is read, so a forgottenGate::authorizecall can no longer leave a route open. Policies, async gates and the RBAC gate bridge all answer it. A guest gets 401, a denial 403, anddeny_as_not_found()404. A parameter name the handler does not take fails to compile. This landed on main after thev3.0.0tag (#127). - Model changes after a save,
sync_without_detaching, and after-commit callbacks. A model reports what its last update changed (was_changed,was_changed_any,get_changes), andget_originalandget_raw_originalreturn the loaded values while itsupdatedandsavedobservers run, as Laravel's do; once the save returns, the original is the saved row. An encrypted column counts as changed only when its decrypted value changed.sync_without_detachingattaches pivot rows without touching the existing ones.DB::after_commitruns a callback after the ambientDB::transactioncommits, and never on rollback; a transaction started withDB::begin_transactiontakes its owntx.after_commitandQueue::push_after_commit_with_tx, because ambient code is outside that transaction. This landed on main after thev3.0.0tag (#128).
Changed
- Less memory for the same work. Model events are built only when a
listener, a fake or a deferral will see them, so a query no longer
copies every row it reads for a
Retrievedevent nobody hears. Eager loading reads each key from its field instead of serializing the whole row, and a runtime cast converts its column where it sits. The first Inertia page is written into one buffer, a file download reads each chunk straight into the bytes it sends, a body sent in several frames is held at its length, CORS path patterns are compiled once per configuration, and a broadcast's last channel takes the payload instead of a copy. A queue job receives its envelope's payload, the SQS driver parses a message once, sends a retried request's bytes without copying them and holds a reservation's body rather than a second envelope.Context::push, image transformations and encoding, filesystemappendandprepend,Collection::pluck, the in-memory vector search, the feature-flag snapshot, Mailgun's form, composite render-cache shells and the docs builder each keep or copy less. A process result holds its output once when the output is valid UTF-8. In the Live engine a mount no longer copies its signed snapshot, action arguments are kept once, a full upload read returns the store's bytes, and the resource queue compacts in place. The Live browser runtime reads a server-sent event stream without copying what it already holds for every chunk, and an upload control response no longer allocates 16 KiB. Magnetar writes hex into one buffer, and its single-flight map holds a key only while a caller holds or waits on it. Every response, file, digest and snapshot is byte for byte what it was. CacheConfighas asweep_intervalfield. Code that builds aCacheConfigas a struct literal has to set it, or useCacheConfig::builder(), which defaults it to 60.DynCasthas afrom_storage_json_ownedmethod that converts a stored value the caller no longer needs. Its default callsfrom_storage_json; a cast whose in-memory value is the stored value returns it without copying.
Fixed
- A workflow step can take an integer argument.
#[workflow_step]handed the step's body to the workflow context in a closure that borrowed its arguments, and the context needs one it can keep, so a step taking aCopyargument such asuser_id: i64failed to compile with E0373 ("closure may outlive the current function"). The closure now takes its arguments by value. - Workers wait for their queued listeners.
queue:work,schedule:workandworkflow:worknow wait, up to ten seconds, for the queued event listeners still running when they stop, as the server does, andschedule:rundoes once its tasks have run; returning dropped them part way. Cache::bootstrapkeeps the cache store the application bound, as the localization chapter says it does, instead of replacing it at boot.- The event dispatcher forgets its finished queued listeners as it starts new ones; it kept every one until shutdown.
DB::flush_query_logreleases the log's buffer rather than keeping its capacity.- The in-memory vector search no longer panics on a NaN score; such an item ranks below every other.
- A
#[json_resource]keeps its attributes in declaration order when it drops a missing one; the last attribute used to move into its place. - The brute-force lockout map sweeps once each time it doubles. With more than 1,024 current lockouts it swept on every new lockout.
- The toast region lets go of toasts a morph removed, which it timed and later dismissed for the life of the page, and resumes its timers when the focused toast is removed or the pointer has left it without the region hearing it.
- The Live browser runtime reads a network chunk larger than one record when the chunk holds only complete records; it ended the stream.
- The Live chart follows the document's theme.
render_chartdrew its SVG with charts-rs's light theme, a white background and fixed colors and font, so in a dark document the chart showed as a white box. The SVG now has a transparent background and no color or font of its own: its text, axis, grid and series carry classes that the chart component's stylesheet colors from--sn-tokens, and the chart's text takes the--sn-font-sansfont. Series take the new--sn-color-chart-1to--sn-color-chart-6palette in order, defined for light and dark and mapped in the Tailwind preset, and a seventh series starts the palette again. An application that vendored the chart keeps its old stylesheet, which has no rule for these classes, so every series, axis and grid line draws in the text color. Runsuprnova live:add chartto take the fix into it. This fix landed on main after thev3.0.0tag. - A cached render whose COMMIT fails answers 500 without a panic. When
a cache-miss render's handler ran and the database then refused the
render transaction's COMMIT (a deferred constraint, a dropped
connection), the render cache took the failure for a transaction that
never opened: a debug build panicked, and the log said nothing about the
commit. It now logs the database error under
suprnova::databaseand answers the same 500, because the handler's writes rolled back and the rendered page would claim they landed. A render transaction that cannot open still renders uncached, as before. This fix landed on main after thev3.0.0tag. - A savepoint can be named with a reserved word.
tx.savepoint("inner")failed with a syntax error on PostgreSQL and MySQL, because the validated name went into the statement unquoted. Savepoint names are now quoted for the backend; they stay case-insensitive. This fix landed on main after thev3.0.0tag. - The sync queue driver runs a whole chain.
SyncQueueDriverran a chain's first job and dropped every later link. It now runs the chain inline, link by link, as Laravel's sync queue does; a link that fails returns its error and the rest of the chain does not run. This fix landed on main after thev3.0.0tag. authorize_resourcechecks the user of the route's guard. On a route whoseAuthMiddlewarenames a guard other than the default,authorize_resourcechecked the default guard's user instead of the one the route authenticated, so that user was refused. It now checks the route guard's user, as Laravel'scanmiddleware does. This fix landed on main after thev3.0.0tag (#127).- A cached page that reads through a raw fragment is never served
stale. A
select_raw,where_raw,filter_rawororder_by_rawon a model query can read a table the query doesn't name, but the render cache stored the page anyway, so a write to that table left it stale. A query carrying a raw fragment now keeps the page out of the cache, as rawDB::selectdoes; the page is still served. Aselect_rawthat is a bare number, such asselect_raw("1"), doesn't count. This fix landed on main after thev3.0.0tag. - A destructured route parameter binds. A handler parameter written
RouteParam(user): RouteParam<User>, as theRouteParamdocs show, looked up a route parameter namedparamand answered 400 to every request. It now reads the parameter its binding names, and a pattern with no single binding is a compile error. This fix landed on main after thev3.0.0tag. - SQLite rows keep computed columns. An aggregate or
select_rawexpression came back missing fromDB::tableandDB::selectrows on SQLite, because SQLite declares no type for a computed column. Such a column is now read by its value's runtime type. This fix landed on main after thev3.0.0tag. - A union arm keeps its soft-delete and scope filters. A union of model
queries rendered each arm's
WHEREwithout its scopes, so soft-deleted rows came back. This fix landed on main after thev3.0.0tag. - A page cached from
where_hassees writes to the related table.has,where_has,doesnt_haveandwhere_relationdid not record the related or pivot table for the render cache, so a write there left the cached page stale. This fix landed on main after thev3.0.0tag. - The notifications table ships as a migration. The manual said
suprnova migratecreates it, but the schema was a SQL file only the framework's own tests loaded, so the database channel failed on its first write in a fresh app. Registersuprnova::notifications::migrations::CreateNotificationsTablein yourMigrator: it creates the same table and indexes, and running it over a table you created by hand from the old SQL file is safe on every engine. The SQL file is gone. This fix landed on main after thev3.0.0tag (#134). - Nullable JSON columns have casts.
AsJson,AsArray,AsObject,AsCollectionandAsArrayObjectstore a non-null string, soAsJson<Option<T>>wrote the textnullinstead of SQLNULL, and a row whose column wasNULLfailed to load.AsOptionalJson,AsOptionalArray,AsOptionalObject,AsOptionalCollectionandAsOptionalArrayObjectmapNonetoNULLand back, and store a value exactly as their non-optional cast does. This fix landed on main after thev3.0.0tag (#133). SESSION_TABLEnames the session table.SessionConfig::table_namewas read and then ignored: the database session driver always usedsessions. The driver now reads and writes the configured table,DatabaseSessionDriver::with_tablebuilds one over another table, andConfig::initrefuses a name that is not 1 to 63 ASCII letters, digits or underscores starting with a letter or underscore. What you have to change: an app that already setSESSION_TABLEnow stores its sessions in that table, which its migration must create, and an emptySESSION_TABLEnow fails boot. The driver also stops logging a session id when it skips a write, and the content of a stored payload it cannot parse. This fix landed on main after thev3.0.0tag (#132).- Re-running a framework migration no longer fails on an existing index.
The workflow and RenderCache migrations relied on
IF NOT EXISTS, which MySQL and MariaDB drop fromCREATE INDEX, and the payments, features and RBAC migrations created their indexes without it, so running one over tables that already existed failed with a duplicate index and blocked every migration after it. Each framework migration now creates an index only when it is missing, with the same columns and uniqueness as before. This fix landed on main after thev3.0.0tag (#136). - A
Dataobject with a route-parameter field answers 422 for a body that does not fit. Its extractor answered 400 where the default extractor answers 422 for the same malformed or unknown-key body. This fix landed on main after thev3.0.0tag. - A
Datafield may be namedkeyormap. The generatedDeserializenamed its locals after the fields, so such a field shadowed the visitor's own variables and the struct failed to compile. This fix landed on main after thev3.0.0tag. has,where_hasandwhere_relationwork through aBelongsTorelation. The existence query compared the related table's key with the foreign key as if the relation were aHasMany, so every existence query through aBelongsTofailed with an unknown column. It now joins the related row's owner key to the parent's foreign key. This fix landed on main after thev3.0.0tag.- A model declared beside
use sea_orm_migration::prelude::*compiles. That prelude bringsExprTraitinto scope, whosemaxandis_nulltook over calls the#[model]macro emitted for relation counts andMorphTorelations. The macro now names those methods by path. This fix landed on main after thev3.0.0tag. - Persisting a replica stamps its timestamps.
replicateresetscreated_atandupdated_atfor the insert to fill, butpersistwrote them as built: 1970-01-01, or NULL for an optional field. It now stamps a timestamp its builder left unset, ascreatedoes, and keeps one the builder set, so a factory can still backdate a row. This fix landed on main after thev3.0.0tag. - Touching an owner writes the owner's own date-time storage. The
touchescascade bound the time as RFC 3339 text whatever the owner'supdated_atcast stored, which Postgres refuses for a native date-time column. It now stores the time through the owner's cast. This fix landed on main after thev3.0.0tag. - The temporal casts' documentation said Postgres accepts RFC 3339 text
for a native column. It refuses a text parameter for
timestampandtimestamp with time zone; the module documentation now says so and points to the native casts. This fix landed on main after thev3.0.0tag. UniqueandExistskeep database errors out of the response. A database rule that could not run returned the driver's error as its validation message, and a validation message is rendered into the 422 body, so a client could read table names, column types and SQL. The rule now logs the cause under thesuprnova::validationtarget and fails the field withvalidation-unchecked. This fix landed on main after thev3.0.0tag.- Precognition keeps the errors of an array's elements. A
Precognition-Validate-Onlyheader namingtag_idsdropped the errors reported undertag_ids.0,tag_ids.1and so on, so a form validating the field saw success for an invalid array. A field now keeps the errors nested under it, andtag_ids.*matches the elements as Laravel's rule key does. This fix landed on main after thev3.0.0tag. - The date picker, upload, account menu and notification bell follow the
theme. Their stylesheets read
--sn-color-accentand--sn-color-on-accent, which the token stylesheet never defined, so the selected day, the upload progress bar, the avatar and the unread count fell back to inherited colors and ignored every theme. The token stylesheet now defines both, from--sn-color-primaryand--sn-color-primary-contrast, and the Tailwind preset maps them asaccentandon-accent. An application that vendored these components withlive:addneeds no change: the framework serves the corrected stylesheet. This fix landed on main after thev3.0.0tag. - A first
live:modeledit on a public seed promotes it. The browser runtime sends an immediatelive:modeledit on a public-seed island as a model synchronization with no action, and the action endpoint promoted a seed only for an action, so the first keystroke in such an island answered500. The endpoint now promotes the seed on that request, applies the proposals as it does on an instance, and runs no action. This fix landed on main after thev3.0.0tag. - The date picker's "Pick the parts" toggle no longer looks like a second
field. The base layer draws every
detailsas a bordered surface for the collapsible, and the date picker's disclosure inherited it, so an empty box sat under the date input. The disclosure is now a plain toggle; the year, month and day strips keep their borders. Runsuprnova live:add date-pickerto take the fix into an application that vendored the component. This fix landed on main after thev3.0.0tag. suprnova generate-typesnames and omits plain-struct keys the way serde does. A struct a prop reaches that derives serde'sSerializesends the keys its#[serde(...)]attributes give it, but the generator declared every field under its Rust name. It now leaves outskipandskip_serializingfields, declaresskip_serializing_iffields optional, names keys byrenameandrename_all(and theirserialize = ...forms), and drops ther#of a raw identifier. Other serde attributes, such asflattenandtransparent, are still not read. A key that is not an identifier is now quoted, which also makes a raw identifier on a derived struct valid TypeScript ("r#type", the key its derive sends).#[derive(Data)]and#[derive(InertiaProps)]structs keep their Rust names: their ownSerializenever reads#[serde(...)]. This fix landed on main after thev3.0.0tag.
3.0.0 - 2026-09-29
Added
FrameworkError::Timeouttells a passed deadline from a failure.WorkflowHandle::wait_with_timeoutdocumented a timeout error that did not exist and returnedFrameworkError::Internal, so a caller could not tell a workflow that is still running from a failed status query. The variant carries the deadline and what was awaited,FrameworkError::timeout(elapsed, message)builds one,is_timeout()asks for it, and it renders as504 Gateway Timeout.wait_with_timeoutandwait_with_optionsreturn it when the deadline fires.Queue::fake()andBus::fake()install their fakes. Every other facade hadfake(); these two had only the free functiontesting::install_fake(). Both return the same guard, and the free functions stay.- Failed-job commands:
queue:failed,queue:retry,queue:forget,queue:flushandqueue:prune-failed. The manual and the code's own docs sent operators to commands that did not exist; the failed-job store could only be reached from code. The application binary now has all five, and thesuprnovaCLI forwards them.queue:failedlists id, connection, queue, job, failure time and the first line of the error.queue:retrytakes one or more ids, orall.queue:flushdeletes every failed job, or with--hours Nthe ones older than that.queue:prune-failedis the same with--hoursdefaulting to 24. A command exits non-zero when an id names no failed job. - Queued mail and notifications can wait for the commit.
Mailable::after_commit(&self)andNotification::after_commit(&self)default tofalse. When one answerstrue,Mail::queue,Mail::laterandNotify::queueinsideDB::transactionpush at the commit, and a rollback discards the push, asJob::after_commitalready does for a job.QUEUE_AFTER_COMMIT=trueturns the same behavior on for every push in the process, as theafter_commitoption of a Laravel queue connection does;EnvelopeOverrides { after_commit: Some(false), .. }still sends one push ahead of the commit. - Queue connections select a driver. One process-global driver received
every push, and a job's connection was only a name on the lifecycle events.
Queue::register_connection(name, driver)now registers a named connection next to the default one thatQueue::set_driverinstalls, and a push goes to the connection it resolves to: a per-pushEnvelopeOverrides::connection, then aQueue::route, thenJob::connection(), then the default.Queue::push,push_with,later,bulkandpush_uniqueall resolve it, the jobs of a batch each go to their own connection, and a failed job is retried on the connection it failed on.queue:work --connection <name>andqueue::worker::run_worker_ondrain one connection, and the worker carries its name on its events and failed-job records.queue:pauseandqueue:resumetake--connection.Queue::connection(name)returns a connection's driver andQueue::connection_names()lists the registered ones;Queue::size()and the other counts and listings read the default connection. While no connection is registered nothing changes: every push reaches the one driver, and a connection name is a label. Once one is registered, a push to a name that is neither registered nor the default's is an error and pushes nothing, and a push that waits for a commit is refused before the commit. A chain runs on the connection of its first job, because the worker enqueues the next link in the step that settles the one before it;Queue::chain().dispatch()refuses a chain whose links resolve to different connections.QUEUE_CONNECTIONS=redis,databaseregisters one connection per entry from the environment, each named for its driver. One driver has one label: an entry that names the driverQUEUE_DRIVERselects is a second name for the default connection, so a pause or aQueue::forward_onset under either name reaches the whole queue, and an entry that would put a second connection over a Redis stream or a jobs table that is already in use is refused at boot. Contexttravels with queued work. A value added toContextduring a request was gone when a queued job, a queued mail or notification, or a queued event listener ran. A push now takes aContextSnapshotof the visible and hidden bags and stores it on the envelope, and the worker runs the job inside a scope restored from it. The snapshot is taken when the push is made, so a push that waits for a commit carries it too. The lifecycle events around the job, such asJobProcessing,JobProcessedandJobFailed, are dispatched in the same scope, so a listener reads what the job read and what the job added. Every link of a chain and every job of a batch gets the snapshot of the code that dispatched it, and a queued listener gets the snapshot of the dispatch. The work runs on a copy, so what a job adds reaches neither the request nor the next job, and every attempt starts from the snapshot. Under the sync driver the copy shadows the caller's context for the length of the job. The query bag does not travel, so a job run inline no longer reads the request's query parameters. A job queued while a request is served carries the request's id as_request_id, which the request middleware adds to the context; a push made outside a request with nothing in its context writes the envelope it wrote before.Context::dehydratingandContext::hydratedregister callbacks for the two ends, as Laravel's hooks of those names do, withContext::dehydrate,Context::hydrateandContext::restoredas the functions behind them.Envelopegains the public fieldcontext, so code that builds one with a struct literal has to name it; an envelope written before the field existed decodes without context. Hidden values reach the queue store and the failed-job store, because the job needs them. They do not reach a log: the envelope a worker logs when no failed-job store is bound carries no hidden context, and theDebugoutput ofContextSnapshotandContextStorenames hidden keys only, and that ofFailedJobgives the size of the envelope and not its text.ThrottleRequestsMiddleware::default(). The plainthrottlealias had no limit to register: every constructor asked for a limit, a window and a key prefix, and the manual registered the alias with adefault()that did not exist. The default is 60 requests a minute, counted for each signed-in user and for each client IP when nobody is signed in, the shape of Laravel's defaultapilimiter. The numbers areThrottleRequestsMiddleware::DEFAULT_MAX_ATTEMPTSandDEFAULT_DECAY_SECONDS. The user's bucket follows the user across routes, and the address's bucket is shared by every route;.prefix(...)gives a group of routes a budget of its own.RateLimitMiddleware::ip_based(max_requests, window). The per-IP limit that every login form and public API needs took a backendArc, aSlidingWindowConfigand a hand-written key closure, and the manual used anip_basedthat did not exist. It uses the rate limiter the application installed, the oneRATE_LIMIT_DRIVERselects, looked up when a request arrives, so the middleware can be built where routes are registered. The key is the addressRequest::ip()resolves through the trusted proxies, and it names the limit as well, so two limits with different numbers share no bucket. A request with no address to resolve gets a bucket of its own.on_backend_error,only_whenandkey_reads_bodychain onto it; when no limiter is installed the backend error policy decides.- Middleware by name on routes. Aliases and groups could be registered and
resolved, but no route took a name: every
.middleware(...)wanted a type, and nothing parsedthrottle:60,1. Routes, groups of routes and the macro builders now have.middleware_named("auth"), which takes an alias, an alias with arguments, or a group that adds every middleware of the group in order. The name is resolved when the route is registered, so a name that is not registered stops the boot and never a request;.try_middleware_named(...)returns the error.register_middleware_alias_with_args(name, |arguments| ...)registers an alias that reads the arguments after the colon, and a group may list such an alias.try_resolve_middleware_aliassays why an alias gave no middleware.ThrottleRequestsMiddleware::from_alias_argsis the factory for thethrottlealias:throttle,throttle:60,throttle:60,5,throttle:60,5,prefixandthrottle:apifor a named limiter. - Route groups take a name prefix and a controller. Every route in an
admin.group had to spell its full name, and every handler its full path.group!(...).name("admin.users.")now puts the prefix in front of the name of every route in the group, and a group inside adds its own after it; a route without a name stays without one.group!("/admin/users", controller = controllers::admin::users, { get!("/", index), post!("/", store) })names the module the handlers live in, so a route names its handler by function alone. A handler written as a path is taken as it is written, and a group inside names its own controller. The path prefix stays the first argument of the macro. - Optional route parameters and parameter constraints.
/posts/{id?}now matches/postsand/posts/42, and the handler finds noidon the short form. Several optional parameters fill from the left, the colon spelling/posts/:id?works, and an optional parameter can only be followed by optional ones. The route's middleware and name apply to every form, androute(...)leaves an optional segment out when it has no value. A route can hold a parameter to a constraint:.where_number("id"),.where_alpha,.where_alpha_numeric,.where_uuid,.where_ulid,.where_in("status", [...])and.where_pattern("year", "[0-9]{4}"), onRouterroutes and onget!,post!and the other route macros, where a constraint may name a parameter of the group's prefix. A value the constraint refuses is a 404, as if the route had not matched, and neither the route's middleware nor its handler runs. On aRouterroute.try_constrain(param, ParamConstraint)returns the error a constraint on a parameter the route does not have gives;.constrainand thewhere_*spellings stop the boot on it. A pattern has to match the whole value, and\dmatches the digits of every script, so write[0-9]for ASCII digits. A WebSocket route takes optional parameters as well. A pattern with an optional parameter and an empty segment, and a second route for one form of an optional route, are refused when they are registered. - Console commands can be tested for what they print and ask:
console::test.dispatch_argvreturns aResultand nothing else, so a test could tell that a command ran and not what it said, and a command that asks a question waited on the standard input of the test runner.console::test(["users:purge", "--days", "30"]).expects_question("Delete 12 users?", "yes").run().awaitruns the command through the dispatcher the console binary uses and returns aConsoleRunwithoutput(),errors(),exit_code(),error()andunasked_questions(), and withassert_successful,assert_failed,assert_output_contains,assert_errors_containandassert_every_question_was_asked. Help, the version, parse errors and the error of a failed command are collected as well. A command prints withconsole::lineandconsole::error_lineand asks withconsole::askandconsole::confirm; what it prints withprintln!a test cannot see. Questions have to come in the order the test gave them, and a question with no prepared answer fails the command. The framework's own commands,db:seedandmodel:pruneamong them, print through the console now, andmake:commandgenerates a command that does. Schedule::command("emails:send --force")puts a console command on the schedule. The schedule took aTaskor a closure, so a command of the application, or a builtin such asmodel:prune, could only be scheduled by wrapping it by hand.commandtakes the line the way it is typed behind the name of the console binary, splits it into words the way a shell does, and returns theTaskBuilderevery other task uses, sodaily(),without_overlapping()andon_one_server()apply. The command runs in the scheduler's process. The line is checked when the schedule is built: a name no command has, arguments the command does not take, and a quote that is not closed stop the boot, andtry_commandreturns the error. The task is named by its command line and described by the command's about text.suprnova db:seedandsuprnova model:prune. The console binary has had both commands, and the manual shows them through the CLI, but the CLI forwardedmigrateand its siblings and not these two, so the step aftersuprnova migratewascargo run --bin console -- db:seed.suprnova db:seedruns every seeder, andsuprnova db:seed UserSeederor--class=UserSeederruns one.suprnova model:prunetakes--model=<Name>and--pretend. Both run the project's console binary, which checks the names.QdrantVectorDriver::from_env()andMariaDbVectorDriver::from_env(). Only the Pinecone driver read its configuration from the environment, so choosing the vector store by environment needed hand-writtenstd::env::varcode for the other two. The Qdrant driver readsQDRANT_URLand, when it is set,QDRANT_API_KEY. The MariaDB driver readsMARIADB_URL, andDATABASE_URLwhen that is not set and names a MariaDB or a MySQL database, which is the setup with one engine for rows and vectors. ADATABASE_URLof another engine is not taken. Amysql://URL is taken as well, because a MariaDB is written that way too. The Qdrant client is built without its version check, which connects and blocks while the application boots. A variable that is missing is named in the error at boot, and the error never shows a URL.- Storage configures an S3 disk from the environment. Mail, the queue and
the rate limiter read their configuration from
.envwhen the server boots; storage read no variable, so an S3 or S3-compatible disk (MinIO, RustFS, R2, B2) existed only when the application built anS3Configby hand, and the.envthe Docker guide shows configured nothing. WhenS3_BUCKETis set, the server now registers an S3 disk nameds3fromS3_BUCKET,S3_REGION,S3_ENDPOINT,S3_ACCESS_KEY,S3_SECRET_KEYandS3_ROOT. With no keys set the driver uses the default credential chain of AWS, andAWS_REGIONis read whenS3_REGIONis not set. What to check when you upgrade: an application that already setsS3_BUCKETfor a disk of its own gets thes3disk as well, and the server does not boot when the variables describe no usable disk: no region, or one key without the other. A disk the application registered under the names3is left as it is, and the variables are not read then.S3Config::from_env()returns the same configuration for a disk with a name of your own, andfilesystem::bootstrap_from_env()is the function the server calls; the console binary boots no driver of the environment, so an application whose commands use the disk calls it in its own bootstrap. There is still no default disk, andFILESYSTEM_DISKis not read. Storage::url(disk, path)returns the public URL of a file. Storage had presigned links that expire,temporary_urlandtemporary_upload_url, and nothing for a file that is meant to be public, so applications built those URLs by hand and repeated the base URL of the disk wherever they did. A disk gets its public base URL withStorage::set_public_url("public", "https://cdn.example.com/files"), or a path of the application's own host,/storage.Storage::url("public", "avatars/7.png")joins the two and writes every character of the path that a URL gives a meaning to as%XX, soc++ notes.pdfisc%2B%2B%20notes.pdf. A disk with no public base URL returns an error, so a private disk hands out no link that can be guessed, and a path with a.or..segment is refused. A base URL is refused when it has a user or a password, a query or a fragment, a backslash, a.or..segment, or another scheme thanhttpandhttps, and the error does not repeat the URL.S3_PUBLIC_URLgives the disk of the environment its base. The function takes the name of the disk, becauseStorage::diskreturns theopendaloperator itself, which carries no name.DB::monitor(max)and thedb:monitorcommand dispatchDatabaseBusy. The event was public, exported from the crate root and listed with the database events the framework fires, and no code dispatched it: an application that listened for it to alert on a database that runs out of connections waited for an event that never came.DB::monitor(max)asks the server of each connection, the default one and every named one, how many connections it has from every client, and dispatchesDatabaseBusyfor a server withmaxor more. PostgreSQL countspg_stat_activity, and MySQL and MariaDB givethreads_connected, the way Laravel'sdb:monitorasks. SQLite has no server and is never busy. The server does the counting, so the answer is the same from every process, and the check can run on the schedule:schedule.command("db:monitor --max 80").every_minute(). Nothing runs it by itself.DB::connection_counts()returns the numbers andDbConnection::server_connections()the number of one connection.DbConnection::connections_in_use()is the other number, the connections of this process's own pool that are out of it now.suprnova::fakeis thefakecrate, for factories written by hand. The crate root hadDummy,FakeandFaker, and everything else a factory uses, the fakers offake::fakerandrand::Rngforfake_with_rng, was reachable through the hiddensuprnova::__fakealone, which the factories chapter showed as the supported path. An application that addedfaketo its own dependencies had to keep its version the one of the framework, or the traits did not line up.use suprnova::fake::faker::internet::en::SafeEmailanduse suprnova::fake::rand::Rngnow work.__fakestays for the code#[derive(Factory)]generates.#[derive(Dummy)]generates code that names the crate::fake, so in an application withoutfakeamong its dependencies the struct says where the crate is:#[dummy(crate_name = "suprnova::fake")].WorkflowWorker::try_with_config(config)andworkflow::assert_no_duplicates().WorkflowWorker::new()refuses to start when two#[workflow]functions have one name.with_configskipped that check and told the caller to runregistry::assert_no_duplicates, a function of a module that is hidden from the documentation and was exported nowhere, so a worker with a config of the application's own lost the check without a word.try_with_configchecks the config and the registry and returns the error wherenew()panics, andassert_no_duplicatesis exported fromsuprnova::workflow.with_configstays the constructor with no check, and says so.new()makes its checks throughtry_with_config, so the two cannot come apart.Crypt::decrypt_string_with_originand its siblings return where a value came from.DecryptOrigin,KeyOriginandAadVersionwere public, and every function that returned one was hidden, so the two questions of a key rotation, does this value still need a previous key and does it still use the legacy label, were answered in log warnings alone.Crypt::decrypt_string_with_origin,Crypt::decrypt_string_for_with_originandCrypt::decrypt_with_originreturn the value and itsDecryptOrigin, andDecryptOrigin::needs_reencryption()says whether the value is to be written again. With them the job that ends a rotation can be written: read every encrypted value, write again what needs it, and remove the previous key when nothing does. For tests,crypto::testing::encrypt_string_underandencrypt_string_for_underwrite a value under a key and a label of the test's choice; they are compiled with thetestingfeature and replace the hidden_test_encrypt_withnames the manual pointed at. The three types are exported from the crate root. An error for a decrypted value that does not decode as JSON no longer quotes the value: it says which kind of mistake it was and at which line and column. That is the error ofCrypt::decrypt, of a pagination cursor, and of the castsAsEncryptedArray,AsEncryptedObjectandAsEncryptedCollection, whose error is a validation error and was shown to the client with the decrypted value in it.- Metric attributes have types.
inc_with,record_withandset_withtook&[(&'static str, &str)]and sent every value as a text, so a status404matched no filter on a number and no range, and the attributes the semantic conventions type as a number or as yes and no arrived as the wrong type. A value is now anything that becomes anAttrValue: a text, a whole number, a number with a fraction, or abool.counter.inc_with(&[("http.response.status_code", 404)])sends a number. Values of one type are written as they are, and values of several types are each made anAttrValue:("route", AttrValue::from("/posts")), ("error", AttrValue::from(true)). Every call that passes texts compiles as before. Au64orusizethat noi64holds is sent as the largesti64. A text is also a reference to what holds one,&String,&&str,&Box<str>,&Arc<str>,&Rc<str>and&Cow<str>, as it was when the values were&str. Two calls have to be written another way: an empty list,inc_with(&[]), isinc(), and a value that is.as_ref()names its type,.as_str().AttrValueis#[non_exhaustive]. - A WebSocket handler sends from another task:
WsSocket::sender()andWsSocket::split(). Every method ofWsSockettakes&mut self, so while a handler waited inrecvnothing could send on the connection, and a broadcast, a timer or a finished job had to go through aselect!loop and a channel of the handler's own.sender()returns aWsSender: it clones, itssend_text,send_binaryandclosetake&self, and every clone sends on the same connection.split()takes the socket apart into aWsSenderand aWsReceiver, and theWsReceiveris also aStreamof the messages. The connection does not wait for its senders: when the handler returns the connection closes, every later send returns an error,is_closed()returnstrueandclosed()completes, so a task that keeps a sender learns when to stop. The receiving half has to be read, because the answer to the heartbeat's ping arrives there. - An upload policy says which rule it breaks:
UploadPolicy::validate()andUploadPolicyError. A Live upload field whose policy the engine refused failed the registration of its component with one closed error,invalid_component_upload_metadata, whichever of the rules was broken: a limit that was not set or was zero, a media type or an extension that was not in canonical form, a media type declared twice, a dimension of zero, a finalize action that was missing or was no name.UploadPolicy::validate()returns the rule as anUploadPolicyError, and the registration logs it as an error before it fails. The error of the registration is what it was, so nothing of a component reaches a browser through it. - A Live operation that fails inside the engine says why. The engine
answered every failure of one of its own parts with one reason for the
browser,
ExecutionFailedorLedgerUnavailable, and threw the error away, so a panic of a component, a clock that gave no time and a ledger that was full read the same in every log. The browser still gets that reason and nothing more.RefreshRequiredExecution::cause()returns anExecutionFailure, a closed value that names the part that failed and the kind of its error: the action, the lifecycle, the ledger, the clock, the snapshot, the view, the composition, a port of the host. It isNonefor a refresh that is no failure, such as a stale revision. The framework writes one warning for each operation that ends with a cause, with the component, the reason and the cause.MountError::cause()returns aMountFailurein the same way for a mount, private or public, andMountError::ledger_kind()is the kind of the ledger when the ledger refused. Neither value holds a text, an identifier of an instance or anything of a request. loadandload_missingon one model. Both were methods of a collection only, so code with onePostin hand wrapped it in a collection of one to load its comments, or ran the query of the relation by hand and lost the cache of the model.post.load(["comments"]).await?andpost.load_missing(["comments.user"]).await?load into the model itself, through the loader of the collections: nested names, the one query for each relation and the transaction of the caller are the same.load_missingruns no query for a relation that the model has.PaddleProvider::archive_customerarchives a Paddle customer. Paddle has no endpoint that deletes a customer, sodelete_customerof the Paddle adapter returnsPaymentError::NotSupported, and its message named a way that did nothing: an update withmetadata: {"status": "archived"}writes a key namedstatusinto the custom data of the customer, and the customer stays active.archive_customer(provider_customer_id)sets the status of the customer toarchivedat Paddle. A customer that Paddle does not know isPaymentError::NotFound. The message ofdelete_customernamesPaddleProvider::archive_customer. What you have to change: code that archived a customer throughmetadatacallsarchive_customer, and removes thestatuskey from the metadata if it does not want it there.- A supported way to test a cached route:
render_cache::testing::RenderCacheProbe,RenderCacheConfig::with_clockanddatabase::testing::StatementCounter. A test that has to prove that the render cache served a response had the hidden hooks of the framework's own tests and nothing else:key_for_route_for_test,inspect_route_for_test,inspect_l1_for_test,clear_l0_for_test,with_clock_for_test,observe_statements_for_test.RenderCacheProbe::route(pattern), with.params(..)and.at_epoch(..), gives the key the route derives (key()), the entry of each tier for that key (l0(),l1()), andRenderCacheProbe::clear_l0()empties the first tier and leaves the second as it is. The probe derives the key with the function the middleware uses, so you tell it each dimension the policy of the route varies on:.login(id)forPrincipal,.tenant(id)forTenant,.locale(tag)forLocale(the current locale of the process when you leave it out) and.host(host)forHost; a route that varies onHostand a probe with no host is an error that names the dimension.l0()reads throughMemoryRenderStore::peek, which does not count as a use, so a probe between two requests does not change what the first tier evicts next;RenderCache::inspectcounts as a use.RenderCacheConfig::with_clockinstalls the clock the runtime reads, so a test moves an entry through its freshness bands without a sleep.StatementCounter::install(&mut connection)counts the prepared statements run through a connection, so a test shows that a request the cache served ran none; unprepared SQL and transaction control are not counted. All of it is compiled with thetestingfeature, and no function of it panics: an error names the route and never a login, a parameter or a key. What you have to change: a test that calledRenderCacheConfig::with_clock_for_testcallswith_clock. The other hooks stay for the framework's own tests, and are compiled with thetestingfeature only. - A binding that lives for one request:
App::scoped. The container had bindings for the process and overrides for a test, and nothing between them, so a service that belongs to one request, such as the database handle of the tenant or an API client bound to the request, was global and leaked between requests, or was built by hand in every handler.App::scoped::<T>(factory)andApp::bind_scopedregister a binding whose factory runs at most once in a scope, at the firstApp::get, and whose value is dropped when the scope ends. The framework opens a scope for each request, each WebSocket session, each attempt of a queued job, each attempt of a queued listener, each run of a scheduled task, a workflow or a supervisor, and each console command. An after-commit callback, a hook that runs after the response and the body of a streamed response share the scope of the request that registered them.App::run_scoped(future)opens a scope of your own,App::in_current_scope(future)carries the scope of the caller into a future that you spawn, andApp::spawn_scopeddoes both steps. Outside a scope,App::resolvereturns an error that names the type, andApp::getlogs a warning and returnsNone: a scoped binding never builds a value that lives for the process. A test override wins over a scoped binding. A factory is synchronous and runs once: a second task of the scope that asks for the value while it is built waits for it on its thread, and a cycle of scoped factories, in one task or across tasks, is an error. - The permissions of a user answer the gate:
rbac::register_gate_bridge. The roles and permissions of RBAC and the gate did not know each other, soGate::allows_async("edit posts", ..)did not see a permission that the user holds, and an application had two systems of authorization side by side.suprnova::rbac::register_gate_bridge::<User>(), called once in the bootstrap, makes every permission that a user holds, directly or through a role, an ability of the gate. An ability that is no permission of the user goes on to the gate definitions and the policies, so the bridge allows and never denies. It reads the permissions of a user once for a request, throughGateBridgeMiddleware, which the call installs as the first global middleware. A grant or a revocation made before the first check of a request is seen by that check; after it, from the next request on. A check insideDB::transactionreads for itself and keeps nothing, so a grant that is rolled back does not answer after the rollback. A unit of work that runs inside a request in a scope of its own, such as a job that the sync queue driver runs inline, reads for itself too. A read that fails is logged and allows nothing. The permissions answer the async forms of the gate,allows_async,authorize_asyncandinspect_async. The forms withoutasynccannot wait for a database and skip them.Gate::before_asyncis the hook the bridge is built on, and an application can register hooks of its own with it. ASome(false)from an async hook denies on the async forms only: a hook that must deny on every form belongs inGate::before. Without the call nothing changes. - An application registers guards of its own:
Auth::extendandAuth::via_request.Guardwas a public trait, but the manager built guards from two drivers, session and token, so a guard for an API key, a client certificate or a single sign-on could be written and not registered, andAuth::guard("api_key")and the middleware that takes a guard name could not use it.Auth::extend(driver, factory)registers the factory of a driver, andGuardConfig::custom(driver, provider)declares a guard of it. The factory gets the name of the guard and its provider.Auth::via_request(name, resolver)is the short form for a guard that reads the request: the resolver gets the request and answers with the user, and the guard is declared withGuardConfig::custom(AuthManager::via_request_driver(name), provider). The middleware for the guard runs the resolver once for a request. Outside that middleware the guard reports no user, as the token guard does. An error of a factory or of a resolver fails the request with 500 and is never a guest. A guard of the application is read-only through the manager:Auth::stateful_guardreturns an error for it, and so doAuth::logout,Auth::login_idandAuth::login_rememberwhen such a guard is the default guard, before they change anything. A guard of the application has no:in its name: resolving such a guard, or registering a resolver for it withvia_request, is an error. A logout forgets the users that the guards of the application resolved in the request, so the request does not sign itself back in. Declared as the default guard, a guard of the application answersAuth::userand the unnamedAuthMiddleware::new(). The principal that the middleware attests for Live is<guard>:<id>for a guard of the application, so the same id under two guards is two principals; a session user attests its bare id. What you have to change:AuthManager::via_requestreturns aResult.GuardDriverhas the variantCustom(String)and is no longerCopy, so code that copies a driver borrows it or clones it, and amatchthat names every variant has one more to name. suprnova::eloquent::prevent_lazy_loading(true)refuses a relation read that runs one query for each row of a list. A template that readspost.author()for each of 50 posts runs 51 queries, and nothing said so until the load of production. With the switch on, a relation read on a model that came out of a query that returned more than one row, when the relation was not loaded withwith(..),load(..)orload_missing(..), runs no query and returns an error that names the model and the relation. A model fromfind,first, agetthat returned one row, orcreatereads its relations as before, as in Laravel.count()of a relation is not refused.handle_lazy_loading_violation(handler)registers one handler for the process, which gets aLazyLoadingViolationwith the names of the model and the relation; with a handler the read goes on, so a staging system can log the reads and keep serving.clear_lazy_loading_violation_handler()removes it, andpreventing_lazy_loading()reads the switch. The switch is off by default, and with it off every read behaves as before. Turn it on in the bootstrap of the application outside production.- A test moves the clock the framework reads:
suprnova::clock::now()andsuprnova::testing::TestClock. The framework read the wall clock withchrono::Utc::now()in about 170 places, andtokio::time::pausemoves the timers of Tokio and not those reads, so a test of a signed URL that expires, a session that idles out, a scheduled task that is due, a window of a rate limit or a model that becomes prunable had to sleep. Every such read goes throughsuprnova::clock::now(), and so do the timestamps the#[model]macro writes, the due check of a scheduled task without a time zone and its one-run-a-minute gate, and the touched-at stamp of the session. Without thetestingfeaturenow()isUtc::now()and nothing else. With it,TestClock::freeze()andTestClock::travel_to(at)stop the clock of the current thread at a time you move withadvanceandset, until the guard is dropped, andTestClock::scope(at, |clock| future)holds a time across.awaitand on a multi-thread runtime;clock.run(future)carries it into a task you spawn. A clock of one test never reaches another test that runs beside it. Three reads keep the wall clock, because each is compared with a clock a test cannot move: the health endpoint, the retry time of a workflow run (compared withNOW()of the database), and the window of theRateLimiterfacade (its cache key expires in real time). The in-memory driver ofRateLimitMiddlewaremeasures withtokio::time::Instant, whichtokio::time::pausemoves, and the Redis driver reads the clock. What you have to change: code of your own that reads the time for a decision readssuprnova::clock::now()when its tests should be able to move it. suprnova::schema::Schemawrites a migration without an identifier enum orColumnDefchains. A migration can build its tables withSchema::create(manager, "posts", |t| { t.id(); t.string("title"); t.timestamps(); })andSchema::table,Schema::drop,Schema::drop_if_exists,Schema::rename,Schema::has_tableandSchema::has_column. The layer builds SeaORM'sTable::create(),Table::alter(),IndexandForeignKeystatements and runs them on theSchemaManagerthe migration is given, so every statement runs on the migration's own connection and transaction, and a SeaORM migration and aSchemamigration can sit in oneMigrator.Blueprinthasid()(aBIGINTauto-increment primary key),foreign_id(name).constrained(table)withon_deleteandon_update, eighteen column types, the modifiersnullable,default,uniqueandlength,indexanduniqueover several columns, and inSchema::tablealsorename_column,drop_column,drop_indexanddrop_foreign. A column isNOT NULLunless it isnullable().timestamps()andsoft_deletes()create thecreated_at,updated_atanddeleted_atcolumns asVARCHAR(255), because#[suprnova::model]stores aDateTime<Utc>field as RFC 3339 text unless the field declares a cast;timestamp_tzwith a native cast gives a native column. On SQLite, adding or dropping a foreign key on an existing table is an error that is returned before any statement of the call runs, and every other alteration runs as its own statement. The layer is not re-exported at the crate root, wheresuprnova::Schemais SeaORM'sSchema.make:migrationgenerates SeaORM migrations as before.
Changed
- Magnetar's
CeremonyStoretakes a named request for its atomic transition.transition_and_consumeandtransition_and_consume_exacttook six and seven positional strings, so a transposed selector or state compiled and acted on the wrong ceremony. Both take aTransitionAndConsume { transition, expected, next, consume }whose two ceremonies areCeremonyRef { selector, kind }, and the exact form takes the consume id as its second argument. A store that overrides either method changes its signature to match. delete_allon a soft-delete model soft-deletes. It issuedDELETEon every model, soPost::query().filter(...).delete_all()permanently removed rows that a row-leveldelete()would have trashed. On a model declared withsoft_deletesit now writes the tombstone, andupdated_atwhen the model manages timestamps, and the rows stay readable throughwith_trashed().force_delete_all()is the explicit hard delete.Builder::without_global_scope::<S>()andBuilder::without_global_scopes()are supported chain methods.#[scopes]refuses a scope written in the wrong form. A method in a#[scopes]block that took&mut Builder<User>, named the model instead ofSelf, or returned nothing was left an ordinary method, and no scope reached the builder. It is now a compile error on the signature that names the accepted shape,fn name(query: Builder<Self>, ...) -> Builder<Self>. A method that handles no builder still passes through unchanged, and#[not_scope]marks a helper that does handle one.suprnova serveruns the pending migrations once, when it starts, and no longer on every save. The backend runs under a file watcher, and an application started with no subcommand migrates before it serves, so every save of a source file ran every pending migration against the developer's database, the draft of a migration saved a moment ago included. A migration that has run is not run again when its file changes, so the database kept the schema of the first draft.servenow runsmigrateonce before the backend starts and starts the watched backend withserve --no-migrate. The frontend and the processes ofSuprnova.tomlstart first and do not wait for it. When a file undersrc/migrationschanges after that,servesays that it was not run and thatsuprnova migrateruns it; with--jsonthat is the new event{"type":"migrations_changed","ts":...}, and the run at the start shows as a process namedmigrate.--migrate alwaysrestores the old behaviour, and--migrate neveror--no-migrateruns no migration at all. When the run at the start fails, the backend is left to migrate by itself for that session, as before: it does not serve until the migrations pass. A project with nosrc/migrationsdirectory is left to migrate by itself as well.seed::clear()is a supported function of thetestingfeature. It was hidden from the documentation as an internal helper, and it is the only way for the tests of an application to reset the registry of the seeders, which is one for the process and which the guard of the test container does not reset. The manual told readers to call it and said in the same breath that it was hidden. It is documented now and compiled with thetestingfeature alone, which is a default feature, so a test suite needs no change. A build withdefault-features = falseand withouttestingno longer has the function.- The paginators serialise to Laravel's JSON shape.
LengthAwarePaginatorhaddata, the counters andpath, and no URL of a page and nolinks; the simple paginator hadhas_more, and the cursor paginator had the cursors and no URL. A front end that was written for Laravel's paginator JSON, the pagination components of the Inertia starter kits among them, could not read them. The three now have the fields of Laravel'stoArray():first_page_url,last_page_url,next_page_url,prev_page_urlandlinkson the paginator with a total,current_page_url,first_page_url,next_page_url,prev_page_url,fromandtoon the simple one, andnext_page_urlandprev_page_urlon the cursor paginator.linkshas the window of pages and the labels of Laravel. A URL is thepathand the page parameter, and apathwith a query string keeps it. Every field that was there is still there, andpathis still left out when it is not set.LengthAwarePaginator::links(),next_page_url()andprevious_page_url()return the same values in Rust, and the other two paginators have their own. A page parameter that thepathhas already is replaced, so the URL of the current request can be given as thepath, and a fragment of thepathstays at the end of the URL. - A web push subscription that cannot be used is
WebPushError::InvalidSubscription. An endpoint that is no URL, that is nothttps, that names an address in place of a host, or that names a host that is no push service wasWebPushError::Internal, with the textinternal:in front. A key that is not what RFC 8291 asks for wasWebPushError::Encryption: ap256dhor anauththat is no base64url or has the wrong length, ap256dhthat is not in uncompressed form or is no point of the P-256 curve. Bad stored data read as a fault of the crate, and no caller could tell the two apart. The new variant says which rule refused the subscription and is not retryable.WebPushChannelhandles it as it handles a subscription that is gone: it logs a warning and the dispatch succeeds, so a queue does not send the job again, with every channel that delivered before this one. A stored route that is no subscription at all is handled the same way. It was an internal error. No warning of the channel has the endpoint, because the path of an endpoint is the token that reaches the browser: a warning has the host andendpoint_sha256, the first 16 hexadecimal digits of the SHA-256 of the stored endpoint, which finds the row. The warning for a subscription that is gone had the whole endpoint. The errors of the crate's own headers stayInternal, and a payload that is too large and a failure of the encryption stayEncryption. AmatchonWebPushErrorthat names every variant has one more to name. - A database error on the payment webhook path keeps its type:
PaymentError::Database. The webhook route made a text of every database error,PaymentError::Internal(format!("{e}")), in twenty-two places, so the code that decides what to do with a failed webhook could not ask whether the failure was a lost connection, which the next attempt cures, or a violated constraint, which none does. The new variant has thesea_orm::DbErras its source, reachable witherror.source()anddowncast_ref, andFrom<sea_orm::DbErr>makes a statement end in?. The text of the error is what it was, and the route answers 503 for every database error as it did: the variant is what a later decision can be made on, and none is made yet.Debugprints the variant with the text of the database error and not with itsDebug, which for a violated constraint names the values of the key. AmatchonPaymentErrorthat names every variant has one more to name. suprnova::paymentsnames the types it exports. The module hadpub use dto::*;, the only glob export of the framework. It exported the modules ofdtoas well as the types, so every type had two public paths,payments::StartSessionRequestandpayments::session::StartSessionRequest, and a type that was added todtowas public inpaymentswithout anybody deciding so. The twenty-five types are named now. The paths through the modules,payments::session::and its seven siblings, are gone: the modules are reached aspayments::dto::session.Http::senddecides once whether an attempt is retried. The loop had the decision twice, for a response with a status of the server and for an attempt that got no response: the same check of the policy, of the method and of theretry_whenpredicate, in two blocks that a change had to keep alike by hand. It is one function now, and the two outcomes are retried by one rule. What is retried and how long the request waits is what it was.- The parser of
#[model]has no#[allow(dead_code)]left. Sixteen suppressions onModelInputandRelationDeclsaid that a later task would read the field. The tasks are done and the fields are read, so the suppressions hid nothing and would have hidden a field that a later change leaves unread. They are removed with the comments that named the tasks. - The dogfood application's
bootstrap.rsimports what it uses. Its import of the framework had a blanket#[allow(unused_imports)], which hid thatsingletonwas imported and never used, and would have hidden every later one. The suppression and the import are removed. - The
Dataderive has no module-wide#![allow(clippy::collapsible_if)]. The attribute turned the lint off for the whole file with no reason given. It is removed, and the nested conditions it hid are written as one. mail::mailable_registry::render_outgoingtakes its values as a struct. The function had fourteen arguments in a row, four of themVec<Address>one after the other: the recipients, the copies, the blind copies and the reply addresses. Two of them in the wrong order compile, and the mail goes to the wrong list. It takesany,mailable_nameand aRenderOutgoingParamsnow, whose fields are named.RenderOutgoingParamsimplementsDefault, so a caller names the fields it has. A caller ofrender_outgoinghas to build the struct. The framework has one, the job that sends a queued mail.OutputFormat::WebPis lossy and honoursquality, andOutputFormat::WebPLosslessis new. WebP was always written lossless, so.quality(80).format(OutputFormat::WebP)gave the same file for every quality, and for a photo a larger file than the JPEG it replaced.WebPis lossy now, at the quality of the pipeline, which is 70 when none is set. The built-in driver writes it lossless in two cases, because the lossy form of WebP cannot hold the image: when a pixel is not fully opaque, and when a side is longer than 16383 px.WebPLosslessis always lossless and ignores the quality. Both have the content typeimage/webpand the extensionwebp. The ImageMagick driver writesWebPlossy with its alpha channel, and passes-define webp:lossless=trueforWebPLossless. What you have to change: amatchonOutputFormatthat names every variant, as a driver of your own has, needs an arm forWebPLossless. Code that needs the pixels of a WebP to be exact asks forWebPLossless. A WebP source that is resized and not converted is written asWebP, so an opaque one is written lossy.Subscription::updatechanges the prices of a subscription on Stripe and on Paddle, and the Paddle adapter cancels at once when it is asked to.updatewithnew_price_refsreturnedPaymentError::NotSupportedon both adapters, so a change of plan was a cancellation and a new subscription. The list is the set of prices the subscription has after the call: an item whose price is in the list keeps its id and its quantity, an item whose price is not in the list is removed, and a price that is new is added with the quantity 1, except in a swap: when the change removes exactly one item and adds exactly one price, the new price takes the quantity of the item it replaces, so ten seats of one plan become ten seats of the other. The adapter computes the change from a read of the subscription, and the change is not atomic: a change made at the provider between the read and the write can be undone (Paddle takes the whole list) or left in place (Stripe changes items one by one), and the returned subscription shows the result. An empty list, and a list that names a price twice, isPaymentError::Validation, on both adapters and on the mock. The new fieldUpdateSubscriptionRequest::prorationtakes asuprnova::payments::Proration:ProrateNowbills the difference at once,ProrateAtRenewalputs it on the next invoice, andDoNotProratecharges nothing for the change.NoneisProrateAtRenewal. On Paddle, a change of prices in the same call ascancel_at_period_endor with anidempotency_keyisNotSupported.cancel(id, false)of the Paddle adapter cancels the subscription at once, andcancel(id, true)cancels it at the end of the billing period; it cancelled at the end of the period for both. Every call of the Stripe and the Paddle adapter has a deadline of 30 seconds. A read that gets no answer in that time is aPaymentError::Providerwhose text ends in "timed out". A call that changes something is aPaymentError::Providerwhose text says that the outcome is unknown: read the state at the provider before you send the call again. The text of an error that the Stripe or the Paddle adapter builds from an error of its SDK holds the operation and the kind and code of the provider's error, and never the provider's message, an id or a URL: a Stripe API error gives its type, its code and the HTTP status, a Paddle API error its type and code, and a transport error comes without the URL of the request. Stripevoidof a payment that is already captured is aValidationerror whose text does not name the payment. TheNotFounderrors ofMockPaymentProvidercarry no id. What you have to change: every struct literal ofUpdateSubscriptionRequestnames the new field,proration: Noneto keep the default. Code that calledcancel(id, false)on Paddle and counted on a cancellation at the end of the period passestrue. A test that read an id out of aNotFounderror of the mock reads it from its own request.- A polymorphic relation takes a target with any key, loads nested
relations, and can be touched. Three limits of
MorphToare gone. The id of a morph relation was ani64, so a model with aString, UUID or ULID key could not be the target: the id is the value of the key of the target, and the<name>_idcolumn of the child has the type of that key. All targets of one relation have keys of one type, and a relation that mixes them does not compile, nor does a child whose<name>_idfield has another type. A parent'sMorphManyorMorphOneis not checked against the child's<name>_id, so keep that field at the key type of every parent that owns it. The lazy read of aMorphTofinds the target by its key and applies no global scope of the target; the eager load runs the query of the target and applies its global scopes. A nested eager load throughMorphTo,with(["commentable.user"]), returned an error: the loader groups the targets by their type and loads the rest of the path once for each type, and a target type that does not have the relation is an error that names the type and the relation, whether or not a row of that type was loaded.#[model(touches = [...])]tookBelongsTorelations only: it takes the name of aMorphTorelation, and a save or a delete of the child writes theupdated_atof its owner, inside the transaction of the write when there is one. An owner without timestamps is skipped, a soft-deleted owner is not touched, and a null<name>_idtouches nothing. A<name>_typethat names none of the targets is an error of the write:create,save,update,deleteandforce_delete(and their_with_txforms) resolve everyMorphToowner oftouchesafter theCreating,Saving,UpdatingandDeletinglisteners have run and before the statement, from the values the statement writes, so a listener that rewrites<name>_typeor<name>_iddecides the owner, and an owner that cannot be resolved returnsErrwith no row written, no later event dispatched and no owner touched. An empty collection checks a dotted path ofCollection::loadandload_missingtoo. What you have to change:MorphTo::morph_idand the id in theUnknownvariant of the generated enum are aserde_json::Value, so code that reads the id as an integer callsas_i64().<relation>_loaded()of aMorphToreturns the generated enum.
Fixed
- Magnetar logs a lockout status failure before the sign-in fails closed.
The password plugin answered
503when the lockout store could not report an identity's status and logged nothing, while the failed-attempt path beside it logged its error. The status path now logslockout status unavailable; failing closedwith the store's error; the response is unchanged. - Magnetar logs a failure to record a rejected two-factor attempt. Re-enrollment, confirmation and recovery-code rotation discarded the error from the lockout store when they recorded a failed attempt, so a store fault during an attack left no trace. Each now logs a warning with the error; the rejection itself is unchanged.
- Magnetar's Redis abuse limiter says why Redis failed. Every client error
became
shared abuse-limiter backend failed, so a refused connection, a timeout and a script error read the same in the log of a limiter that fails sign-in closed. The message now ends with the Redis client's own description of the fault. - A stored session payload that fails to parse is logged. The database session driver read a damaged payload as an empty session, which signs the visitor out, and logged nothing. It now logs a warning with the parse error and without the session id. A failed delete of an expired session row is logged as well.
- A Live request that cannot be prepared says why in the log. When the
Live runtime could not be bound or a request could not be prepared, the
server answered
500 Live request preparation failedand logged nothing. It now logs the error with the route pattern and the stage, on the HTTP path and on the WebSocket upgrade path; the response is unchanged. - The NOWPayments adapter's HTTP failures name their cause. A failed
request, an unreadable response body and a body that is not JSON each became
a fixed
PaymentError::Providermessage. Each now ends with the underlying error, down to the refused connection or elapsed deadline for a transport failure, and never includes the request URL, which carries the payment id. - A failed Live upload cleanup run is logged. The background loop that retires expired uploads discarded the result of every run, so a store that kept failing left the uploads in place with nothing in the log. A failed run now logs a warning, and the loop retries on its next interval as before.
- A model's cast storage aliases stay out of its rustdoc.
#[model]emits apub type __Suprnova_Cast_Storage_<field>for each cast field, and each one appeared in the documentation of the application's own models. They are hidden now. - A factory insert fires the model's lifecycle events.
Factory::createandcreate_manyinserted through SeaORM directly, socreating,saving,createdandsavednever fired and no observer saw a factory's rows. They now take the same insertModel::createtakes: acreatingobserver can change the attributes or cancel the insert, andcreatedruns for every row.create_quietly()andcreate_many_quietly()insert with the events muted. A model whose key is not auto-increment keeps the key its factory set. DATABASE_URL=mariadb://...connects. Onlymysql://was recognised, so the scheme a MariaDB operator naturally writes failed at connect with no supporting driver.mariadb://is accepted for the primary connection, named connections and read replicas, the migrator, andMariaDbVectorDriver::from_url, andDB::driver_title()answersMariaDBfor it. The vector driver's pool error no longer quotes the connection URL, which carries the password.QUEUE_DRIVER=syncandQUEUE_DRIVER=nullselect their drivers. Both drivers existed, but the environment bootstrap knew onlymemory,redisanddatabase, sosyncbecame an in-memory queue with a warning. AQUEUE_DRIVERthat names no driver is now a boot error in production, where an in-memory queue taken by mistake loses every job at the next restart; elsewhere it still falls back to memory, and the warning lists the accepted names.- A chained job's
Job::delay()applies. A chain built each link's envelope withavailable_atset to now, so a job that declares a delay ran at once when it was a link of a chain, head or not.ChainLinknow records the delay at build time, as it records the queue, and the link becomes available that long after it is reified: at dispatch for the head, and when the link before it completes for every other link.ChainLinkgains the public fielddelay_secs, so code that builds one with a struct literal has to name it. Chain payloads written before the field existed decode as links with no delay. - Batches, chains and failed-job retries go through the queue fake. Only
the
Queue::pushfamily checkedQueue::fake().Queue::batch().dispatch()andQueue::chain().dispatch()went to the driver, so a faked test failed with "queue driver not initialized" when no driver was installed and pushed real jobs when one was.Queue::retry_failedandQueue::retry_all_faileddid the same. All four record in the fake now and write to no driver. A batch is still stored in the batch repository, so the id the caller receives names a batch.queue::testinggainsbatched(),assert_batched,assert_batch_count,assert_nothing_batched,chained(),assert_chainedandassert_nothing_chained, with the recordsFakedBatchandFakedChain. The jobs of a batch and the head of a chain are recorded as pushes too, soassert_pushedsees them. - The queue worker honors a retry hint. A job that failed with
FrameworkError::RateLimitedcarrying aretry_afterwas retried on its own backoff, so a queued web push that a push service refused with429andRetry-Afterwent back to the service early, or waited far longer than it was asked to. The worker now releases such a job for the hinted time, capped at 24 hours (queue::retry::RETRY_HINT_CEILING). Every other failure keeps the job's backoff.queue::retry::delay_after_failureis the function the worker calls. - The middleware priority list orders the chain.
append_middleware_priorityandprepend_middleware_priorityrecorded a list that nothing read, so middleware ran in the order it was registered whatever the list said, and an application that relied on the documented order could run authentication before the session was loaded. A chain is now put in the order of the list when it runs, for a matched route, the fallback, an unrouted request and a WebSocket upgrade alike. A middleware the list names moves in front of any middleware the list places after it. Every other middleware keeps its place, so one registered afterAuthMiddlewarestill runs after it. The list orders global, group and route middleware together. It sees the middleware registered by type; a middleware boxed by hand withinto_boxedand added with.middleware_boxed(...)keeps its place. An empty list costs one read per request. #[derive(Command)]without adescriptionkeeps clap's own about text. The derive called.about("")when#[console(description = "...")]was left out, which replaced the about text clap had taken from the struct's doc comment or from#[command(about = "...")]. A command described the way clap users describe one showed an empty line in the console's list of commands. The derive now sets the about text only when adescriptionis given, and adescriptionstill overrides the doc comment.CommandEntry::about()returns the text the help shows, whichever of the three it came from;CommandEntry::descriptionstays the attribute's text and is empty when the attribute has none.suprnova schedule:list --timezone=<zone>is accepted. The application's ownschedule:listhas taken--timezonesince the flag shipped, and the manual shows it through the CLI, but the CLI's subcommand took no arguments and ended withunexpected argument '--timezone'and exit code 2. The CLI now takes the flag and hands it to the application, which checks the zone name.- The scaffolded
src/tasks/mod.rsshows a task that compiles. Its example implemented aScheduledTasktrait withnameandschedulemethods. The trait isTask, its only method ishandle, and the name and the times a task runs at are set where it is registered. Every new project received the wrong example, and copying it gave an unresolved import. The comment now shows whatmake:taskgenerates, with the registration insrc/schedule.rs. - A render cache policy that varies on
FeatureVersion,ConfigVersionorApplication(name)is refused when it is registered. Nothing gives these three dimensions a value, so a route that declared one could not build its key and every request for it went past the cache, while the route looked cached in the code.try_render_cacheandtry_render_cache_groupnow return an error that names the route or the group and the dimension, for a full policy and for a patch that brings the dimension in, so the application stops at boot. The other six dimensions register as before. This refuses one arrangement that cached before: a group whose policy declared one of the three, with a patch on every route that replaced the dimensions. The group is refused now, and the dimension is to be taken out of its policy. - Telemetry is exported, each signal to its own path, and a signal can have
an endpoint of its own. With the
otelfeature the OTLP exporters had no HTTP client: each one failed to build withno http client specified, no trace, metric or log left the process, and the error was logged before a log subscriber existed, so nothing showed it. The exporters have the blockingreqwestclient now, and an exporter that cannot be built is reported after the subscriber is installed.init_telemetryalso gave the baseOTEL_EXPORTER_OTLP_ENDPOINTto the exporter of each signal, and the exporter uses an endpoint it is given in code as it is written, so the URL of every signal was the root of the collector, where a collector has nothing, andOTEL_EXPORTER_OTLP_TRACES_ENDPOINT,OTEL_EXPORTER_OTLP_METRICS_ENDPOINTandOTEL_EXPORTER_OTLP_LOGS_ENDPOINThad no effect. Each signal is now sent to its own path under the base,/v1/traces,/v1/metricsand/v1/logs, and a signal with a variable of its own is sent to that URL as it is written, as the OTLP specification says. Traces can go to one collector and metrics to another. The base endpoint is still what turns telemetry on.OtelConfighas the three endpoints as fields,traces_endpoint,metrics_endpointandlogs_endpoint, whichfrom_envreads, so code that builds anOtelConfigwith every field named has three more to name. A signal whose endpoint is no URL is left out and reported, and the other signals are exported; the report never has the endpoint in it, which can carry a password or a token. A base endpoint that was given a path of a signal to make up for the missing one, such ashttp://collector:4318/v1/traces, is to be the base again: the path is added to it. An endpoint is a URL with the schemehttporhttpsand a host: a blank base endpoint does not turn telemetry on, and a signal whose endpoint is a path alone is left out and reported, where it was built and sent nothing.OTEL_EXPORTER_OTLP_COMPRESSION=gzipworks;zstdis not compiled in and leaves the signals out, with the reason in the log. What the exporters log about their own requests is printed and not exported, so a process at debug level does not send lines about its own sending without end. - The session middleware does not panic on a poisoned lock. The session,
the cookies that wait for the response, the remember tokens that wait to be
revoked and the list of the fresh Magnetar sessions were locked with
.lock().unwrap()in thirty places, which panics when an earlier panic left the lock poisoned. The list of the fresh sessions is shared with the clean-up task that runs after the request, so a panic in one request could end the clean-up of it. The locks are taken with a function that goes on with the value of a poisoned lock. The three lists are changed by code of the framework alone, which cannot panic between two writes, so they are whole after any panic. The session is changed by closures of the application: when a closure ofsession_mutpanics and a Live action or a listener catches the panic, the request goes on and can read the session, but the middleware does not store it. It retires a Magnetar session that the request issued, takes back a remember cookie that the promotion of a second factor issued, answers 500, and the stored session stays as it was, which is what such a request did before. The policy of the framework for locks is that a poisoned lock is an error or is recovered, and never a panic. generate-routesfinds a form request by every name it is declared with. The command read the source for#[derive(FormRequest)]and for the helper attribute#[form_request(..)]. An application writes neither: the crate root exports the derive asFormRequestDerive, becauseFormRequestis the trait there, and the short form is the attribute#[request]. A struct with one of those was left out of the generated routes, so its request type was missing in the TypeScript, and no message said so. The command reads#[request],#[derive(FormRequestDerive)]and#[derive(FormRequest)], each bare or behindsuprnova::, and the helper attribute.generate-typesreadInertiaPropsandDatain both forms already, and the three detectors ask one function.chunk_by_idandlazy_by_idwalk a table whose key is noi64. The cursor of the walk was ani64, so a model with aStringkey, or withunique_id = "uuid","uuid_v4"or"ulid", got the first batch and then an error. The closure had run on that batch by then, and a table that fits in one batch never gave the error. The cursor is the value of the key as the model has it, so an integer key and a string key both walk, in the order of the key. For a key with no order in time, a UUID v4, a row that is inserted during the walk with a key below the cursor is not seen by that walk. A key that cannot be a cursor is refused before the first query and before the closure sees a row: a composite key, and a key column that is no integer and no text, such as a nativeuuid::Uuid, a timestamp or a decimal.lazy()andcursor()walk throughlazy_by_id, so both hold for them. What you have to change: a walk over a model with such a key returnedOkwhen the table fit in one batch, and returns the error now. Usechunk()for it.
Security
- Global scopes can no longer be bypassed by a trashed view, a chained
opt-out, or an
or_where. Scopes were applied whenModel::query()built the builder, which left three holes.with_trashed()andonly_trashed()started from a bare builder and ran with no global scope, so on a model with a tenant scope they returned every tenant's rows.query().or_where(...)folded into the scope's own term and read(tenant_id = ? OR ...), and on a soft-delete model(deleted_at IS NULL OR ...). Andquery().without_global_scope::<S>()compiled and did nothing. The soft-delete filter and the registered scopes are now folded in when the query runs: the statement is<scopes> AND <your terms>with anORgroup as one atom, the trashed views lift only the soft-delete filter, and an opt-out lands wherever it is chained.update_all,delete_allandincrement_eachresolve the same way, so a mass write reaches only the rows a read would return. A scope that reads per-request state reads it when the query runs. - Behind a proxy,
Request::ip()is the address the proxy saw, and no longer one the client wrote. A proxy adds the address it saw to the right end ofX-Forwarded-Forand leaves what was there, andip()returned the left end. Behind nginx, Traefik, HAProxy or a cloud load balancer, a client that sent the header itself chose the address the application saw: a new rate-limit bucket with every request, and the address of a payment provider for a webhook that checksremote_addr.ip()now reads the header from the right and returns the first address that is no trusted proxy. It reads every line of the header as one list, reads an entry with a port (203.0.113.5:54321,[2001:db8::5]:443) as its address, and ends at an entry it cannot read, where the answer is the proxy that wrote that entry.X-Real-IPis read only when the request has noX-Forwarded-Forat all. What to check when you upgrade: every proxy between the client and the application has to be inAPP_TRUSTED_PROXIES, not the last one alone. A proxy that is not listed is taken for the client, and all of its clients share one address; that includes the address a load balancer adds behind the client's, as the external Application Load Balancer of Google Cloud does.APP_TRUSTED_PROXIEStakes ranges in CIDR form for that,10.0.0.5,173.245.48.0/20,2400:cb00::/32, which is how the edge of a content delivery network is listed; in code it isTrustedProxiesConfig::and_networkswithProxyNetwork. A range must hold proxies and nothing else, because a client that connects from a trusted address is believed like a proxy, and the range of every address (0.0.0.0/0) is refused. A proxy that writesX-Real-IPalone has to remove theX-Forwarded-Forof the client. An IPv4 address that is written as an IPv6 one (::ffff:10.0.0.5) is the IPv4 address, in the headers and for the peer.Request::ips()still returns the whole chain and is a record, nothing to decide by. - A cap on the WebSocket connections one client address holds open:
RateLimitMiddleware::connections_per_ip(n). The only limit on open connections was the server-wideSERVER_MAX_CONNECTIONS, one number for every client together, so a single address that opened WebSockets and kept them could use all of it and lock every other client out of HTTP and WebSocket alike. The broadcasting and WebSocket chapters showedconnections_per_ipon thews!route; it did not exist. The middleware answers429 Too Many Requestswhen the address already holdsnsockets. A socket is counted until its session ends, close frame or none, and an upgrade that a later middleware refuses gives its place back at once. The address is the oneRequest::ip()resolves through the trusted proxies; an IPv6 address is counted with its /64 network, because one client holds a whole /64. The counts are kept per process; a clone shares them, so one cap can guard several routes, andopen_for(address)reads a count. On a route that is no WebSocket route the cap counts the requests being handled at one time and does not cover a streamed response.Request::hold_for_connection(guard)is the part other middleware can use: it keeps a guard alive until the socket of an upgrade ends, where a guard the middleware holds itself is dropped at the handshake. - Magnetar does not quote decrypted state in an error. Four places decrypt the state of a ceremony or of a device session and decode it, and the error for state of another shape was the message of the JSON decoder, which quotes the value it could not read. That state holds challenges, session grants and tokens, and two of the errors are shown to the client. The error has the kind of the mistake and its position now, and nothing of the content. It can happen where a deployment changes the shape of the state while a ceremony is under way.
- An encrypted cookie opens under its own name and in no other way.
Release 1.3.0 bound the name of a cookie into its encryption and kept a
fallback that still opened a value written without the name, to be removed
in 1.4.0, which was never released. While the fallback was there, such a
value opened in every cookie, so the binding protected nothing against it.
The fallback is removed for cookies. It stays for the other purposes, where
it opens stored values that do not expire as a cookie does: read those with
decrypt_string_for_with_originand write them again. What you have to change:Cookie::read_encrypted(wire)is removed, useCookie::read_encrypted_for(name, wire).Crypt::encrypt_stringandCrypt::encryptwithCryptPurpose::Cookiereturn an error, useCookie::encrypted(name, value)orCrypt::encrypt_string_for.Crypt::decrypt_string,decrypt_string_with_origin,decryptanddecrypt_with_originwithCryptPurpose::Cookiereturn an error, useCookie::read_encrypted_fororCrypt::decrypt_string_for. A cookie that was written before 1.3.0, or withencrypt_string, does not open any more. For the session cookie and the remember cookie the user signs in again, and for the maintenance bypass the operator visits the secret URL again. No request fails for it.
2.1.0 - 2026-09-18
Added
- Live ships the foundations of its component library. A token stylesheet
with a base layer arrives as the
ui-stylesruntime artifact when a document opts in withwith_suprnova_ui(); every rule sits in thesuprnova-uicascade layer and every visual value is a--sn-token with light and dark values, so the skin is removable with nothing breaking.live:addinstalls a component as one directory undertemplates/suprnova-ui/from its manifest, keeps files you edited, and accepts a third-party manifest under its own root; the framework serves the vendored stylesheet and script at/suprnova-ui/<component>/<file>. The form family ships as Askama macros the checker now expands, so a library view passeslive:checklike any other. Thesuprnova.namespace is reserved to the library and the registry refuses it from any other crate. - The Live component library gains its overlay family. Tooltip, collapsible
and accordion, popover, a single-level dropdown menu, dialog, sheet, and
drawer install with
live:addbeside the form family. Each owns its open state through the native primitive (details, thepopoverattribute,dialog) before any script, makes no Live request to open or close, returns focus to its trigger on close, and keeps its open state across a morph under a stable key withlive:preserve.self. - The Live component library gains its feedback and navigation families.
Alert, skeleton, spinner, progress, empty state, toast region and flash
region; header bar, footer, sidebar, breadcrumbs, tabs, pagination and load
more install with
live:addbeside the form and overlay families. Feedback presents state the server or runtime holds: an alert's role follows its variant with a non-color cue, loading presentation is bound throughlive:loadingand shows on the runtime's own timing, progress is the native element with a label and readout, the empty state's reason is server state, and a toast announces once without taking focus while a critical error also renders as an alert. Navigation keeps route semantics: anchors with real URLs,aria-currentfrom the server, an explicit local or route mode for tabs and pagination, Live pagination reflected withhistory.replaceStateand no history entry, and load more as a keyed append from a button. Thelive_keyview filter lands with them: alive:keyinside a{% for %}loop passes through it, and it enforces at render time the key rule the checker enforces on literal keys. - The Live component library gains its data display family, and with it
the built-in set is complete. Separator, scroll area, aspect image, card,
badge, avatar and avatar group, list group, description list and stat card
install with
live:addbeside the earlier families; every one keeps document order and native semantics, and every status carries text. The chart renders on the server throughcharts-rs:render_chartinsuprnova::live::chartsdraws bar or line marks from bounded typed series as trusted SVG, and the macro places a summary and a data table beside it, so no charting script reaches the browser. The datatable is a native table with one island per table whose sort, filter and page are#[url]fields reflected into a shareable URL after every action. - The Live component library gains its live-native family, the last one.
The upload widget renders the shipped upload protocol's states from the
runtime's progress root and claims nothing durable before the finalizing
action; the live feed and notification bell carry the runtime's stream
status announcements, so a degraded, reconnecting or closed stream says
so; the account menu is a details disclosure with a CSRF-protected
sign-out form and a documented stitch slot under RenderCache. The
custom-element tier, input OTP, date picker and combobox, enhances native
controls it never replaces: each
sn-element is a light-DOMHTMLElementdefined by its own vendored file and holds no form value, so the form submits the same value with the script blocked. The combobox refuses a listbox rendered for an older query. - Session blocking serializes the requests that carry one session.
SESSION_BLOCK=true, orSessionConfig::block(SessionBlock::default()), makes the session middleware hold a cache lock for the session from load to write, andblock_sessionon a route or group enables it for those routes alone. Both bounds are yours, the hold and the wait, and a request that waits past the bound answers503withRetry-After. Without it, two concurrent requests on one session wrote back last-writer-wins, so a flash set by a redirect could be lost to a request that started earlier.
Changed
- Live's supported browser baseline is Chrome and Edge 114, Firefox 128, and
Safari 17. The floor rises from Chrome and Edge 111 and Safari 16.4 to the
first releases that ship the native
popoverattribute the component library's overlays own their open state with. The compatibility matrix's minimum slots move with it; Firefox stays at 128.
Fixed
- A template's
live:keyreaches the Live runtime. The checker validatedlive:keyand the manual named it, but the browser runtime's morph identity, morph controls and preservation scopes read only the engine'sdata-suprnova-live-key, so a keyed control written as the checker requires had no effect and every library component wrote the key twice. The runtime now readslive:key, keeps the engine spelling for the roots it renders, refuses an element carrying both with different values, and the components writelive:keyalone. The form gallery's save form also gained the.preventmodifier it lacked, so a Live submit no longer reloads the page from the form's own query. - A Live form holding an empty number input or an unselected select submits. The runtime read such a control's null value as a mismatch with itself and refused the whole submit, so the action never ran and the browser submitted the form natively. The search input's model binding also used a debounce the runtime does not accept; it now uses 250 ms.
live:checkchecks every element a view renders. A view that called a macro splicingcaller()with an empty call block, as the validation summary is called, rendered no content after that call to the checker, so the component proved clean while the rest of the view went unchecked. The empty call is now empty content, and a view that renders nothing fails the check. Fixing it exposed errors the dogfood form gallery had hidden.- A declared model debounce is 100, 250, or 500 milliseconds.
#[model(debounce = N)]accepted 1 to 60000 ms, but the directive grammar the checker and the browser runtime share lists three durations, so any other value could never be bound by a template; it now fails to compile.live:erroralso accepts an action as its target, as a validation summary names one, matching what the runtime resolves. - A Live form of more than seven model fields submits. The browser runtime
refused any request carrying more than eight operations or model proposals,
and any response with more than sixteen validation entries or eight events,
though the framework's server accepts 128 of each; the refused submit never
left the browser and was reported as a network failure. The browser now
admits the server's counts,
live:checkrefuses alive:submitform of more than 127 model fields, and a request refused for a limit is reported as a resource limit that shows the action's error feedback. - The combobox stays responsive and shows what the server answered. Text
that no option matched froze the page, because the element's observer
watched attributes its own render rewrote even when nothing changed. The
element also filtered the server's options by substring, hiding results a
server search matched another way, such as an accent-insensitive or code
match. It now writes only what changed, shows every option while the
listbox answers the input's current text, keeps an answer to older text
hidden, and filters by the typed text only for a fixed list, which
remote=falseselects. - A library custom element binds once however a morph moves it. The combobox, input OTP, date picker, and password input bound their listeners on every connection, and the dialog, sheet, and drawer guarded on an attribute a morph removes, so a moved element answered one click twice and the password reveal toggled back at once. Every element now binds per connection, releases its listeners and observers when it leaves the document, and keeps them across an atomic move.
- A toast holds while the pointer is anywhere on it or focus is inside it. The region resumed its timers when the pointer left any child element, so moving from a toast's text to its padding let it time out under the pointer, and a toast could hide while its dismiss button had focus.
- Nested tabs act on their own tabs. A local tabs instance selected every tab below it and handled the events of a nested instance, so a click on an inner tab hid the outer panel.
- The tooltip bubble stays open while the pointer moves onto it. The bubble ignored the pointer, so it hid as the pointer left the trigger and its text could not be read or selected.
- The select's dropdown indicator follows the text color. It was a
data-URI SVG, whose
currentColordoes not inherit the document's color, so it drew black on the dark scheme's surface. - The form controls show the island's values. No form macro took a value,
so a number input mounted at 1 rendered empty and a submit that changed
nothing proposed an empty value. Each value control now takes
value=,checked=, orselected=, radio and checkbox group inputs are keyed by value so a choice the user has not sent survives a re-render, andauthority=marks the render that must replace what the user typed. - A checkbox group proposes the list of checked values. The runtime read every checkbox as a boolean, so a group whose boxes disagreed could not be submitted. A checkbox group of any size, and any field that more than one checkbox binds, now proposes the checked values in document order; a single checkbox stays a boolean.
- A model proposal its field cannot decode is a validation error on that
field. A proposal such as null for a
u64field or a boolean for a list field was dropped silently: the action ran and the response carried no validation. The field now reports the error throughlive:errorand keeps its value, and the action does not run. - The checker, the
live_keyfilter, and the runtime accept one key alphabet. The checker and the filter accepted a key beginning with_,-,., or:, which the runtime refuses, so the island's first morph failed. A key now begins with an ASCII letter or digit everywhere, andlive:checkholds the element ids inside an island to the rule the runtime checks, refusing an invalid id (invalid_element_id) and a repeated one (duplicate_element_id), a literal id inside a loop included. live_key_digestkeys any value.live_keyfails the island's render for a value outside the key alphabet, so a row keyed by an email address failed the island for every viewer. The new filter turns any value into a stable key, one value always yielding the same key.live:checkchecks a loop or match binding as that binding. Inside a macro body, a name that afor, amatcharm, or anif letbound was checked as the macro parameter of the same name, so a literal argument proved a directive that the loop's own values render.render_chartreturns an error for a value beyond 1e9. The renderer's axis arithmetic overflowed and panicked from about 1e12; a value whose magnitude exceeds 1e9 is now an input error.- An application that cannot read its vendored components refuses to
start.
try_live_ui_assets()readstemplates/suprnova-ui/under the application base path on each request, so an application started elsewhere, such as from a container image that holds only the binary, answered 404 for every component stylesheet and script and started cleanly. Installing the route now fails and names the directory. live:addreplaces a file you never edited. It compared bytes only, so after a library update it kept every installed file and reported it edited locally. It now records each file's digest beside the component and replaces a file whose bytes still match the record; a file you edited, or one no record vouches for, is kept and reported.live:add --manifestrefuses a file that is a symbolic link. Each third-party file was read through links, so a component could install the bytes of any readable file as a template. A named file must be a regular file inside the manifest's directory.- A model edit that a render replaced is sent when it is typed again. The browser compared each edit with the value it last proposed, so after a refused value and a render that replaced it, such as a reset, typing the same value again sent nothing: the control showed it with no error while the island held another value. The render an island applies is now the baseline the next edit is compared with, and a field's dirty state compares with the value that render gave its control.
- A tooltip can be dismissed where it is shown. A bubble that covers
content could be dismissed only by moving the pointer or focus away, which
WCAG 2.2 success criterion 1.4.13 does not accept. Escape now hides it with
neither moved, and the next hover or focus of that trigger shows it again.
The bubble still shows with no script in the page; the new
sn-tooltipelement carries the dismissal alone, andlive:add tooltipinstalls it.
2.0.2 - 2026-09-14
Changed
- The Live endpoints carry no version segment.
/__live/v1/action,/__live/v1/upload,/__live/v1/assets/*, and the/__live/v1/async/*family now live at the same paths without/v1:/__live/action,/__live/upload,/__live/assets/*,/__live/async/*. Suprnova's version is the git tag and the browser runtime ships in lockstep with the framework, so a second version inside the URL space promised an evolution path that would never be used. Applications are unaffected: the framework registers these routes and the runtime builds every URL, and hand-written references to/__live/paths were never supported.
Fixed
- Every issuance the Live per-scope limit admits answers with a subscription
that connects. Concurrent issuances of one scope in the same millisecond
mint identical descriptors, and the host's credential store kept only the
last secret minted for a descriptor, so the earlier requests answered 403
async_authority_invalidfrom the connect that issuance performs. About one issuance in five hundred also answered 503async_unavailable, because the claims it published while its envelope context was built shared one slot with every concurrent issuance. A descriptor now keeps every unconsumed secret until each is consumed or expires, and the claims under construction are keyed by subscription id.
Security
- The lockfile takes the rustls TLS 1.3 handshake fix.
rustls0.23.45 replaces 0.23.40, which accepted TLS 1.3 handshake messages across encryption level boundaries (RUSTSEC-2026-0285, published on the release day);aws-lc-rsandrustls-webpkimove with it. Every HTTPS client in the framework, from the HTTP facade to the Qdrant and payment adapters, resolves the fixed release. - A Live stream ends with the session that opened it. An asynchronous membership was re-authorized against its Gate before every delivery but never against its session: a browser that logged out, or whose session was revoked, kept receiving events until the stream itself closed. Destroying a session on a node now retires every membership it opened there at once, for a plain logout, session invalidation, id regeneration, and "log out everywhere" alike, and delivery re-checks each membership's session against the session store at most once per ten seconds, so a session destroyed on another node stops receiving events within that interval.
- A request's
Cache-Controldirectives are honored by RenderCache. A request carryingno-cachewas answered from storage withAge, and a cold request carryingno-storeseeded the cache for the next request.no-storenow bypasses lookup and publication alike, andno-cacheskips the lookup so the request is answered by a fresh render. Found by the 2026-09-13 adversarial audit (ASTRA-13). - A render without a snapshot is never published. When the snapshot
transaction could not open, RenderCache rendered without a read view and
still published if the generation reread agreed, so a render that
interleaved with a concurrent multi-row write could store a mix of two
database states. Such a render is now served but not stored (decline reason
snapshot_unavailable), and its rebuild lease is released. Found by the 2026-09-13 adversarial audit (ASTRA-08). - A cached response replays its
Content-Encoding. A pre-compressed body was stored without its content coding, so a hit served gzip bytes as plain text. The coding is stored with the body and replayed on every hit. Found by the 2026-09-13 adversarial audit (ASTRA-04). - A HEAD request never seeds the GET representation. A cold HEAD on a
route that renders nothing for HEAD stored an empty body under the key every
GET shares, so later GETs answered zero bytes. A HEAD miss is now served as
rendered and not stored (decline reason
head_render). Found by the 2026-09-13 adversarial audit (ASTRA-03). - The Live per-scope subscription limit holds under concurrency. Issuance counted a scope's subscriptions, released the lock, awaited the authorizer, and inserted afterwards, so a burst of concurrent requests could all pass the count and all be admitted once authorization returned, well past the advertised limit of 512 per scope. The slot is now reserved under the same lock as the count, released on every error path, and handed to the record when it lands. Found by the 2026-09-13 adversarial audit (ASTRA-07).
- A Live subscription stops receiving events once its Gate denies. An existing asynchronous membership kept receiving newly published events after the stream's authorization Gate was redefined to deny the principal, because delivery compared the subscription's own retained authorization memo with itself. New subscriptions were correctly refused; the old stream was not. The runtime now records the principal a subscription was issued to, asks the Gate again before every delivery, and retires a membership the Gate no longer allows. Found by the 2026-09-13 adversarial audit (ASTRA-01).
- A Live action declaring
transaction = "required"is refused at registration. The host's transaction port is a documented no-op, so the policy promised atomicity it never provided: each write committed on its own and nothing rolled back when a later stage failed.LiveRegistrynow fails withRegistryErrorKind::RequiredTransactionUnsupportedfor such a component until the port installs a real ambient transaction; actions without the policy register as before. Found by the 2026-09-13 adversarial audit (ASTRA-05). - A cached route's named-connection reads stay on their connection. A
RenderCache miss renders inside a snapshot transaction on the primary
database, and query routing preferred that transaction over a query's own
on("name")or a model's declared connection, so opting a route into the cache changed which database its code read from. A tenant or auxiliary database read could return the primary's row, fail on a table the primary lacks, or publish the wrong content under a valid key. Reads bound for another connection now run there even inside an ambient transaction, and a render that read outside its snapshot is served but not stored (decline reasonforeign_connection_read). Found by the 2026-09-13 adversarial audit (ASTRA-06). - A data write and its RenderCache invalidation commit together. On the autocommit path, a model save, a query-builder write, or a raw statement landed its row first and advanced the dependency generations in a second transaction afterwards. When that second transaction failed, the row was durable, the API returned an error, and every cached page that depended on the row kept passing its coherence check and serving the pre-write content: a visibility, entitlement, or deletion change could stay invisible until the next successful invalidation. Every write terminal now runs the row write and its advancement inside one transaction opened for the purpose, so both commit or neither does. A ledger table that vanishes after RenderCache decided it was present now fails the write instead of being skipped with a warning. A write bound for a named connection, whose ledger lives on the primary, keeps its separate advancement; if that advancement fails, the process stops serving stored entries until one succeeds. Found by the 2026-09-13 adversarial audit (ASTRA-10).
- A handler's
Varycontract is enforced before RenderCache stores. A handler that varied its body on a request header of its own and said so withVarywas stored under a key built from the route policy alone, so the first variant's body was served to every other variant, with theVaryheader missing from the hit. Wherever that header selected user, device, or experiment-specific content, one request's content reached another's. RenderCache now parses the response'sVarybefore publication and declines to store when it names*or a field the policy does not declare as a key dimension (decline reasonvary_undeclared). Found by the 2026-09-13 adversarial audit (ASTRA-09). - A handler's
Cache-Control: no-storeis honored by RenderCache. A route opted into the cache stored a response whose handler saidno-storeand replayed it under the policy's ownpublic, max-age=60, s-maxage=60, so a handler's "do not store" was ignored on the server and rewritten for every browser and proxy downstream. The eligibility check now reads the response'sCache-Controland declines storage on theno-storetoken (decline reasonno_store_directive), and the declined response goes out exactly as the handler built it. Found by the 2026-09-13 adversarial audit (ASTRA-02). - A per-response CSP nonce is never replayed from the cache. A public page
that minted a nonce on every render and named it in
Content-Security-Policywas stored as an ordinary complete entry, so every later hit carried the first render's nonce in both the header and the inline script. A nonce is the authorization token for inline script in one response; replaying it made that token readable to anyone who could fetch the page. RenderCache now declines to store such a response (decline reasonnonce_source_policy); a hash-based policy caches as before, and stitched Live documents keep issuing a fresh nonce per hit. Found by the 2026-09-13 adversarial audit (ASTRA-12). - A cached response keeps its isolation and execution headers. RenderCache
stored a response's
Content-Disposition,Cross-Origin-Opener-Policy,Cross-Origin-Embedder-Policy,Cross-Origin-Resource-Policy,Permissions-Policy, andX-Frame-Optionsnowhere, so a cache hit served the same bytes without them. An HTML export that downloaded as an attachment on the first request rendered inline under the application's origin on the second, where any markup it carried ran with same-origin authority. The six headers now replay byte for byte from the stored representation. Found by the 2026-09-13 adversarial audit (ASTRA-11). - The lockfile sheds one unsound and three yanked dependency releases.
event-listener5.4.2 replaces 5.4.1, whose stack-allocated listener was unconditionallySend/Syncand let a!Sendtag cross threads in safe code (RUSTSEC-2026-0221); Suprnova's dependencies only use untagged events, so the unsound path was never exercised here.spin0.9.9 and 0.10.1 andchacha200.10.2 replace releases their publishers had yanked, andconcurrent-queueleaves the tree entirely.
2.0.1 - 2026-09-12
Fixed
-
A
redis://URL with a database index selects that database everywhere. The queue driver and the fanout broadcast hub each carry a sea-streamer producer beside their direct redis connections, and sea-streamer does not read the logical database from the URL's path - so a queue pointed atredis://host:6379/3pushed jobs into database0while its consumer half waited on database3, and the fanout hub operated on0outright. Both now carry the index across explicitly, with the same parsing rule the redis client applies. A URL without a path keeps selecting database0, so nothing changes for the common form. -
suprnova generate-typesends its output with one newline. The blank line that separates one interface from the next was also written after the last one, so a project that enforcesgit diff --checkfailed withnew blank line at EOFon a file it could not correct by hand: the next regeneration wrote the blank line straight back. Only the end of the file changes; the blank lines between declarations stay. -
A scaffolded login or registration form shows its validation errors. The generated auth controller declared an
errorsprop onLoginPropsandRegisterPropsand sent it asNone. The framework seedserrorson every Inertia page from the session-flashed validation bag, and an explicit prop of the same name replaces that seed, so the page receivederrors: nulland invalid credentials returned to a form that displayed nothing. Both props are now empty, the Login and Register pages of all three frontends readuseForm().errors, and the scaffold'sinertia-props.tsis the byte-exact output ofsuprnova generate-typesfor the scaffold's controllers, so a project's first regeneration no longer rewrites a file nobody edited. -
A scaffolded application serves its built frontend. The generated
routes.rsregistered no static-file fallback, so once Vite's dev server was not running every/assets/*URL in the HTML shell answered404, including inside the production image the scaffold'sDockerfilebuilds.routes.rsnow ends withfallback!(StaticFiles::public().handler()): declared routes still win, dotfiles such aspublic/assets/.vite/manifest.jsonand path traversal are refused, and an unknown URL still renders the InertiaErrorpage. -
A scaffolded application verifies email addresses and resets passwords. Registration created and signed in the user without sending verification mail, and no route offered email verification or password recovery, although the generated
Useralready implementedMustVerifyEmailandCanResetPasswordand theauth_flow_tokensmigration already shipped. Registration now mails a verification link throughEmailVerification::send_linkand continues to/verify-email, which shows the notice, resends the link, and consumes it on/verify-email/verifyfor the signed-in owner only./forgot-passwordmails a reset link to a verified address (an unknown or unverified address gets the same answer and no mail) and/reset-passwordrotates the password throughPasswordReset::complete_with_outcome, refusing to finish while the account's other sessions or remember-me tokens could not be revoked. The Vue, React and Svelte starters ship theForgotPassword,ResetPasswordandVerifyEmailpages and a "Forgot your password?" link on the login page. Links are built withurl::to, soAPP_URLmust name the address users reach the application at, and registration needs a working mail transport: the.envthe scaffold writes pointsMAIL_DRIVER=smtpat a local catcher on port 1025 (the Mailpit thatsuprnova docker:compose --with-mailpitadds), or setMAIL_DRIVER=logto print each message, link included, to the server log. -
A fresh Svelte scaffold builds against
@inertiajs/svelte3.7. The generatedmain.tsdeclared anasync setup, and@inertiajs/svelte3.7 typessetupas returningSvelteRenderResult | void, so a project scaffolded today (the template asks for^3.6.1, which now resolves to 3.7.1) failedsvelte-checkinsidenpm run buildbefore a single page had been written.setupis synchronous now and chains the translation catalog load onto the mount, so the ordering the template describes is unchanged.
Documentation
- The six locale mirrors of the 2.0.0 chapters follow the manual's own conventions. The chapters translated since 1.3.7 wrapped Japanese and Simplified Chinese prose mid-sentence (1,653 line breaks that rendered as stray spaces), rendered 59 terms differently from the rest of their locale, translated 9 repeated headings a second way, and left 2 quotes unpaired. All of that is aligned with the older chapters, so a reader of any locale sees one vocabulary and unbroken sentences across the manual.
Upgrading
- These are scaffold fixes; an application generated with 2.0.0 keeps
its generated files. Upgrading the framework crate changes nothing in
src/orfrontend/. To pick the fixes up in an existing project, make the same edits by hand: drop theerrorsfield fromLoginPropsandRegisterPropsand readuseForm().errorsin the pages; addfallback!(StaticFiles::public().handler())as the last entry ofroutes!; and copy theemail_verificationandpassword_resetcontrollers, their routes, and the three auth pages from a project generated with 2.0.1. Thegenerate-typesoutput changes only at the end of the file.
2.0.0 - 2026-09-10
Security
-
A bearer token and a web session are now separate identities. The request-scoped user cache kept one current-user slot that everything wrote to and everything read from, so a browser session hydrated by
SessionMiddlewaresatisfied aTokenGuardon the same request, and a user resolved for the web guard was handed back to code that had asked for the API guard. Bearer credentials now carry their own provenance in that cache:BearerTokenMiddlewarerecords the identifier it validated in a bearer slot of its own,TokenGuardresolves and caches the full user there, and only something that arrived through a bearer credential can satisfy a token guard. Session guards are cached per guard name in the same place, soAuth::guard("admin").user()andAuth::guard("web").user()in one request no longer resolve to whichever of them ran first. The generic slots remain as a compatibility view for the staticAuthfacade, mirrored from the configured default guard alone, soAuth::id(),Auth::check()andAuthMiddlewarebehave exactly as they did for an application with one guard and for a token-only request that never installs a session. -
A named guard keeps its own principal, its own remember-me credential, and its own revocation. Logging in through
Auth::guard("admin")wrote the identifier into the same session key the default guard uses, so two guards in one application shared one principal and signing out of either signed out of both. In the persisted session each guard now owns its entry under the_auth_guardsmap, and the remember-me cookie carries a guard-tagged carrier (suprnova.remember.v1:followed by the guard name and the credential) so a cookie issued for one guard cannot re-authenticate another. A cookie without that prefix is read as the default guard's, which is exactly what a cookie issued by an earlier release is, so nobody is signed out by the upgrade; a carrier naming a version this build does not understand is refused rather than guessed at. Revocation follows the same boundary: signing out, and the middleware's own rotation path, retire the exact selector the owning guard issued rather than every credential the user holds. -
BasicAuthMiddlewareno longer accepts a stale session slot as proof. Its non-stateless form skipped theAuthorizationheader wheneverAuth::check()was true, andAuth::check()reads the request-scoped current-user slot, which anything earlier in the chain could have populated. It now asks for the persisted session principal of the guard it was configured with, and refuses outright when that guard is absent or is not a stateful guard, so a request is admitted without credentials only when a real session row says who it belongs to. The stateless form always re-read the header and is unchanged. -
Remember-me credentials rotate as one atomic replacement. Rotation used to remove the accepted credential and insert its successor as two writes: a failure between them consumed a valid credential and left the visitor with no way back in, and a crash left both rows live. The default schema now replaces one exact, still-valid row with its prepared successor in a single operation, and a store that cannot make the conditional removal and the replacement insert atomic fails closed rather than performing them separately. Selector matching is exact, so a credential is never retired by a prefix collision, and a synchronous identity transition inside a handler queues the exact credential it invalidated for revocation at the end of the request instead of leaving it live.
-
Two-factor admission is serialized, and a lockout write that fails takes the request down with it. Two workers proving the same code could each read the attempt counter before either wrote it, so a brute-force budget admitted more attempts than it allowed. Verification now reserves attempt capacity inside the same serialized store operation that admits the attempt, returning both the reservation and any finalized-failure state observed in that one decision; a ceremony that cannot commit cancels its prepared proof, and the cancel path's default fails closed so an existing verifier implementation cannot silently leak reserved capacity. A lockout counter write that errors is no longer swallowed: the attempt is refused. Promoting a session that is waiting on a second factor is one atomic migration, and the bearer credential is suppressed before the storage call is awaited, so a timeout or a backend failure can never leave a credential attached to a session the framework did not commit.
-
Session rotation fails closed. Rotating a session id destroys the old row and writes a new one. A destroy that errored was logged and stepped over, which left the previous authenticated row replayable by anyone holding the old cookie. The middleware now returns before writing the replacement and before issuing the new id, and expires the browser's old credential on the way out. Separately, the cookie that carries a fresh or rotated session is built before the row is committed: a cookie that cannot be constructed used to leave a session in the store that no browser could ever present, and now leaves nothing behind at all.
-
A session that outlives its user stops authorizing, and revoking a user's sessions reaches the named guards.
AuthMiddlewaretreated the presence of a persisted identifier as proof of an identity, so a deleted or soft-deleted user kept passing every guarded route until the session expired. It now resolves the user through the provider and clears the stale slot when the provider finds nothing; an application with no user provider bound at all keeps the identifier-only fast path, recognized by its own error rather than by matching message text, and every other provider failure is an error rather than a pass.destroy_all_for_usermatched only the indexeduser_idcolumn, which is null for a session authenticated through a named guard alone, so those sessions survived a "sign out everywhere". It now compares the guard identities inside each surviving payload as well. -
Device-authorization ceremonies transition atomically and are validated before consumption. Approving a device code read the ceremony, then consumed it, then wrote the grant, so a replacement issued under the same selector between the read and the consume could be consumed instead of the record that was actually approved. The store contract now binds the consuming transaction to the exact record a prior read observed, and transitions one ceremony while consuming another in a single atomic step. Both methods default to failing closed, so an external store implementation stays source-compatible without silently getting the weaker behaviour.
-
A provider-token refresh whose outcome is unknown is fenced, not retried. A linked-account refresh that started and then lost its answer left an ordinary claim that expired on schedule, so a second worker refreshed the same grant and one of the two results was discarded, taking a single-use refresh token with it. Starting an exchange now replaces the claim's owner with a reserved exchange owner while preserving the original deadline, so followers can tell a live exchange from an abandoned one, and a store must never reclaim a row whose owner is in that reserved namespace. Stores that do not implement the fence fail closed.
-
Web Push refuses to send through a transport that might follow a redirect.
EndpointPolicy::Strictvalidates the subscription endpoint URL, but validation only ever covered the initial URL: a client that follows redirects turns a validated endpoint into a3xxto anywhere, and reqwest follows redirects by default. A client this crate builds now has redirects forcibly disabled, and the newWebPushClient::with_client_builderapplies every option a caller wants (proxy, TLS pinning, timeouts) while overriding the redirect policy.WebPushClient::with_client, which takes an already-built client whose redirect policy cannot be inspected, now refuses to send underStrictwithWebPushError::UnconfinedRedirects, before encryption and before any request.WebPushClient::allow_unconfined_redirectsis the explicit opt-out for a caller who knows their client is safe. -
A signed URL is bound to the exact path it was signed for. Signing and verification both trimmed a trailing slash before hashing, which made
/orders/1and/orders/1/one signature, and made a proxy that appends a slash indistinguishable from a client that edits the path. The path is now hashed exactly as it appears, so a signature covers one path and one path only. -
A cache key can no longer address a lock or a tag index. Redis lock, tag, and key-tag records lived under a NUL sentinel after the configured prefix, and a caller-supplied key beginning with that sentinel landed in the same space, so a
Cache::forgetcould release a distributed lock somebody else was holding. Values and each internal record type now carry distinct namespace components ahead of the caller's key, so the two spaces cannot meet. An ordinary key is stored exactly where it was before, so nothing already cached is orphaned. The in-memory driver got the same separation. -
Payment webhooks reject what they cannot identify and classify duplicates by the database, not by message text. A provider event with a missing, non-string, or whitespace-only identifier used to enter the shared idempotency namespace under a blank key, where it collided with every other such event; it is now rejected before any state is written. A concurrent duplicate is recognized from SeaORM's structured unique-violation code rather than from human-readable error text an unrelated failure can also contain, and only a re-read of a committed
processed_atis acknowledged as one, so a mirror-write failure stays retryable. Stripe's signature timestamp is compared with an unsigned absolute difference, so an extremet=value returns a signature error instead of overflowing, and a negative configured tolerance accepts only an exact match. The webhook route preserves the typed status of a body it refused, so an over-cap body is still a413rather than a flattened400. -
A non-idempotent HTTP request is no longer replayed after a transport error. The retry policy already required the explicit
retry_non_idempotentopt-in before replaying aPOSTorPATCHthat answered5xx, but the transport-error branch beside it did not check, so a request whose connection dropped after the server had accepted it was sent again. Both branches now apply the same rule. -
Session lifetimes cannot overflow into mass expiry.
SESSION_LIFETIMEandSESSION_REMEMBER_LIFETIMEare minutes multiplied by sixty and then added to a stored timestamp in date arithmetic that panics on overflow, so an oversized value either aborted the process or wrapped into a deadline in the past that expired every session at once. Both are clamped toMAX_SESSION_LIFETIME_MINUTESbefore the multiplication, the database driver caps the same way for a configuration built in code, and a garbage collection cutoff that cannot be represented is skipped rather than sent to the database, which is the difference between collecting nothing and collecting everything. -
Machine-to-machine cache identities are unambiguous. The token broker's cache key concatenated the provider, the client, and the normalized scope set, so two different requests whose components happened to run together into the same string shared one cached token. The key is now a versioned domain with length-prefixed components, which no combination of inputs can make collide.
-
An idempotency lease is proven still held before its result is reported as fenced. The lease refreshed periodically while the body ran, and a transient refresh error was treated as loss, while a body that finished between two refreshes was reported as fenced without anyone asking whether the lock was still there. A transient refresh error is now retried and only gives up after several consecutive failures, and one final owner-scoped refresh must succeed after the body completes before the outcome is reported as fenced; an error in that last check answers
FreshUnfenced, because ownership is then unknown. -
The encryption key ring is validated and installed before application bootstrap.
Cryptwas initialized byServer::from_config, so anything that ran earlier - the bootstrap callback, a console command, a queue worker entry point that never builds a server - either found no key ring or built its own.#[suprnova::main]now loads the environment and then validates and installs the ring, in that order, before your bootstrap runs. Validation runs on every boot even after the ring is installed, so a production process with a missing or malformedAPP_KEYstill fails closed, while the process-wide key stays immutable. Laravel'sAPP_PREVIOUS_KEYSis accepted as an alias forAPP_KEY_PREVIOUS; when both are set and disagree, the Suprnova name wins and the duplicate is named in a warning. -
The archived
proc-macro-error2crate is replaced by its maintained successor. It was archived on 2026-06-07, is flagged unmaintained in RUSTSEC-2026-0173, and made every build warn that a future Rust release will reject it (E0365).validator_derive0.20.1 moves toproc-macro-error33.1.1 andsea-bae0.2.2 drops the dependency, so neither the advisory nor the warning appears any more. This landed on main after thev2.0.0tag; the taggedCargo.lockstill resolvesproc-macro-error2.
Added
-
Suprnova Live is part of the framework.
suprnova::liveis a server-driven interaction engine: a component is a Rust struct whose state lives on the server, whose view is a checked Askama template, and whose actions run over a signed protocol from a small browser runtime that morphs the re-rendered HTML in place. There is no client-side state model to keep in sync, no build tool to install to use the shipped runtime, and no inline JavaScript in your documents. The engine ships as an internal crate the framework depends on unconditionally, so nothing has to be enabled; the browser half is published as@suprnova/liveand its exact reviewed bytes are served by the framework itself.manual/live.mdis the application-facing chapter, and a project created bysuprnova newis Live ready out of the box: it writessrc/live/mod.rswith an empty registry and aroutes()function, binds the registry inbootstrap.rs, and installs the routes fromcmd/main.rs. -
Components are declared with
#[derive(LiveComponent)]and#[live]. The derive names the component and its view (#[live(name = "app.counter", view = "live/counter.html")]); the#[live]attribute on theimplblock marks the methods the browser may invoke. A#[public]field is rendered and carried in the signed snapshot, a#[model]field additionally accepts browser proposals throughlive:model, and an#[action]method is the only entry point a request can reach, receiving validated arguments and returning typed outcomes such as a redirect or a flash. Every field type must implementDefault; a fresh island starts from those defaults unless a mount hook says otherwise. Components are registered explicitly throughLiveRegistry::builder, and the registry is immutable once the runtime assembles - a duplicate name or view, or a component whose actions need validation with no validation port bound, fails registration with a typedRegistryError. -
suprnova::viewis a checked server-rendered view contract for ordinary routes as well as Live components.#[suprnova::view(path = "...")]declares a template,TrustedHtmlis the one audited type a template may emit unescaped, and thetrusted_htmlfilter is how it gets there;#[suprnova::view_filter]declares a checked custom filter. Askama is the substrate, but handlers depend on the framework's own contracts rather than on the template engine's modules, andTemplateFailureis a closed, redacted failure set (MissingData,InvalidData,Failed) rather than the engine's own error text. -
The
live:directive grammar is closed and proved against your components. A view binds behaviour withlive:click,live:submit,live:model,live:upload,live:key,live:loadingand the rest of the documented set - never an inline expression language, and never a server-returned script.suprnova live:checkbuilds your application and runs the integrated checker over every registered view: an unknown action, an unknown model field, a rawsafefilter, or an accessibility violation fails with the file, line, and column.--allow-unprovedaccepts the dynamic structures the checker deliberately makes no claim about. -
Router::try_live()installs the reserved Live namespace once. It registers/__live/v1/action,/__live/v1/upload, the/__live/v1/async/*control routes and WebSocket handshake, and the immutable/__live/v1/assets/*routes, and startup fails if an application route could claim/__live.Router::try_live_withtakes aLiveRouteGuardwhose middleware chain is applied to the action, upload, and asynchronous control routes and to the WebSocket upgrade, which is how an application attaches its own authentication, tenancy, and rate limiting; asset routes stay unguarded. Every reserved request carries a strict policy: session, origin, CSRF, principal, tenant, and rate-limit facts must all have been recorded by real middleware, and an asynchronous route that cannot see the complete set is refused rather than opening an anonymous transport. -
A Live request proves its own origin, and using Live relaxes nothing else. The shipped runtime sends the Live media type and the browser's own
Sec-Fetch-Siteheader and carries no session token, soCsrfMiddlewareverifies that proof for a Live operation on its own, whatever origin policy the application configured, and falls back to token validation for a cross-site or header-less request. Ordinary routes keep the configured policy, so an application no longer has to widenOriginPolicyfor the whole application to let Live work.AuthMiddleware::optional()is the new guard form this needs: it records a principal when one exists and lets an anonymous request continue, so anonymous visitors can act on a public seed while an identity-bound island still refuses a request without principal evidence. -
Documents place islands through
LiveDocument. A document route builds one from the request, mounts each island withLiveMount, and emits the bootstrap markup exactly once.LiveMount::public_seeddeclares an island any visitor may render, whose state is a reusable seed promoted to a real instance on the visitor's first action;LiveMount::identity_bounddeclares an island that belongs to the current session and principal, so its document route must authenticate.LiveDocument::bootstrapemits the inert configuration element and the ordered script tags with integrity attributes for the ESM or the classic strategy, adds the upload and asynchronous roles when a mounted component needs them and the Stimulus bridge on request, and rejects a second bootstrap or a mount after bootstrap.Router::try_live_mountregisters a mount, andRouter::try_live_documentdeclares a document route with no startup mounts. -
The framework serves the exact reviewed browser artifacts. The ten deterministic build outputs are embedded and validated against their manifest on first use, failing closed on any drift in digest, length, file name, role, capability, or version, and are served from
/__live/v1/assets/<identity>/<file>forGETandHEADwith immutable caching, strong digest validators, conditional requests,nosniff, and closed misses. Documents contain no inline executable code, so a strictscript-src 'self'policy holds.suprnova live:assets --out <dir>publishes the same bytes to a CDN or a static directory atomically, treats an identical publication as up to date, and refuses to replace a directory whose bytes differ unless you pass--replace. -
Live components accept file uploads under a declared, checked policy. An
#[upload(policy = ...)]attribute on a#[model]field declares maximum file count, declared and aggregate byte budgets, accepted media types, and replacement behaviour throughUploadPolicy::builder, and the view binds it with<input type="file" live:upload="avatar">. The runtime creates, transfers, and completes the upload through/__live/v1/upload; the bytes wait in quarantine until the declared finalize action runs, when the framework hands them to the application'sUploadFinalizer, alongside an optionalUploadScannerandUploadApplicationValidator. Every control is authorized through the gate aslive:<component>.upload.<field>.<Control>for each ofCreate,Reacquire,Status,Queue,BeginTransfer,PutChunk,Complete,Accept,BeginFinalize,CommitFinalize,Cancel,Reject,Expire, andFail. Every request revalidates the current mount, principal, session, tenant, component, field, and document scope, a per-handle lock serializes chunk, completion, cancellation, action, finalization, and cleanup races, and chunk bodies reserve the shared in-flight budget before buffering.Router::try_live_upload_reacquisitiondeclares an application-owned path outside the reserved namespace where a browser that lost its transfer grant can get a fresh one, answering only the session and principal that created the upload. -
Islands update asynchronously over SSE, WebSocket, or polling. A component declares the streams it listens to in the
#[live]attribute (streams(stream(name = "activity", topics("activity"), events(ActivityPosted)))), the framework signs a bounded subscription descriptor for the visitor, and the browser runtime opens a native transport and falls back to polling when it cannot. Subscribing is authorized through the gate abilitylive:<component>.stream.<name>; the application publishes throughsuprnova::live::LiveStreams, withrefreshtelling subscribed islands to fresh-render andevent::<T>delivering a typed payload to the island's registered handlers. Fanout, hop count, and per-document delivery are all bounded. Polling is an ordinary fresh render, so state catches up but event payloads published while a transport was unavailable are not replayed, which the runtime reports as a degraded stream rather than a current one. -
The browser runtime is a strict TypeScript package that ships in core and optional bundles.
@suprnova/livebootstraps once per document, discovers islands, parses the closed directive grammar, gives each island bounded work and truthful pending and failed state, applies a response only after a successful morph through a pinned private Idiomorph adapter, and preserves focus, form state, controllers, scroll, and history across morphs and native navigations. Optionaluploads,async, andstimulusbundles attach through a typed feature port, in ESM and classic forms; Stimulus is never bundled into core. There is noeval, nonew Function, no server-returned script, and no inline expression language anywhere in it. -
Four CLI commands cover the Live workflow.
suprnova live:make <name>scaffolds a component insrc/live/, its view intemplates/live/, and its registration in theregistry()builder, declares the module, validates every target and refuses traversal and symlinks before writing, writes atomically, never overwrites, rolls back every file a failed run had written, and can report a dry run.suprnova live:check,suprnova live:inspect, andsuprnova live:assetsare thin clients of a hidden framework console command and a bounded, versioned JSON-lines protocol, so the CLI keeps no framework or engine dependency and fails closed with no writes on anything unsupported, stale, truncated, oversized, or unexpected.live:inspectreports the bound registry, configuration limits, installed upload capabilities, assembled runtime services, and the asset identity as presence booleans and counts, never state or secrets. -
suprnova::live::testingprepares a router's runtime and mount catalog for in-process tests.prepare_live_router_for_testgives a test the same runtime the server assembles, so a test can decode an island's snapshot from itsdata-suprnova-live-snapshotattribute, post an action with a real session cookie andSec-Fetch-Site: same-origin, and assert on the accepted render through the application's real global middleware stack. -
RenderCache stores a proven-safe copy of a route's response and serves the next matching request without running the handler. It is opt-in per route and per group, it never changes what an application can do, and a route it declines still renders and serves correctly.
Router::try_render_cacheopts one already-registered route pattern in andRouter::try_render_cache_groupopts every route under a path prefix in;RenderCache::install(router, RenderCacheConfig::from_env())finishes the wiring after every middleware registration that establishes request-scoped locale, session, or identity.RENDER_CACHE_ENABLED=falseis a real off switch at install time: a disabled configuration returns the router untouched, probes nothing, registers nothing, and leaves the process gate shut. -
A cache policy states a representation class, a freshness policy, and how the response may be shared.
RenderCachePolicy::buildertakes aRepresentationClassrunning widest to narrowest -PublicShared,PublicShellStitched,PrivateCached,Uncacheable- andFreshnessPolicy::new(fresh_ms, stale_servable_ms, stale_on_error_ms)sets how long a representation is fresh and then how far past that edge a stored copy may be served while a background rebuild runs or after a foreground rebuild failed.SharedCachePolicycontrols what a shared cache in front of the application is told. A route inside a cached group can narrow its enclosing policy with aPolicyPatchinstead of restating it, and may only make it narrower; pulling one route out of a cached group is a patch that sets the class toUncacheable. -
Variance is declared, never guessed. A cached representation varies by route pattern, path parameters, and application build unless a policy says otherwise.
QueryPolicy::declared([...])names the query parameters that distinguish representations, and any other query parameter on a request bypasses the cache for that request rather than being silently ignored..vary(VarianceDimension::Locale | ::Host | ::Tenant | ::Principal)partitions by the negotiated locale, the request host, the current tenant, or the signed-in visitor, the last two as opaque key material; aPrivateCachedroute that declares neitherPrincipalnorTenantfails to build at all.MediaandEncodingare declared together with their own closed set through.vary_media(NegotiatedPolicy::declared([...], default)?)and.vary_encoding(...): the middleware negotiates the request'sAcceptorAccept-Encodingagainst that set per RFC 9110, with the highest quality winning, equal quality keeping the header's own left-to-right order, a wildcard compared as a literal token rather than expanded, and aq=0, out-of-range, or unparsable quality excluding a candidate rather than defaulting it. An absent, unmatched, or unparsable header resolves to the declared default and never panics. Both the render key and theVaryheader take their value from that one resolution, so they cannot disagree. -
A served hit is a real HTTP response with real validators. It carries
ETagas a strong validator a client can send back asIf-None-Matchfor a304, plusCache-Control,Vary, andAgein whole seconds since publication, which is the quickest local sign that a response came out of the store rather than out of a handler. A response served past its fresh interval additionally carriesWarning: 110 - "Response is Stale". Conditional requests andHEADare answered from the stored entry. -
Cached output is proved current against the database, not assumed. A request-scoped collector attributes every read a handler makes to the thing it read: a model, a table, a configuration value, a feature flag, an authorization decision, an identity axis. Every supported write path on the other side advances the generation of what it changed, in the caller's own transaction where there is one - the ORM's model and bulk writes, the query builder facade, raw table writes, the payments hydration path, feature flag writes, and the RBAC role and permission statements including the new revocations. A hit reproves the generations it depends on before serving, either by rereading the ledger under
CoherenceMode::Authorityor against a validation lease underCoherenceMode::Lease, so nothing a write has invalidated can be served as current.RenderCache::bump_permission_versionis the one invalidation an application calls by hand, from the code path that changes what a signed-in user may do; it advances a persisted generation every principal-keyed render observes, survives a restart, and joins the transaction the role change runs in. -
Authorization, feature flags, and global scopes participate honestly. A gate decision is judged by the identity axis its evaluation actually consulted, so a tenant-only consult needs only
Tenantdeclared while anything that resolved principal material, or resolved nothing nameable at all, needsPrincipal. An RBAC-gated route caches and a permission grant or revocation rebuilds it, because the five role and permission tables are observed rather than treated as an unknown. A feature flag read observes aFeaturegeneration whenever the snapshot holds that flag at any scope key,set_flagadvances it, and a flag reload advances it for every flag its own diff found changed. An EloquentGlobalScopedeclaresScopeDependency::Constantor keeps the conservativePerRequestdefault, and a per-request scope whose filter read nothing the collector can name is recorded as an undeclared read and narrows the render toUncacheablerather than silently caching a tenant filter away.suprnova::live::current_tenant()is the instrumented accessor a gate body or a scope reaches for. -
The write side is open in every process that writes through the ORM. A queue worker, a scheduled task, or a console command writes through the same ORM the server does and never calls
RenderCache::install, so its writes used to advance no generation and pages depending on them kept being served stale. The write side is now a process-wide tri-state probed at most once, never inside a caller's transaction, so every writing process advances the same generations the server does while an application with the cache disabled still issues no RenderCache SQL at all. -
Three deployment profiles decide where entries and rebuild leadership live.
RENDER_CACHE_PROFILEselectsembedded(a per-process file tier underRENDER_CACHE_L1_DIR, in-process leadership),database(entries insuprnova_render_entries, leases insuprnova_render_leases, Live instance records insuprnova_live_instancesandsuprnova_live_promotions), orredis(a Redis hash per key, plus a per-key publication token counter).RENDER_CACHE_L1andRENDER_CACHE_COORDINATORoverride either half independently, so a deployment that wants its entries in the database and its leases in process says exactly that. Generation truth does not move: the database-backed ledger is the authority at every profile, which is what lets Redis lose everything it holds without anything stale being proved current. The full table isRENDER_CACHE_ENABLED,RENDER_CACHE_PROFILE,RENDER_CACHE_L1,RENDER_CACHE_COORDINATOR,RENDER_CACHE_L0_ENTRIES,RENDER_CACHE_L0_BYTES,RENDER_CACHE_L1_DIR,RENDER_CACHE_L1_BYTES,RENDER_CACHE_REDIS_URL,RENDER_CACHE_REDIS_PREFIX,RENDER_CACHE_LEASE_MS,RENDER_CACHE_MAX_WAITERS,RENDER_CACHE_HINTS,RENDER_CACHE_FAILURE, andAPP_BUILD_ID. A closed-set variable given a value outside its set fails the boot with a message naming the variable and never repeating the value, because an environment value can carry a secret. The Live instance ledger has its ownLIVE_LEDGER_DRIVER,LIVE_REDIS_URL, andLIVE_REDIS_PREFIX, and both installs fail closed at boot on a missing tier migration or an endpoint nothing answers. -
A Live document can be cached as a shared shell with per-visitor islands. A route declaring
RepresentationClass::PublicShellStitchedstores the shell once as a composite entry cut from the slotsLiveDocument::mountcaptured, and on a hit the middleware attaches the prepared entry and still calls the route chain, so the route's own guard and tenant middleware decide the request before the Live completion middleware re-mounts every slot under authority derived for that request alone. A capture that is not exactly usable - a slot not found exactly once, a document digest that does not match - declines publication and stores nothing. The bounds are 32 slots, 64 nonce holes, 193 graph segments, and 4,096 bytes each for slot parameters and fallbacks. Because every assembly is a distinct representation, no composite response answers304or honoursIf-None-Match, and a slotted assembly is sentCache-Control: private, no-storewhile a zero-slot one keeps its class's privatemax-age. -
A stored composite can name another stored entry as one of its segments.
LiveNestedSegmentis the typed declaration andRouter::try_live_nested_segmentregisters it. The inner entry keeps its own key and its own version, so it is invalidated, republished, and fenced on its own terms rather than the includer's, and each segment declares what happens when it cannot be resolved: fail the document, omit it, or serve a bounded fallback. Nesting is bounded to three levels and sixteen nested segments, a cycle is reported as a cycle even when it would also overrun the depth, and the assembled length is checked against the body bound before a single byte is copied. Publication is refused for a composite naming an inner segment of a wider representation class, one with a longer freshness window, a transitive cycle, a graph past the depth bound, or aPrivateCachedinner segment that could never resolve. On a hit an identity-bound inner segment is reauthorized for the requesting visitor; one declared identity-free skips that, which is proven identity freedom rather than a weakening of it. -
Nodes can tell each other that a generation just moved.
RENDER_CACHE_HINTSturns on a Redis pub/sub channel carrying the dependency digests an advance just touched, defaulting to on for theredisprofile and off for the other two, riding the sameRENDER_CACHE_REDIS_URLandRENDER_CACHE_REDIS_PREFIXas the cache itself. A hint's only power is to make a node revalidate earlier than its own lease would have: it can never extend or create a lease, prove an entry current, bypass the ledger read a hit still makes, or touch the authority epoch, which is why the channel is unauthenticated by design and why an unreachable hint endpoint does not refuse the boot the way an unreachable cache tier does. A hint carries no instant, so no clock-skew assumption between nodes is needed. A deployment with hints off, one whose channel is dead, and one that never had them serve the same entries and admit the same rebuilds; only the moment of revalidation differs. -
Two console commands and nine telemetry counters are the operating surface.
render-cache:inspect <key>reports one stored entry's representation class,body_bytes, other metadata, and the current authority epoch, and it reads this process's in-process tier and nothing else, so on a shared profile it answers "what this node has in memory" rather than "what the deployment has stored".render-cache:epoch-advanceis the emergency invalidation: it advances the authority epoch, which is baked into every lookup key, so stored entries go out of reach with nothing to enumerate and nothing to delete, and on the node that runs it the effect is immediate. Neither ever prints a stored body or a raw dependency identity, which is asserted rather than merely stated. The counters aresuprnova.render_cache.lookups,.hits,.publications,.rebuilds,.stitch.assemblies,.stitch.slots,.stitch.nested,.hints, and.epoch_rewinds, all with closed low-cardinality attributes that never name a route, a key, a digest, a tier, or a provider. -
A declined lookup says exactly which contract refused it.
outcome="declined"on the lookup counter now carries areasonattribute from a closed set of thirty-eight labels, computed from a typed value at the branch that actually declined rather than reconstructed from the response afterwards. They are grouped by contract: eligibility (policy_uncacheable,method,status,streaming,sets_cookie,unsafe_header_name), observation (observation_overflowed,ledger_read_failed,handler_not_begun), classification, key mismatch, Live document, and composite build. Every label is documented in the operations chapter, and a test asserts that rather than trusting the prose.reasonis emitted only besideoutcome="declined"; a hit and a miss carry none. -
An authority epoch that goes backwards is detected, refused, and lifted past. A database restore can move the epoch to a value the deployment has already used, which would let entries published under the old higher value be proved current again. An entry or a lease stamped above the authority is now refused at any age, before any dependency comparison, and the node that detects it lifts the ledger epoch past the stamp, drops its lease, clears its in-process tier, and increments
suprnova.render_cache.epoch_rewinds. -
NOWPayments joins Stripe and Paddle as a payment adapter. The
suprnova-payments-nowpaymentscrate creates hosted invoices, verifies payment notifications, and reads payment status with the merchant API key, and registers asnowpaymentsin the ordinary provider registry throughNowPaymentsProvider::from_env(). It readsNOWPAYMENTS_ENVIRONMENT(sandboxorproduction, defaulting tosandbox; an unknown or blank value fails configuration),NOWPAYMENTS_API_KEY,NOWPAYMENTS_IPN_SECRET, andNOWPAYMENTS_IPN_CALLBACK_URL, and refuses blank credentials before any HTTP request. Its webhook endpoint isPOST /webhooks/payments/nowpaymentsthrough the sharedwebhook_routes, and it needs the exact public HTTPS callback URL and request bodies that reach the adapter unchanged.manual/payments-nowpayments.mdis the chapter. -
RBAC has the revoking counterpart of every granting helper. The surface exported the granting and checking halves of an access-control API and nothing that took access away, so removing an administrator's role meant composing statements against join tables whose semantics you had to infer - during an incident, which is when you reach for revocation.
remove_permission_from_role,remove_role_from_modelandremove_permission_from_modelare the free functions, each with the_on_guardpairing the granting side already had, andHasRoles::remove_roleandHasRoles::remove_permission_topair at the call site. A name that exists on no such guard is an error, so a typo or a call aimed at the wrong guard is loud; an assignment the model or role does not hold is a no-op returningOk, so a retry of a revocation that already landed is safe. Each call removes exactly the one assignment it names, with no bulk sweep, and every statement resolves its executor through the ambient transaction first, so a grant-and-revoke bundle insideDB::transactioncommits or rolls back as one unit. Revocation is source-specific and does not contradicthas_permission_for_model, which resolves a direct grant before a role-inherited one: taking a role away leaves a permission the model also holds directly still answering true, and the rustdoc names the second call that ends effective access. -
An application can build its router asynchronously.
Application::try_routes_asynctakes a closure returning a future, andServer::try_from_config_with_routes_asyncis the asynchronous twin oftry_from_config_with_routesthat hosts it, sharing the same prologue and epilogue. It exists becauseRenderCache::installhas to probe for the generation ledger's tables before it can assemble a runtime, and the route closure is the only place with both a container and a router - neither boot hook has one.routes,try_routes, andtry_routes_asyncwrite the same slot, so the last one called is the one the server builds. -
The Magnetar integration exposes what a partially completed sign-in actually returned.
SignInOutcomeis public, so a magic-link, OAuth, or passkey callback that resolves toSignInOutcome::FactorRequiredcan be handled rather than being reported as a failure: the framework session is not bound, and the selector it carries can be completed through the retained host engine.FactorAuthandMagnetarFactorAuthEngineare the types that hold that continuation, andinstall_magnetar_oauth_engineandinstall_magnetar_oauth_engine_with_factorinstall an OAuth engine with or without one. Magnetar bootstrap failures now name what is missing instead of reporting a generic install error. -
The queue driver contract reports whether it can honour a queue-name filter.
QueueFilterCapability(Supported,Unsupported,Unknown) is whatQueueDriver::queue_filter_capabilityreturns; the default isUnknown, notUnsupported, so a third-party driver that already overridespop_fromkeeps working unchanged, and a decorator may reject a knownUnsupportedconnection before polling but must let anUnknowndriver answer for itself.TerminalCallbackClaimis the metadata a worker gets back when it atomically claims a finished batch's terminal callbacks, carrying the durable completion time and any cancellation visible in the same critical section, so the callback decision cannot be made from a snapshot that went stale before ownership was elected. -
Schedule::try_addis the fallible sibling ofSchedule::add. Task name identifies a task in direct lookup and in the distributed keys used byTaskBuilder::on_one_serverandTaskBuilder::without_overlapping, so one name cannot identify two registered entries and a schedule that registered the same name twice had two tasks contending for one lock. Names are now exact, case-sensitive, and unique:addpanics on a duplicate and the existing task is retained, whiletry_addreturns the error for code that would rather handle it. -
Session lifetime bounds and the session migration error are public.
MAX_SESSION_LIFETIME_SECSandMAX_SESSION_LIFETIME_MINUTESare the clamps the environment parsing and the database driver apply, andSessionMigrationErroris exported so a customSessionStorecan name the failure it returns. -
Scaffolded projects are built in a production shape by construction. The generated
Cargo.tomldepends on the framework with default features off and the nine non-testingdefaults listed explicitly (filesystem,database-sqlite,database-postgres,database-mysql,vector-mariadb,web-push,localization,magnetar-oauth,media), and re-addsfeatures = ["testing"]as a dev-dependency. Cargo's resolver pulls a dev-dependency's features intocargo testand other--testsbuilds only, socargo build --bin appnever compiles a test seam into a shipped binary, andcargo testis unchanged.manual/deployment.mddocuments the shape for an existing application to adopt. -
The default cache build id comes from the application, not the framework.
#[suprnova::main]records the application crate's ownCARGO_PKG_VERSIONimmediately after loading the environment, andRenderCacheConfig::from_envresolvesbuild_idthrough an explicitAPP_BUILD_ID, then that recorded application version, then this framework crate's own version only for a binary that never expanded#[suprnova::main].RenderCacheConfig::with_build_idoverrides whateverfrom_envchose, for an application that derives its own per-deploy identifier in code. SetAPP_BUILD_IDexplicitly once per deploy: it is mixed into every lookup key, and a package version rarely changes when you ship a template, a translation, or a handler fix.
Changed
-
A worker on the failover queue connection now drains every connection, not just the primary.
FailoverQueueDriverdocumented the Laravel consequence it inherited: writes fell through the list, reads did not, so whatever failed over to a fallback sat there until somebody ran a second worker against that fallback directly.popandpop_fromnow rotate their starting connection and then scan the whole list sequentially - rotation so a recovered, continuously busy primary cannot starve work that landed on a fallback, sequential so one call cannot reserve several jobs and hand back one. Each reservation is issued a fresh aggregate token that the driver maps back to the connection that really owns it, because inner tokens are not globally unique and two backends can legitimately mint the same UUID; an expired or unknown aggregate token is treated as stale rather than sent to an arbitrary connection. Counters and all three listings aggregate every configured connection in configured order andclearattempts every one, so what an operator inspects is the backlog this driver can actually consume. A driver declares whether it can honour a queue-name filter throughQueueDriver::queue_filter_capability, which defaults toUnknownso an existing third-party driver is unaffected. -
The minimum workflow lease is two seconds, and the first heartbeat fires immediately. The heartbeat refreshes at
max(lock_timeout / 2, 1s), so a one-second lease was due for its first refresh at or after its own expiry: any claim latency or scheduling jitter opened a window another worker could walk through while the first was already running effects. The heartbeat's first tick is no longer skipped, which closes the claim-to-first-refresh window, and admission awaits an owned refresh before any user code runs, not only inside a step.WORKFLOW_LOCK_TIMEOUT_SECSbelow two is clamped with a warning that says why, and a configuration built in code that carries a shorter lease fails validation. -
A payment provider without customer records can decline transaction-mirror hydration.
WebhookHandler::mirrors_payment_transactionsdefaults totrue, so every existing provider behaves as it did; a provider that returnsfalsestill has its verified events persisted and deduplicated in the webhook audit log, refunds included, but no transaction mirror is fabricated for orders the application owns and must reconcile against authenticated provider state.try_extract_payment_snapshotis the fallible form ofextract_payment_snapshotthe hydration path uses: returningErrleaves the webhook pending so the provider retries it, whileOk(None)is reserved for an event that genuinely cannot supply a complete snapshot. Both are provided methods, so an existing driver compiles and behaves unchanged. -
A Paddle
transaction.billedis no longer read as money collected. An issued invoice does not confirm collection, and treating it as a settlement marked orders paid that had not been. Approved refund and dispute adjustments are classified as adjustments rather than transactions, with their currency taken fromdata.currency_codeand their settle time from the latest captured payment attempt where one is available; onlyWebhookHandler::parse_eventclassifies them, because the decision needs the payload's own action and approval status. The adapter also preserves the merchant correlation it was given through checkout instead of substituting a customer identifier that Paddle.js does not accept as a customer auth token, encodes non-string custom data as JSON strings consistently across customer and checkout requests, and gives its HTTP client the request deadline the pinned SDK does not set. -
The framework crate carries three new modules and two new hard dependencies.
suprnova::live,suprnova::render_cache, andsuprnova::vieware unconditional, not feature-gated, so the framework now depends on the internalsuprnova-liveengine crate and onaskamain every build. Neither module does anything until an application opts in:Router::try_live()is what installs Live's reserved routes, andRenderCache::installwith a policy is what makes the cache do anything at all.
Fixed
-
A batch job is not acknowledged until its accounting is durable. The worker acknowledged a successful batch member and then wrote the batch bookkeeping, so a failure between the two left a batch permanently short one settlement and its completion callbacks never fired. The reservation is now held until every accounting write succeeds; a rejected or uncertain write leaves it intact so visibility expiry redelivers the job, and the repository's
(batch_id, job_id)uniqueness makes the replay safe even when the first write took effect and only its response was lost. The batch repository is separately installable and may address a different database, which is why this cannot simply share the queue settlement's transaction. -
A batch's terminal callbacks are elected exactly once. Two jobs finishing the last two entries of a batch could both observe a pending count of zero and both run the completion callbacks. Settlement rows are now the source of truth and their parent batch row is locked before insertion, so concurrent jobs for one batch form a total order and exactly one final settlement observes zero - through row locks on PostgreSQL and MySQL, and through the writer lock the serialized transaction takes on SQLite. Claiming the callback bundle returns the durable completion time and any cancellation visible in that same critical section, so a worker cannot choose
thenfrom a snapshot that went stale before ownership was elected, and a non-empty batch whose pending count reached zero is sealed against positive growth. A cancellation already visible after an uncertain response is not restamped on redelivery. Envelope-construction failures collected while building a pending batch are surfaced at dispatch, which rejects the whole batch before any repository or driver mutation, instead of being swallowed by an infallible fluent builder. -
The Redis queue driver fences every terminal operation against the delivery it was issued for.
ack,nack,release, andsettlenow compare the stream entry's consumer owner and delivery count with the generation captured bypop, and one Redis script applies any successor publication and theXACKtogether, so a delayed response that makes the caller retry finds the generation gone and the retry becomes a no-op instead of a duplicate publish. Becausenackis inherently two commands (XADDthenXACK), each reservation retains a per-token lifecycle that stays addressable through every failed operation and is removed only after the acknowledgement succeeds, so a retry resumes at the step that failed rather than republishing. The driver's at-least-once contract and the requirement that handlers be idempotent are now stated in the module documentation rather than implied. Consumer identities are isolated per process, so two workers cannot claim each other's pending entries. -
A database queue reservation lasts as long as it was asked to.
reserved_untilstores whole seconds and readers compare it with the floored current time, so the current fractional second was silently taken off every lease and a subsecond timeout could round to nothing. The absolute expiry instant is now rounded up. -
Workflow step writes are fenced, an exhausted attempt budget terminalizes, and MySQL date columns match the entities that read them. A step write from a worker that had already lost its claim could land on top of the worker that now owns the workflow; writes now carry the claim's fencing token. A row whose attempt budget is already exhausted could neither be claimed nor left pending forever: the claim statement now terminalizes at most one such row per poll, with disjoint cleanup and claim predicates so a large abandoned backlog cannot turn one worker poll into an unbounded write. The early workflow migrations declared MySQL date columns as
TIMESTAMPwhile the public entities usechrono::NaiveDateTime, whose MySQL storage type isDATETIME;NormalizeWorkflowDateTimesForMysqlis an additive migration that converts them and is a no-op on PostgreSQL and SQLite. -
Cancelling a task no longer abandons a transaction's deferred effects. An aborted
DB::transactionrolls its database work back when SeaORM drops the transaction, but nothing rolled back a deferred queue push or released a held uniqueness lock for it, and an after-commit callback that was already running when the abort landed was dropped mid-effect. Callbacks now run as awaited child tasks, in registration order, so one already in flight survives its caller's cancellation, and the unstarted remainder is diverted to a detached task that either runs the after-commit list (the transaction did commit) or compensates (it did not). A panicking callback surfaces as an error instead of skipping the callbacks behind it, and aCOMMITthe database refuses after the closure has already taken the request is handled rather than panicking. -
Cross-disk copies and read-through caching clean up after a cancelled task. A mid-stream failure already discarded the partial destination object, but a cancellation returns no error at all, so the writer was simply dropped and a truncated object or a staged multipart upload was left behind. The destination writer is now owned by a guard across the transfer: an error settles inline with the same abort and delete as before, while a cancellation diverts that cleanup to a detached task, and the cleanup itself runs to completion even if the awaiting task is cancelled during it. Cleanup never targets a published object, because another writer may have won the condition. Local filesystem work is kept alive until it finishes, since dropping a Tokio filesystem future does not stop the blocking work it has already submitted.
-
Two throttle clauses that hashed to the same storage identity no longer share one counter. A rate-limit rule with several finite clauses could collide, so one clause's hits counted against another's budget. Colliding clauses now reserve deterministic, unambiguous counter and timer identities, computed once so the gate, the deferred hit, and the response headers all use the same key, and legacy keys are kept where no collision exists.
-
A sliding-window sweep no longer erases history a longer quota still needs. The in-memory limiter dropped a bucket whose last hit was older than the window it was asked about, which discarded the record enforcing an already-observed longer quota on the same key. A bucket is now retained until its last recorded hit is older than both the supplied window and the longest quota window observed for it. A decrement below the minimum amount is handled rather than under-counting.
-
The in-memory cache driver rejects an increment against a non-integer value. Redis
INCRBYandDECRBYrefuse a live non-integer and leave its value and TTL alone; the memory driver overwrote it, so the same code behaved differently against the two backends. It now parses before inserting and leaves the entry untouched on error. Separately, Redisaddinstalls a missing untagged value and clears stale tag metadata in one script, so a newer tagged overwrite can no longer land between the conditional write and the cleanup that follows it. -
Inertia one-shot session data survives a failed response.
SessionMiddlewareages_flash.new.*into_flash.old.*before the handler runs, so a response that failed while being constructed left those values to be deleted by the next request's aging pass - the user lost the validation errors or the flash message that explained what went wrong. A request-scoped guard now reflashes them on every uncommitted exit, cancellation included, and removes them only after the complete response has been built. -
Fanout broadcasting waits for the backend to say it wrote.
SeaProducer::sendonly enqueues, and the returned future is what reports the actual backend write, so a delivery was reported as sent when it had only been queued. Every send in a pass is now polled for its receipt under one deadline, which also stops an unavailable broker from holding an application request open indefinitely. Membership heartbeats hold the read guard until every snapshot heartbeat is enqueued, so a concurrent untrack cannot be overtaken by a stale heartbeat. -
suprnova generate-typesnever leaves a stale or truncated artifact behind. A scan that ended early used to overwrite the output with whatever it had, so a transient parse failure silently deleted type definitions the application still used. File generation now refuses to overwrite an artifact after an incomplete scan, writes atomically through a collision-free sibling temporary file with bounded retries, and skips the write entirely when the contents are unchanged. An output symlink keeps its previous behaviour: the resolved target is replaced atomically and the link stays in place; a changed read-only destination is rejected. -
Two
suprnovacommand failures are reported instead of swallowed.suprnova newreports a failedgit initrather than presenting a project as fully created, andsuprnova workflow:installvalidates the migration path before creating any directory, so an invalid path fails without leaving a half-made tree behind. -
A savepoint and its deferred-effect registry agree on identity. The savepoint statement and the registry mark used the caller's original spelling, but names are case-insensitive and PostgreSQL additionally aliases names sharing their first 63 ASCII bytes, so
ROLLBACK TOcould unwind a savepoint whose deferred effects the registry had filed under a different key. Both now share one validated, backend-canonical identity. The accepted 64-byte API limit is unchanged. -
suprnova <command> --helpprints help instead of running the command. The CLI declared its ownhelpflag and consulted it only when no subcommand had been given, so every other--helpprinted the banner and then executed the command anyway.suprnova migrate:fresh --helpdropped every table in the database, and the guard that would have stopped it refuses only in production whileAPP_ENVdefaults tolocal. Clap now owns-hand--helpon the top level and on every subcommand, in either argument order, and the curated banner is still what the top level prints. A test enumerates the subcommands from clap itself, so a subcommand added later is covered without anyone remembering to add it. -
A scaffolded frontend no longer pins the CSRF token it read at boot. The generated Vue, Svelte, and React entry points read
<meta name="csrf-token">once at module load and attached that value to every Inertia visit. Logging in rotates the session, the captured token goes stale, and the next state-changing visit - typically the logout - was refused with419 CSRF token mismatch. Every generated application shipped with it. The hook is gone: the Inertia client reads theXSRF-TOKENcookieCsrfMiddlewaresets and echoes it back inX-XSRF-TOKENitself, once per request, so the value that travels is the one the browser holds at that moment. Server-side verification is unchanged and both header names are still accepted. The manual chapter and thesuprnova::csrfmodule documentation named the old hook as the thing to do; both now name it as the thing to avoid. -
A scaffolded application's XSRF cookie is usable over local HTTP.
CsrfMiddleware::new()defaults the JS-readableXSRF-TOKENcookie toSecure, while the generatedenv.examplesetsSESSION_SECURE=falsefor development, so a browser would neither store nor return the cookie overhttp://localhostand every state-changing request in development was refused with419. The generated bootstrap now passes itsSessionConfigtoCsrfMiddleware::with_session_config, which copies the session cookie'sSecure,SameSite,Domain,Path, and lifetime onto the XSRF cookie so the two cannot drift apart. Nothing is weakened: token validation, the default origin policy, and the production guards are unchanged. -
suprnova make:commandappears on the help screen. The command scaffolds a console command intosrc/commands/and had no line on the curated screen, so the only way to learn it existed was to read the source. The screen is now checked against the subcommand list clap reports, in both directions, so neither a missing line nor a line naming no command can survive.
Upgrading
-
Most applications need no code change. Live and RenderCache are both opt-in:
suprnova::livedoes nothing until a router callsRouter::try_live(), andsuprnova::render_cachedoes nothing until a route is opted in andRenderCache::installis called. Everything else in this release is a fix to behaviour you already had. The version is 2.0.0 because the framework's surface grew by two whole subsystems and because of the specific behaviour changes listed below, not because the ordinary application API was rearranged: no public item in the framework crate, the macro crate, or the payment, Magnetar, and Web Push adapter crates was removed or renamed. -
Rebuild times and dependency footprint go up. The framework now depends on the internal
suprnova-liveengine crate and onaskamain every build, becausesuprnova::live,suprnova::render_cache, andsuprnova::vieware unconditional modules rather than features. There is nothing to enable and nothing to disable. -
An application that never uses RenderCache pays one schema probe per process.
RENDER_CACHE_ENABLEDdefaults totrue, so the first ORM write a process makes outside a transaction asks once whether the RenderCache migration is present; finding it absent, that process is closed for the rest of its life and issues no further RenderCache SQL. SetRENDER_CACHE_ENABLED=falseto skip even that one statement. The probe never runs on a caller's transaction, so it cannot poison a write you are making. -
Anyone building a
WebPushClientfrom an already-builtreqwest::Clientmust act.WebPushClient::with_clientnow refuses to send under the defaultEndpointPolicy::Strictand returnsWebPushError::UnconfinedRedirects, because an already-built client's redirect policy cannot be inspected and reqwest follows redirects by default. Move toWebPushClient::with_client_builder, which honours every transport option you were setting (proxy, TLS, timeouts) and forces redirects off, or callWebPushClient::allow_unconfined_redirectsif you know your client is safe.WebPushClient::newis unaffected. -
Signed URLs issued before the upgrade that carry a trailing slash stop verifying. Signing and verification both used to trim a trailing slash before hashing; both now hash the path exactly. A URL signed as
/orders/1still verifies at/orders/1, and only at/orders/1- a proxy that appends a slash now producesSignatureVerdict::Invalid. If a proxy or a framework in front of your application normalizes paths by adding a slash, sign the URL the way the request will arrive. -
A schedule with two tasks of the same name now fails at registration.
Schedule::addpanics on a duplicate, keeping the task already registered. Rename one of them, or switch toSchedule::try_addand handle the error. Names are exact and case-sensitive. -
A workflow lease shorter than two seconds is clamped or refused.
WORKFLOW_LOCK_TIMEOUT_SECSbelow2is clamped to2with a warning naming the reason; aWorkflowConfigbuilt in code with a shorter lease failsvalidate. If you were running a one-second lease deliberately, the heartbeat could not refresh it before it expired. -
A MySQL application using workflows should add one migration.
suprnova::workflow::migrations::NormalizeWorkflowDateTimesForMysqlconverts theworkflowsandworkflow_stepsdate columns fromTIMESTAMPtoDATETIME, which is whatchrono::NaiveDateTimeactually stores. It is additive, and a no-op on PostgreSQL and SQLite. MySQL may rebuild and lock both tables while applying it, so schedule it accordingly. A project created bysuprnova newgets it wired automatically. -
AuthMiddlewarenow resolves the user on every guarded request. It used to accept the presence of a persisted identifier. The behaviour change is that a session belonging to a deleted or soft-deleted user stops authorizing. The cost is smaller than it looks: the resolved user is cached for the rest of the request, so a handler that already calledAuth::user()pays nothing extra and the lookup has simply moved from the handler to the middleware. Only a guarded request whose handler never resolved the user gains a provider lookup it did not make before. An application with no user provider bound keeps the identifier-only path unchanged.BasicAuthMiddlewarein its non-stateless form now requires the guard it names to exist and to be a stateful guard. -
destroy_all_for_usercosts more and revokes more. It now reads the surviving session rows and compares the guard identities inside each payload, in addition to the indexeduser_idmatch, so it reaches sessions authenticated through a named guard alone. Revocation is rare enough that correctness was chosen over index use; if you call it on a hot path, that is worth knowing. -
A
POSTorPATCHretried after a transport error now needsretry_non_idempotent. The5xxbranch already required it; the transport-error branch did not. If you were relying on a dropped connection being retried for a non-idempotent request, opt in explicitly. -
A production process with a missing or malformed
APP_KEYnow fails at#[suprnova::main], not atServer::from_config. That includes a console binary or a worker entry point that never builds a server. Local, development, and testing environments still generate a transient key and warn.APP_PREVIOUS_KEYSis accepted as an alias forAPP_KEY_PREVIOUS; if both are set with different values, the Suprnova name wins and the duplicate is named in a warning you should act on. -
A worker pointed at a
failoverqueue connection now drains every connection in the list. If you were running a second worker against a fallback connection directly - which the 1.3.3 notes told you to do - that worker and the failover worker will both be draining it. Remove the extra worker, or keep it and accept the competition. Counters and listings now aggregate every connection, so a dashboard readingpending_sizeon the failover connection will report a larger number than it did. -
Custom store and driver implementations get fail-closed defaults, never weakened behaviour. Magnetar's provider-token, ceremony, and remember stores gained methods for the atomic operations described above; each has a default that refuses rather than performing the operation non-atomically, so an external implementation still compiles but will report failure until it implements the method.
WebhookHandler::mirrors_payment_transactionsandtry_extract_payment_snapshot,QueueDriver::queue_filter_capability, andGlobalScope::dependencyall have defaults that preserve the previous behaviour exactly. -
To adopt Live, bind a registry during bootstrap with
App::singleton(crate::live::registry().expect("Live component registry")), install the reserved routes withRouter::try_live_withand a guard carrying yourAuthMiddleware,LiveTenantMiddleware, andRateLimitMiddleware, and registerCsrfMiddleware::new()globally - Live verifies its own origin proof, so you do not need to widenOriginPolicyfor the whole application, and if you widened it for something else, narrow it back. UseAuthMiddleware::optional()on the Live guard if you want anonymous visitors to act on public seeds;AuthMiddleware::new()answers401for every anonymous request before any engine work. Then runsuprnova live:makeandsuprnova live:check.manual/live.mdhas the complete walkthrough. -
To adopt RenderCache, add
suprnova::render_cache::migration::Migrationto yourMigrator(andsuprnova::render_cache::migration::TierMigrationas well if you run thedatabaseorredisprofile), opt routes and groups in withRouter::try_render_cacheandRouter::try_render_cache_group, and finish withRenderCache::install. Becauseinstallis asynchronous - it probes for the ledger's tables before assembling a runtime - the router has to be built throughApplication::try_routes_asyncrather thantry_routes. The install has to come after every middleware that establishes request-scoped locale, session, or identity, and after every route and group has been opted in. A shared profile refuses to boot without its tier migration or with an endpoint nothing answers, which is deliberate. -
Set
APP_BUILD_IDonce per deploy. It is mixed into every RenderCache lookup key, so changing it is what stops a new build from serving entries the previous one published. Its default is your application crate's package version, which does not change when you ship a template, a translation, or a handler fix. A commit id works:APP_BUILD_ID=$(git rev-parse --short HEAD). -
Consider moving your
Cargo.tomlto the production build shape. Declaresuprnovawithdefault-features = falseplus the nine non-testingdefaults you use, and re-addfeatures = ["testing"]under[dev-dependencies]. Cargo pulls a dev-dependency's features intocargo testand other--testsbuilds only, so your shipped binaries stop carrying test seams whilecargo testkeeps working unchanged. A project created bysuprnova newis already in this shape;manual/deployment.mddocuments it for an existing one. -
If you consumed the standalone
@suprnova/liveruntime or wrote your own subscription host, the registered-event descriptor changed.DESCRIPTOR_SCHEMA_VERSIONmoved from 1 to 2 and the descriptor's registered-event fields are nowmaximum_hops,maximum_fanout, andpayload_contractrather thanmaximumHops,maximumFanout, andpayloadContract- they were the only camelCase keys in a public JSON contract that is snake_case everywhere else. A descriptor signed at schema version 1 is refused withSubscriptionErrorKind::InvalidDescriptorrather than being read with three absent fields. Nothing in a 1.3.7 Suprnova application consumed this contract, so for most readers there is nothing to do.
1.3.7 - 2026-08-26
Added
- Where the Inertia error page middleware sits is now yours to choose, and documented.
Inertia::installregistersInertiaErrorPageMiddlewareinnermost of the Inertia layer, so it covers the handler, the route middleware, and everything you register after that call - which is why the scaffold putsCsrfMiddlewarebelow it. It does not cover anything registered above the call, because a middleware that answers without callingnexthands its response to nothing registered inside it. The case that bites is a lapsed session posting a form:CsrfMiddlewareregistered above the install answers419with{"message":"CSRF token mismatch."}and the user gets the Inertia crash modal on the one flow they are most likely to hit; an outer rate limiter's429and an auth guard's401are the same. Registering the middleware yourself, further out, already worked in 1.3.6 - the type was public and registration is idempotent per type, so an earlier registration kept its place - but nothing said so and nothing ininstallacknowledged it, which made it an accident rather than a contract. It is a contract now: registerInertiaErrorPageMiddleware::new("Error")afterSessionMiddlewareandLocaleMiddlewareand before the middleware whose rejections it should cover, andinstallchecks for it, logs atdebug, and skips its own. The component you named at that registration is the one rendered, so you name the page once and.error_page(...)on the config becomes optional - it is still what makesinstallregister a middleware for an app that does not place one itself. The two ordering rules are documented on the type and in the manual.
Fixed
- An SSR page has one
<title>, and it is the page's own. The HTML shell wrote itsdefault_titleand then the SSR worker's head verbatim, so every page rendering a title through Inertia'sHeadcomponent produced a document with two<title>elements and the framework's generic one first. First is the one the browser tab, the crawler and the link preview read, so the real title never showed. A worker head carrying a title now replaces the shell's title rather than joining it - bothdefault_titleand a per-responseInertiaResponse::title(...)stand down; a head without one leaves the shell's title exactly where it was. - The document declares the language it is written in. The shell hardcoded
<html lang="en">, so a reader switched to Japanese got Japanese prose in a document claiming to be English - a screen reader picks its voice from that attribute and a search engine takes it as the page's language signal. It now carries the locale in effect for the request: whatLocaleMiddlewaredetected, then aLang::set_localeoverride, then the configuredAPP_LOCALE, in the same BCP 47 formLocalerenders (pt-BR,zh-Hans). This holds for the error page too, which is rendered on the way out and was the case that surfaced it. Without thelocalizationfeature the shell keepsen.
Upgrading
- Nothing is required. Both fixes apply to every Inertia app on upgrade, and
Inertia::installbehaves exactly as it did for an app that does not register the error-page middleware itself. - An app that spliced
<html lang="...">into the finished document with a middleware of its own can delete it - the shell does it now, from the same locale that middleware was reading. - An app whose
CsrfMiddleware, rate limiter, or auth guard is registered beforeInertia::installshould registerInertiaErrorPageMiddleware::new("Error")afterLocaleMiddlewareand before that middleware, so its rejections render the error page instead of reaching the client as raw JSON.installthen skips adding its own, and the component you named at the registration is the one rendered, so.error_page("Error")on the config is optional - keep it or drop it. The scaffoldedbootstrap.rsregisters CSRF after the install, so a project generated bysuprnova newneeds no change. - An app that renders its own
<title>through Inertia'sHeadcomponent under SSR will see the shell's title stop appearing in the document - bothInertiaConfig::default_titleand a per-responseInertiaResponse::title(...). That is the fix: the page's own title is the document's only one. If you were relying on the shell's title as a prefix or suffix, move it into theHeadcomponent where the rest of the title lives.
1.3.6 - 2026-08-26
Added
- Framework errors can render your own Inertia page instead of the client's crash modal. A user without a permission clicked a nav link into a guarded route and got Inertia's "All Inertia requests must receive a valid Inertia response, however a plain JSON response was received" screen: the
403carried the framework's JSON error body and noX-Inertiaheader, so the client refused it. The same held for an unrouted404, a rate-limited429, and a failing handler's500. Name a page component withInertiaConfig::error_page("Error")and those responses render that page at their original status, withstatus,message, and - when the error carried one -request_idprops. Every header the error response set survives the swap except the ones that only described the body being replaced (Content-*,Transfer-Encoding) or governed how it could be stored (Cache-Control,Expires,Age,ETag,Last-Modified), soRetry-Afteron a429,WWW-Authenticateon a401,Vary, andSet-Cookieall still reach the client. The page setsCache-Control: no-cache, privatefor itself: it carries your shared props, so it must never be stored by a shared cache and served to a different visitor, whatever the response it replaced permitted. An Inertia visit gets the JSON page object; a hard navigation gets the full HTML shell, so pasting the URL into the address bar works too. Everything with an owner is left alone: validation422s still redirect back to the form,X-Inertia-Locationbounces and responses that already are Inertia pages pass through, and a client whoseAcceptprefers JSON keeps the exact body it got before.suprnova newscaffoldsfrontend/src/pages/Error.*and sets.error_page("Error"), so new projects are covered without doing anything.
Fixed
- A local disk no longer refuses a legitimate path because another task touched it. The path guard resolved each component of a path with two probes and combined them into one verdict, so ordinary concurrent activity could be read as a symlink escape: a component that
canonicalizehad just reported missing, and that another task then created as an ordinary file, came back asPermissionDeniednaming a symlink that was never there. It bit hardest where writers contend by design - a losingwrite_with(..).if_not_exists(true)racer got that refusal instead ofConditionNotMatchwhenever the winner published the key between the two probes, which under a loaded test suite was roughly a third of runs. Each component is now classified from a single pass,symlink_metadatafirst: nothing there is free space, an ordinary file or directory is resolved and confined as before, and only a symlink that still cannot be resolved is refused. A component that vanishes mid-classification is looked at once more rather than refused. Every symlink refusal is unchanged.
Upgrading
- Nothing changes for an existing app until it opts in.
InertiaConfig::error_pagedefaults toNone, andInertia::installregisters the error-page middleware only when a component is named, so error responses keep their exact bodies. To adopt it, add a page component namedErrorbeside your others (it receivesstatus,message, and an optionalrequest_id) and chain.error_page("Error")onto theInertiaConfigyou pass toInertia::install. A handler that panics stays out of scope: the panic net wraps the whole middleware chain, so its synthesized500is built after every middleware has unwound. ReturnErr(...)rather than panicking and the error page covers it. Note that the gate is the body's shape, not its author: at an error status, an empty body, a JSON object whosemessageis a string, and the router's own404 Not Foundtext are rewritten no matter which middleware built them, and onlymessageandrequest_idsurvive into the props. A response that must keep its own JSON body should key its text as something other thanmessage, or setX-Inertia: trueon itself. And registerLocaleMiddlewarebeforeInertia::install: the error page is rendered on the way out, after every middleware registered inside the Inertia layer has returned, so a locale scope opened inside it is already gone and every error page would render in the app's default locale. The scaffoldedbootstrap.rsnow does this, and the same reasoning applies to any request-scoped middleware of your own whose state the page's shared props read.
1.3.5 - 2026-08-26
Changed
- Every changelog section reads in all six manual translations. The de, es, fr, ja, pt-BR and zh-Hans manuals used to carry the 1.3.0 to 1.3.2 sections in English behind a translator's note, and older sections with stray English lines; every section from 1.3.5 back to 0.1.0 is now translated, and the notes are gone.
Fixed
-
Local-filesystem disks publish every object in one step.
Storage::register_fsandregister_fs_withnow stagedisk.write(...),disk.writer(...), anddisk.copy(...)as a temp file under<root>/.suprnova-atomic/and publish it onto the target with a singlerename(2), so none of them is ever observable at a partial length. Before this, the driver opened the target withcreate + truncateand streamed into it in place: a concurrent reader got an empty or half-written object for the whole duration of the write, and a crash mid-write left a truncated object at the live path.abort()on a writer now discards the staged file instead of failing withUnsupported. -
write_with(..).if_not_exists(true)is a true exclusive create on a local disk. It is published withlink(2), which fails atomically in the kernel when the target exists, so exactly one of any number of racing callers succeeds and every other one getsConditionNotMatchhaving written nothing. A staged write published by a plain rename would have degraded the condition to a check followed by an overwrite, silently discarding all but the last writer - which is the opposite of what the primitive is reached for. -
An
appendthat creates the object is still an append. Appends are the one in-place operation on a local disk, and that now holds for the first one too, so two writers appending to the same missing object both land instead of one staging its own copy and overwriting the other. -
suprnova serveno longer rebuilds a project nobody has touched, and neither doessuprnova generate-types --watch. Both watchers classified a filesystem event by its path alone, and the generator reads every.rsfile under the samesrc/tree they are watching - so on Linux, where the kernel reports those reads, each regeneration scheduled the next one. A freshly scaffolded project regenerated its types and restarted its backend every half second, forever, without a single source edit. Only events that mean the bytes on disk actually changed count now.generate-types --watchalso had no debounce at all, so it acted on the first file of a burst rather than the last; it now sharesserve's 500 ms trailing edge, and both watchers share one implementation so the next fix cannot land in only one of them. The generator compares before it writes, so a regeneration whose output is byte-identical leaves the file, and its mtime, alone. -
The backend watcher is scoped to the paths the server is built from.
cargo watchran with no-w, so it watched the whole non-gitignored project: saving a Svelte component, or regeneratingfrontend/src/types/inertia-props.ts, rebuilt the framework and restarted the server. It now watchessrc/,cmd/,Cargo.toml,Cargo.lock,.env, andlang/- the build inputs plus the two trees read once at boot - each included only when it exists, since cargo-watch refuses a-wpath that does not.cmd/is where the full-stack scaffold keeps the server binary'smain.rs. The invocation also passes--no-vcs-ignores, because cargo-watch applies.gitignoreto explicitly named-wroots and the scaffold ignores.env, which would otherwise leave-w .envwatching nothing;-whas already narrowed the surface, so the flag cannot widen it. Frontend edits and generated.tsfiles no longer restart the backend. -
serde_json::Valuegenerates asJsonValueinstead ofunknown. It used to degrade tounknownand warn that it "isn't a struct this project defines", advice that is wrong for a JSON document - and the scaffold's own login and register pages tripped it twice on every regeneration, so every fresh project warned out of the box. It now emits a recursiveJsonValuealias, declared once at the top of the generated file and only when something references it. A bareValuemaps there too, unless the project defines aValuestruct of its own. -
Neither
generate-typesnorservereports a file it did not write as generated. Because a pass now writes only when the emitted content differs,Generated <path>was a claim about the filesystem that was false on every rerun of an unchanged project.generate-typessays<path> is up to dateinstead, in one-shot and--watchalike, andserve's startup pass saysN type(s) up to date → <path>, keeping the count.serve's file watcher now stays silent on a regeneration that wrote nothing, in text and under--jsonboth: atypes_regeneratedevent means the generated file on disk is different now, so silence after a save tells you your edit did not change any prop shape.
Upgrading
.suprnova-atomicis reserved at the root of every local disk. The staging directory has to live inside the root - a sibling of the root can be on a different filesystem when the root is a mount point, and every rename would fail withEXDEV- so the name is reserved rather than merely conventional. Any path whose first component is.suprnova-atomicis now refused with a permission error (read, write, delete, stat, list alike), as is any path that resolves into the directory through a symlink, and the entry is filtered out offiles,directories,all_files, andall_directories. If a disk root already contains a.suprnova-atomicentry of your own, it is no longer reachable through that disk: move it aside before upgrading. A regular file of that name is refused at registration with a message saying so, rather than failing later inside the driver. The name is exported assuprnova::ATOMIC_STAGING_DIRso backup and sync tooling can exclude it.- Publishing by rename replaces the target's inode. Rewriting an object on a local disk no longer preserves its mode, owner, or hard links, and a reader holding an open descriptor keeps the old content instead of seeing the new bytes. That is the standard cost of atomic publishing, but it is a behavior change if you were relying on either.
- A conditional write needs a filesystem with hard links.
if_not_existsis published withlink(2), which is unsupported on FAT, exFAT, and some network filesystems. There it fails outright rather than falling back to a check followed by an overwrite, because a fallback would hand you an exclusivity guarantee that does not hold. Nothing else on the disk is affected. - A first
appendthat fails leaves an empty object. An append is the one operation that is not published in a single step, so the object is created before the bytes land; a failed or aborted first append leaves it behind, exactly as an append onto an existing object always has. - A dangling symlink in the disk root is refused, not overwritten. A path whose symlink target does not exist can no longer be written, appended to, copied onto, moved onto, or deleted through the disk.
1.3.4replaced such a link with a regular file; the guard cannot prove where an unresolvable link leads, and creating through one creates the link's target anywhere on the host, so it now refuses. Remove the link outside the disk if you meant to write there. - Nothing sweeps the staging directory. It holds in-flight temp files plus whatever a process that died mid-publish left behind, so a host in a crash loop grows it without bound. Emptying it while nothing is writing to the disk is safe; excluding it from backups is recommended.
1.3.4 - 2026-08-25
Added
-
Read-through disks take a
copyflag and resolvecopy/renameacross the fallback. Setcopy: falseonReadThroughConfigto serve fallback hits without writing them through, which turns the disk into a transparent overlay and narrows each fetch to the range you asked for.copyandrenamenow stream a source that lives only on the fallback across to the primary destination; arenamealso deletes the fallback source, so a later read cannot resurrect the moved object. Conditions carry across that streaming path:if_not_existsstill refuses an existing destination, a copy's source version selects which object the fallback hands over, and a copy'sif_matchis refused withUnsupportedrather than silently dropped. A transfer that fails partway removes only a destination it created, so it cannot destroy an object that was already there. -
Debounced jobs and debounced queued listeners.
Job::debounce_for()collapses a burst of dispatches into one run, one window after the most recent one, carrying the newest payload. It is the mirror ofpush_unique, which keeps the first dispatch and suppresses the rest.Job::max_debounce_wait()stops a continuous burst from deferring the work forever, andJob::debounce_id(&self)scopes the window per entity so twenty updates to one order collapse without touching another order's.Queue::push_debounced(job, DebounceOptions)sets the window at the call site, andDebouncedListener::new(window, build).keyed_by(...)debounces an event listener with the key derived from the event - a plainQueuedListeneralready honors a window the job itself declares. Every dispatch is still enqueued; the collapse is settled at the worker, which acknowledges a superseded envelope and emitsJobDebounced. Debouncing fails open: an expired or evicted window runs the job rather than dropping it. Each actual run starts a fresh maximum-wait window, so a burst always measures its maximum wait from its own first dispatch rather than inheriting the previous burst's. A job cannot declare bothdebounce_forandunique_id, and chains and batches refuse a debounced job - a superseded link would strand the rest of its chain, and a superseded batch job would leave the batch's pending count above zero forever. The envelope carries two additive fields for this and stays byte-identical on the wire for every non-debounced push. -
Storage::register_read_throughcomposes two disks into a read-through disk. Reads and metadata resolve against the primary first and fall back to the second disk; anything found on the fallback is written through to the primary, so a store migration completes under real traffic. Writes and listings stay on the primary, and a delete removes the object from both disks. Setthrow_on_promotion_failurewhen a failed promotion must surface instead of degrading to a fallback read. A promotion is published atomically, so no reader can see a half-written object, and it carries the fallback object's content type, cache control, content disposition, content encoding, and user metadata across. A versioned or conditional read is passed through with its condition intact and served without being promoted. -
Queue::forwardredirects a whole queue by name. WhereQueue::routeis keyed by job type,Queue::forward("default", "high")is keyed by queue name - the lever for retiring a pool, absorbing a backlog, or moving work off a pool you are about to take down, without touching a single job or route. It applies on both sides: new pushes that resolved todefaultland onhigh, and a worker started with--queue=defaultdrainshigh, so the destination cannot collect work nobody claims. Forwardingdefaultcatches jobs that named no queue. A forward is a single lookup, never a chain, so a swap (a -> bwithb -> aalso registered) or a longer rotation is a coherent pool exchange rather than a loop - exactly like Laravel, whose resolver is the same single lookup. Pausing is still evaluated on the names a worker was started with, soQueue::pause(&connection, "default")stops that worker even whiledefaultis forwarded.Queue::forward_on(from, to, connection)restricts a forward to one connection name, compared against this process's connection name rather than a job's declared connection, so both halves of the redirect gate on the same value.Queue::forward_for(from)reads a forward back, andQueue::try_forwardis the fallible sibling. The inspection calls (Queue::pending_jobsand its siblings) deliberately do not follow a forward, so a backlog left behind on a forwarded queue stays visible. -
Read-shaped Redis commands retry a transient failure instead of surfacing it. The connection manager already reconnected in the background, but the command that hit the dead socket still failed your call.
GET,EXISTS, theSCANandSSCANpages behindCache::flush/Cache::flush_tags, the queue driver'sXLEN/ZCARD/XPENDINGreads, and the rate limiter'sRetry-Aftercomputation now retry once after a short pause.REDIS_COMMAND_RETRIESadds further retries on top, clamped at 10. Budget the retry in seconds rather than milliseconds: the second attempt waits for the replacement connection, so it costs the driver's whole connect and response budget, and a timed-out command counts as transient as well as a dropped one. Writes never retry at any setting: a transient error means the connection failed, not that the server refused the command, so repeating aSET, anINCR, a lock acquisition, a rate-limit hit, or a queue pop could run it twice. Error messages are unchanged, so anything matching on them keeps working. -
A paused worker now tells you it is paused.
queue:workprints one line per transition -2026-08-25 14:03:11 Queue billing PAUSED, andRESUMEDon the way back - and the worker emitsWorkerQueuePaused/WorkerQueueResumedso you can route the same signal into your own alerting. These are the worker-side pair; the existingQueuePaused/QueueResumedfire in whichever process ranqueue:pause, which is never the worker, so until now a worker that went quiet because somebody paused its queue was indistinguishable from a hung one. Each event fires once per transition, not once per poll. Theirqueuefield is optional: a worker started without--queuedrains everything and has no queue names to report underpause_all, so it reportsNonerather than inventing a name a listener could match on. -
?include=paths are capped at five segments, andmax_relationship_depthmoves the ceiling. A cyclic relationship graph turns?include=author.posts.author.posts...into fan-out a client controls, bounded only by the query string. Paths are now truncated while they parse; callsuprnova::max_relationship_depth(n)inbootstrap::register()to change the limit, or pass0to turn includes off. -
Gt,Gte,Lt, andLtecompare a field against a number or against another field.CompareWithnames the operand and the measure in one value:Numberfor a literal,NumericFieldfor a numeric sibling, andLengthFieldfor a sibling compared by character count. An operand the rule cannot measure fails the field instead of panicking. -
Three membership rules join the built-in set:
InArray,Contains, andDoesntContain.InArraychecks a value against another field's list, and you pass the list directly instead of naming the field in a rule string.ContainsandDoesntContainrun over a JSON array and match a parameter only against a string element, so1and"1"stay distinct. -
The database pool now has liveness knobs.
DB_IDLE_TIMEOUT,DB_MAX_LIFETIME,DB_ACQUIRE_TIMEOUT,DB_TEST_BEFORE_ACQUIRE, andDB_PING_AFTER_IDLEcontrol when the pool closes, recycles, and pings a connection, with matchingDatabaseConfig::builder()setters. Each is unset by default, so an existing deployment's pool behaves exactly as it did. Use them when a NAT gateway or firewall drops idle connections: sqlx exposes no libpqkeepalives_*equivalent, so pool recycling is the mechanism. -
db:seed <Class>reports its progress. A targeted run prints aRUNNINGline before the seeder and an elapsed-millisecondsDONEline after it. A baredb:seedstays silent. The formatter,suprnova::two_column_detail, is available to your own#[command]handlers. -
Many-to-many relations now filter on pivot columns.
where_pivot,where_pivot_op,where_pivot_in,where_pivot_not_in,where_pivot_null,where_pivot_not_null,where_pivot_between,where_pivot_not_between,where_pivot_group, and theiror_twins constrainget,first, andcountonBelongsToMany,MorphToMany, andMorphedByMany.where_pivot_grouptakes a closure and renders one parenthesised group, so it stays atomic inside a followingor_where_pivot. Pivot filters apply to reads only:attach,attach_with,detach, andsyncreturn an error while one is set, and eager loading does not carry them. -
where_binarycompares column values byte for byte. The family (where_binary,or_where_binary,where_not_binary,or_where_not_binary) ships onBuilder<M>, andwhere_binaryandwhere_not_binaryship onDB::table(...). MySQL and MariaDB emit= binary; Postgres and SQLite return an error when the query renders, rather than falling back to a collation-dependent match. -
Builder::try_to_sql_with_bindings_forrenders SQL for a dialect without panicking. It is the fallible sibling ofto_sql_with_bindings_for, for the cases where a builder legitimately cannot render for a backend. -
Model::refresh_for_updatereloads a row under aFOR UPDATElock. Call it inside a transaction when you need the row's current state and the exclusive lock in one statement. SQLite has no row-level locking, so the lock clause is a no-op there. -
Builder::or_where_keyandBuilder::or_where_key_notadd primary-key filters as a disjunction. Both fold into the precedingWHEREclause the same wayor_wheredoes, and both shipor_filter_keyandor_filter_key_notaliases. -
Builder::in_order_ofsorts rows into an explicit sequence. Pass a column and the values in the order you want them; rows whose value is not in the list sort last. The values bind as parameters, so they are safe to take from request data.
Fixed
- The maintenance bypass cookie now expires on the server. The 12-hour TTL was a
max-agethe browser enforced, so a captured cookie kept working until you rotated the secret. The encrypted payload now carries the deadline, and every request re-checks it. suprnova serveruns a frontend-less project. A project scaffolded withsuprnova new --apihas nofrontend/directory, andserverejected it as "No frontend directory found. Are you in a Suprnova project directory?" unless you passed--backend-only. It now skips the Vite pane and the TypeScript generation that feeds it, and serves the backend.--frontend-onlystill fails on such a project, with a message that says why.
Upgrading
- Bypass cookies issued before this release stop working. The cookie's payload changed from the bare secret to a sealed
{ secret, expires_at }object, and a payload with no deadline is refused. Visit the secret URL once after upgrading to get a new cookie. Nothing else changes:down,up,--secret, and--with-secretall behave as before. - An include path longer than five segments now returns its first five relationships instead of all of them. Nothing outside a resource's allowlist was ever reachable, so no response gains data; a deep path loses its tail. One status code changes with it: a path whose over-deep tail names a relationship the resource does not allow is truncated before anything validates it, so it now returns
200with the segments that survived where the full path used to return400- adjust any client or test asserting on that rejection. Raise the ceiling withsuprnova::max_relationship_depth(n)if your API documents paths longer than that. DatabaseConfiggained five public fields. Code that builds one with a struct literal no longer compiles. UseDatabaseConfig::from_env()orDatabaseConfig::builder(), both of which fill the new fields with the defaults that preserve today's pool behavior.
1.3.3 - 2026-08-25
Added
-
Failover queue connection.
FailoverQueueDriverwraps an ordered list of connections: a push the first one refuses is retried on the next, and so on down the list. Wire it from env withQUEUE_DRIVER=failoverplusQUEUE_FAILOVER_CONNECTIONS=redis,database(each entry reads its own driver's variables, so adatabaseentry still needsDB::init()first and still brings its failed-jobs store), or build it directly withFailoverQueueDriver::new(vec![(label, driver), ...]). Only writes fall through:pushandbulk_pushwalk the list, whilepop,pop_from,ack,nack,release,settle,clear, all four counters and all three inspection listings delegate to the first connection and no other, because a reservation token is meaningful only to the driver that issued it. The operational consequence is documented rather than papered over: a worker on the failover connection drains the primary only, so whatever failed over to a fallback needs its own worker.bulk_pushpushes each envelope separately rather than forwarding a batch, which both preserves each envelope's ownavailable_at(Laravel #60950) and keeps a batch the primary half-accepted from being re-pushed wholesale onto the fallback. A refusal dispatchesqueue::events::QueueFailedOver { connection, job_name, exception }, edge-triggered: a connection reports itself once when it enters failure and stays quiet until a later push succeeds on it and re-arms it, so an outage produces one alert instead of one per dispatch. When every connection refuses, the push returns the last connection's error. An empty connection list, a missing or blankQUEUE_FAILOVER_CONNECTIONS, a nestedfailoverentry, and an entry naming a driver that doesn't exist are all boot errors - the warn-and-fall-back-to-memory behaviour stays onQUEUE_DRIVERitself, where a typo can't splice an ephemeral backend into a durable chain. -
Queue inspection API.
Queue::pending_jobs(queue)/delayed_jobs/reserved_jobslist the actual envelopes behind the existingpending_size/delayed_size/reserved_sizecounters, asInspectedJobDTOs (id,queue,name,attempts,payload,created_at) - mirrors Laravel'sInspectedJob. A singleOption<&str>queue filter collapses Laravel'spendingJobs($queue)/allPendingJobs()pair (and thedelayedJobs/reservedJobsequivalents) into one call each. TheQueueDrivertrait default is an honestErr- not Laravel's Beanstalkd/SQS empty-collection default, which reads as "nothing queued" even when there plainly is - so a driver that has not implemented inspection says so;sync/nulloverride withOk(vec![])because for them that really is the truth. The memory, database, and Redis drivers all implement the full listing: the memory driver's delayed storage moved from a bareDelayQueue<Envelope>(which cannot be iterated) to aDelayQueue<Uuid>plus an id-keyed map; the database driver reuses the size counters' exact predicates plusORDER BY available_at, and a row whoseenvelope_jsonfails to decode is still listed (id: None,payload: {"unparseable": true}) rather than dropped, so one poison row can't blind an operator to the rest of the queue; Redis'sreserved_jobsis scoped to this consumer's in-process reservations (documented), andpending_jobsscans the stream viaXRANGEin batches.Queue::fake()gained matchingpending_jobs()/delayed_jobs()helpers, projecting recorded pushes withattemptsalways0andcreated_atalwaysNone. -
After-commit dispatch.
Job::after_commit()holds a push until the surroundingDB::transactioncommits, so a worker on another process can never pop an envelope that describes rows the transaction has not made durable yet. The whole push waits, not just the driver write: the envelope build,JobQueueingandJobQueuedall happen at commit time, so no listener is ever told about a job a rollback then discards. A rollback discards the push entirely; outside a transaction the push happens immediately, which is what lets a job type declare the opt-in without every dispatch site knowing whether its code path is transactional. Per dispatch,EnvelopeOverrides::after_commitoutranks the job:Some(true)(with the shorthandQueue::push_after_commit(job)) defers a job that did not opt in, andSome(false)is Laravel'sbeforeCommit(). A deferredQueue::pushre-resolvesJob::delay()against the commit rather than the push, whileQueue::push_later/later/later_withcarry the caller's absolute timestamp through unchanged.Queue::push_uniquetakes its dedupe lock immediately even when the envelope is deferred, so a duplicate inside the same transaction is still suppressed, and a rollback releases that lock owner-scoped.Queue::bulkdefers as a unit.Queue::fake()records a push immediately, deferral and all, matching Laravel'sBus::fake. ManualDB::begin_transactionnever defers - it installs no ambient transaction, so there is no commit to hang a callback on. Every ending that leaves the commit unlanded compensates identically, including aCOMMITthe database refuses and a leakedTxHandlethat blocks one, andTransaction::rollback_tocounts as one for the scope it unwinds: a push deferred inside a savepoint is discarded when that savepoint rolls back and its lock is released right then, while anything registered before the savepoint is untouched. Queued mail, notifications, batches and chains do not defer yet. -
Unique-until-processing jobs.
Job::unique_until_processing()releases the uniqueness lock when processing begins - after the job's middleware pass, immediately before the handler runs - instead of holding it for the fullunique_forwindow, which is what you want when the lock exists to coalesce queued duplicates rather than to serialize execution. A job that a middleware releases back onto the queue keeps its lock, because it has not started processing; a job a middleware deletes or dead-letters gives its lock up. Release is owner-scoped:Queue::push_uniquerecords the cache lock's owner token on the envelope (Envelope::unique_lock_owner, an additive field that leaves the frozen wire format byte-identical for every non-unique push), and the worker releases with that token, so a redelivered attempt can never force-release a lock a newer dispatch now holds. The supporting idempotency surface is public too:Idempotency::commit_on_success_ownedhands the body the lock owner and returns it, andIdempotency::release_owned(key, owner)releases owner-scoped, reportingOk(false)rather than an error when the lock is absent or held by somebody else. Plainunique_idjobs are unchanged and still let theunique_forTTL be the dedupe window. -
Gate::default_denial_responsecustomizes the default shape of a bare denial. Mirrors Laravel'sGate::defaultDenialResponse($response). Set once - typically inbootstrap::register()- it reshapes exactly two outcomes: a barefalse(a bool gate -Gate::define/Gate::define_async, including a#[policy]method returningbool- or abefore/afterhook that decidedfalse) and an evaluation nothing else decided at all (an undefined ability with no hook opinion either). All of those used to collapse to a bareResponse::deny()(a 403); now they surface as whateverResponsethe default carries, e.g.Response::deny_as_not_found()for a 404 that hides a resource's existence application-wide instead of gate by gate. The default applies to barefalseonly - a gate registered withdefine_with/define_async_withalready returned theResponseit wanted, and that always passes throughGate::inspectuntouched, matching Laravel's own rule that the default never substitutes for a returnedResponseobject. A default shaped asResponse::allow()is rejected (logged, ignored) rather than silently inverting every bool gate to allowed - seeGate::default_denial_response's doc comment for the one place this deliberately diverges from Laravel, which has no such guard. -
The
Passwordvalidation rule family ships, including the Have I Been Pwneduncompromised()check.Password::min(n)plus the strength builders (.max(),.letters(),.mixed_case(),.numbers(),.symbols()) port Laravel'sPasswordrule regexes verbatim - a plain space satisfies.symbols(), matching Laravel's\p{Z}separator class..uncompromised()(or.uncompromised_with_threshold(n)) checks the password against Have I Been Pwned's k-anonymity range API: only the first 5 characters of the password's SHA-1 hash ever leave the process, and a network failure, timeout, or non-2xx response fails open rather than blocking signups, exactly like Laravel'sNotPwnedVerifier. Because that check is an HTTP round trip,Passwordis the one built-in rule implementing bothRule(strength only, for syncvalidate!rows) andAsyncRule(strength, then the HIBP check, forafter_validation_async) - calling the sync path on aPasswordconfigured withuncompromised()is a loud, developer-facing error rather than a silent skip.Password::defaults_with(...)sets the process-wide defaultPassword::defaults()returns. NewHIBP_TIMEOUT_SECSenv var (default 30s).Http::fake_response_text(...)is the new raw-body sibling offake_response(...)for tests againsttext/plainupstream APIs like HIBP's. -
A scheduled task can now name the timezone its cron expression is read in, and
schedule:listcan render the whole schedule in any zone..timezone(chrono_tz::Tz)pins one task,.try_timezone("Area/City")is the fallible sibling for a zone name that only exists at runtime, andSchedule::timezone(tz)sets a default for every task registered after it. Nothing changes for a task that pins no zone: it is still evaluated against the process's local zone. A pinned zone affects due-ness only - the scheduler still ticks once per process minute and the same-minute dedup gate is untouched. Note that a zone observing daylight saving makes some wall-clock minutes happen twice and others not at all, so a task pinned to such a minute can run twice or be skipped; the scheduling chapter carries the full warning.schedule:listgained a--timezoneoption and two columns: the zone a printed expression is written in, and the next minute the task fires. A pinned task's expression is rewritten into the listing's zone, splitting into several lines when it straddles midnight there, and is left exactly as written when a faithful rewrite is impossible - across a daylight-saving transition, when a day rollover would have to move a restricted day-of-month and day-of-week together, or when it would have to decide how long February is.chrono_tz::Tzis re-exported from the crate root, so consuming apps do not addchrono-tzto their ownCargo.toml. -
A Laravel-shaped image subsystem, in
suprnova::mediabehind the default-onmediafeature.Image::from_bytes/from_path/from_disk/from_upload/from_streambuilds a lazy pipeline -resize,scale,crop,cover,contain,rotateat any angle,flip_vertically/flip_horizontally,blur,sharpen,grayscale,to_format,quality- finished withto_bytes,to_response,save,store,dimensions,mime_type, ordominant_color. Reads and writes PNG, JPEG, WebP, GIF, and BMP; AVIF output is deferred until the in-house AV1 encoder publishes, at which point it is one newOutputFormatvariant and no other change. Like Laravel'sgd/imagicksplit there are two drivers:IMAGE_DRIVER=oxideav(the default) runs on the pure-Rust OxideAV codec family with no native library and nothing to install, andIMAGE_DRIVER=magickshells out to a host-installed ImageMagick 7 for wider input support including HEIC. Decode limits (IMAGE_MAX_DIMENSION,IMAGE_MAX_ALLOC_BYTES) are checked against the input's own header before anything is allocated - including the inner bitstream of an extended WebP, whose advisory canvas size cannot be used to smuggle a larger frame past the gate - and all pixel work runs on a blocking thread. Themagickdriver pins the input coder by name rather than letting ImageMagick pick one from the bytes, and bounds every invocation withIMAGE_MAGICK_TIMEOUT_SECS.ImageDriveris the trait boundary for anything else. The module is namedmediabecause the OxideAV-backed audio and video surfaces will live beside it. Images -
The WebP gate carries one fixed, non-configurable bound. A WebP declares its real decoded size in its innermost bitstream chunk, so the framework walks the container to find it; that walk visits at most 4096 chunks per level and follows two levels of nesting, and a file past either is refused rather than measured. Reporting a number from an unfinished walk would be a gate that enough filler chunks could step around. No
IMAGE_MAX_*variable affects it and the error says as much. A 300-frame animation is unaffected; a 4100-frame one is refused. Images -
OAuth can now be installed without replacing an application's existing password and session authority.
MagnetarOAuthOnlyConfigandinit_magnetar_oauth_onlyinstall the default ceremony and provider engine while leaving the password and passkey slots empty. Applications with an existinguserstable can callverify_oauth_identity, map the verified provider subject themselves, and establish their normal framework session.
Changed
DB::transactioncan now returnErrafter a successful commit, when an after-commit callback fails: the message readsafter-commit callback failed (the transaction itself committed): …, the closure's return value is lost and its writes are not.DB::transaction_with_attemptsnever retries that error, however deadlock-shaped the callback's own message reads - re-running a closure whose writes are already durable would apply them twice.- New validation catalog key:
validation-password-unverifiable. A customUncompromisedVerifierthat returnsErrno longer puts its own error text in the 422 body verbatim. That text is logged aterrorinstead, and the response carries this key, rendering as "The { $field } could not be checked against known data leaks. Please try again." - the check did not run, which is not the same as the password being bad, and infrastructure detail does not belong in a client response. An app shipping its own validation catalog has to add the key, or its users see the built-in English fallback. - The
Imageupload validator is nowImageFile.suprnova::Imageis the new image-manipulation pipeline type, matchingIlluminate\Image\Image, and the magic-byte upload rule takes the name Laravel gives the same rule class,Illuminate\Validation\Rules\ImageFile. Migration is one line per use site:UploadedFile<(Image, MaxSize<N>)>becomesUploadedFile<(ImageFile, MaxSize<N>)>. Pre-1.0 churn absorbed by the git-tag distribution model.
Removed
- The unused direct
imagedependency is gone. It had been a base dependency with zero use sites anywhere in the workspace, pulling JPEG, PNG, WebP, and GIF codecs in for nothing; dropping it removesgif,image-webp,zune-jpeg,color_quant, andweezlfrom the tree. The crate itself still appears transitively, with only itspngfeature, behindtotp-rs's QR-code rendering. The new image subsystem is built on the OxideAV crates behind themediafeature instead.
Fixed
- Installing OAuth no longer forces provider-backed applications into
Magnetar web-binding validation. The full
init_magnetarpath remains atomic and unchanged. The OAuth-only path reserves the engine slots during construction, publishes only OAuth, and fails rather than mixing two authentication authorities.
Upgrading
-
Imageis a different type now; the upload validator isImageFile. Source-breaking for anyone using the magic-byte upload rule. Rename it at every use site:UploadedFile<(Image, MaxSize<N>)>becomesUploadedFile<(ImageFile, MaxSize<N>)>.suprnova::Imagestill resolves, but it is now the image-manipulation pipeline type, so a missed rename fails to compile rather than changing behaviour silently. -
EnvelopeOverridesgained a publicafter_commit: Option<bool>field. Every construction in this repo and in the scaffolded templates uses..Default::default(), which needs no change. Code that builds anEnvelopeOverrideswith an exhaustive struct literal has to name the new field;after_commit: Nonekeeps today's behaviour, which is to defer toJob::after_commit(). Nothing else changes:after_commit()defaults tofalse, so no existing job starts waiting for a commit it did not before. -
Envelopegained a publicunique_lock_owner: Option<String>field. The wire format is unchanged - the field is#[serde(default)]and skipped whenNone, so envelopes round-trip byte-identically in both directions andschema_versionstays at 2 - but any code that builds anEnvelopewith a struct literal now has to name it. Addunique_lock_owner: Noneunless you are deliberately carrying a uniqueness lock across the push. Code that only reads envelopes, or builds them throughQueue::pushand its siblings, needs no change. -
Use
init_magnetar_oauth_onlyinstead ofinit_magnetarwhen the application already owns users, passwords, framework sessions, and remember-me state. OAuth-only callbacks useverify_oauth_identity; full Magnetar applications continue to usecomplete.
1.3.2 - 2026-08-25
Added
-
OAuth providers can now be registered through
MagnetarConfig::oauth. Suprnova re-exports theOAuthProvidercontract, all five first-party provider and configuration types, and the HTTP, revocation, abuse-limiter, authorization, and auto-link types an application needs. Custom providers no longer require a directsuprnova-magnetardependency or a hand-retainedMagnetarHostEngine. -
A production OAuth transport and framework limiter adapter now ship at the crate root.
ReqwestOAuthTransportimplements token, userinfo, and revocation I/O with redirects disabled by default, a 30-second timeout, a defaultUser-Agent, and a 1 MiB response cap.FrameworkAbuseLimiterreuses the configuredRateLimiterDriver; apps no longer hand-write either adapter.
Fixed
-
init_magnetarnow publishes OAuth with password and passkey services as one reserved installation. The OAuth service is built before publication, and all three engine slots remain hidden while the reservation is active. A failed or duplicate OAuth configuration cannot leave password and passkey state visible without the configured OAuth registry. -
Custom providers can supply userinfo headers.
OAuthProvider::userinfo_headersis merged with the host-owned bearer header, enabling requirements such as GitHub'sUser-Agentand media-typeAcceptheaders without allowing a provider to replaceAuthorization.
Upgrading
-
The Magnetar cutover in
4faaa933removed Torii's OAuth installation path without wiring its replacement into the default initializer. The old workaround required constructing a custom host engine, callingoauth_service, and installing the adapter separately. Replace that workaround withMagnetarConfig::from_sea_orm(database).oauth(oauth_config)and oneinit_magnetarcall. -
GitHub community providers must handle verified email explicitly. GitHub
/userusually omits non-public email, while the verified primary address requires/user/emails. Returnemail: Noneto use the email-completion ceremony, or pointuserinfo_endpointat a host adapter that combines both responses; never treat a public but unverified address as ownership.
1.3.1 - 2026-08-24
Fixed
- Provider-backed applications can reset verified users again. When no Magnetar engine is installed,
PasswordResetuses an explicitly reset-capableUserProviderand frameworkauth_flow_tokensfor already verified accounts.EloquentUserProvider<M>opts in whenMimplementsMustVerifyEmail + CanResetPassword; noapp_usersmigration is required. - The published framework line now contains both post-release repair sets. The translated 1.3.0 changelog layout and headings, CJK wrapping, localized anchors, glossary terms, and prose punctuation are reconciled instead of split across divergent local and remote branches.
- Post-tag CLI and Magnetar hardening is included. Development-process cleanup uses the completed process-group fallback, and the local qualification contracts cover the released refs and plugin-SDK SQLite lanes.
Security
- The provider fallback never treats password reset as first mailbox proof. Unknown and unverified addresses receive the same no-mail response. Install Magnetar when an unverified account must prove mailbox ownership through reset so credential cleanup, auth-epoch advancement, and revocation remain atomic. Provider fallback completion reports framework session and remember revocation failures through
PasswordResetOutcome.
Upgrading
- Move every
v1.3.0Git dependency tov1.3.1. Applications with their ownuserstable keep their configuredUserProvider; they do not initialize the defaultapp_usersengine merely to reset an already verified account. Applications that use Magnetar credentials or unverified-account first proof continue to initialize Magnetar.
1.3.0 - 2026-08-24
Security
-
Magnetar now fences credential and session mutations to the authenticated actor and account auth epoch. Password, passkey, linked-account, two-factor, opaque-session, JWT, remember, OAuth, and device-authorization writes reject stale or revoked actors. The first successful password-reset, magic-link, or OAuth verified-email proof on an unverified account advances the epoch and atomically removes provisional credentials, sessions, remember state, and squatter TOTP enrollment. Verified accounts preserve legitimate credentials during password reset. Email verification requires the authenticated token owner, and OAuth never auto-links an unverified existing account from email alone.
-
A protocol-relative
_previous.urlcan no longer produce an off-origin open redirect throughRedirect::back(), on either the write side or the read side.SessionMiddlewareno longer persists a protocol-relative current URL: the write goes through the identical sanitizerInertiaValidationRedirectMiddlewareuses for itsReferercheck, and a request path shaped like//host(or carrying an ASCII control byte) is never recorded - without this, an app'sfallback!route (the standard Inertia/SPA app-shell pattern, where any unmatched path answers200) could haveGET //evil.test/anythingpersist that path verbatim.SessionData::previous_url()now applies the same check on every read, too, so a session cookie that survived an upgrade from a release before this fix - already carrying a raw, unsanitized value no write in the current process ever produced - self-heals to "nothing recorded" instead of being trusted. Together, neither an old poisoned cookie nor a new malicious request can handRedirect::back(),Redirect::refresh(), orurl::previous()an off-originLocation. When a value fails either check it's treated as absent rather than replaced with a synthesized one, so a genuinely good previous URL is never clobbered. -
The Inertia validation-redirect bridge's
Referercheck closed two more same-origin bypasses.InertiaValidationRedirectMiddleware's303target only rejected aRefererstarting with the literal//or/\prefix - a value likeReferer: /<TAB>/evil.testslipped through, because the WHATWG URL parser strips ASCII tab and newline from the whole string before comparing origins, so a browser reads that as//evil.testand follows the303off-origin. The check now rejects any ASCII control byte (C0 or DEL) anywhere in the candidate, not only within the two named prefixes. Separately, the last-resort fallback - the failing request's own path, used when neitherReferernor the session's previous URL is usable - was never sanitized: an origin-form HTTP request-target is syntactically free to start with//, so a raw client or a non-normalizing proxy could turn the "safe last resort" into an off-origin redirect too. Both legs now share one root-relative check, falling back to/if even the request's own path fails it. -
Cookie ciphertext is now bound to its logical cookie name with contexted v2 AAD.
Cookie::encrypted/Cookie::read_encrypted_forstop a value minted for one cookie slot from decrypting in another slot, while the logical-name binding keeps a later__Host-/__Secure-wire-prefix flip safe. The version-less compatibility window tries v2 across the whole key ring, then v1 across the whole ring, so existing cookies survive the rollout; the v1 fallback preserves the old replay weakness until its scheduled 1.4.0 removal. -
Session and remember-me cookie prefixes are validated at boot and enforced at render time.
SESSION_COOKIE_PREFIX=__Host-requiresSecure,Path=/, and noDomain;__Secure-requiresSecure. Invalid boot combinations fail before serving, and the renderer rewrites invalid prefixed headers instead of letting browsers discard them silently.
Added
- Suprnova authentication now runs on the internal Magnetar engine. The
framework-owned
Authfacade preserves existing password, magic-link, passkey, OAuth, bearer, lockout, session, and two-factor call sites while removing the Torii dependency. The default engine installs password/session and passkey adapters atomically, stores lifecycle delivery leases in the application database, and shares the application's canonicali64app_usersidentities. - A shape-aware authentication migration runner now covers Torii, Suprnova web, and Suprnova API sources. Dry runs bind a stable plan id to durable row and schema fingerprints plus destination identity decisions. Apply uses transactional imports, retry ledgers, shape-owned cleanup, and collision refusal. MySQL uses a write-barrier-protected shadow swap with pre-copy journals, row and schema parity, resumable renames, and cleanup-preserving restore.
MAIL_DRIVER=filewrites one RFC 5322.emlper message toMAIL_FILE_PATH(defaultstorage_path("mail"); a relative value anchors at the application base directory, not the process CWD), so local mail can be opened in a mail client instead of read out of a log line. The file carries the same header superset SMTP emits, includingX-Priority,Importance,X-Tag,X-Metadata-*, andReturn-Path. Likelogandmemory, it does not deliver: a production boot refuses it unlessMAIL_ALLOW_NON_DELIVERING_IN_PRODUCTION=true.FrameworkError::Externalcarries the error it wraps.FrameworkError::from_external(e)andFrameworkError::from_external_with("saving user", e)keep the original error reachable as astd::error::Errorsource instead of melting it into a string.FrameworkError::external_source()returns it for downcasting - use that rather thansource(), which yields the sharedArchandle. Both constructors map to HTTP 500.- 5xx logs now render the full error source chain.
render_error_chainwalkssource()and is wired into the framework-error log line, theErrorOccurredevent payload, and thedebug_messagefield emitted underAPP_DEBUG=true. Client-facing response bodies are unchanged and 5xx bodies stay sanitised. InertiaResponse::scroll_wrapped/scroll_with_wrapped/try_scroll_wrapped. Nest a scroll prop's merge instruction under<key>.<wrap_key>instead of the bare key -mergeProps: ["users.data"]rather than["users"]- for a value that's itself an envelope ({ data: [...], meta: {...} }). Laravel'sScrollPropwraps under"data"unconditionally; Suprnova's built-in paginators hand back a bare row array, so this is opt-in rather than a default every caller has to work around. NewProvidesScrollMetadatatrait (page_name/previous_page/next_page/current_page, with a defaultscroll_metadata()) mirrors Laravel's interface of the same name for a paginator this crate doesn't know about;LengthAwarePaginator,Paginator, andCursorPaginatornow implement it instead of buildingScrollMetadataby hand. A scroll prop's.match_on(...)fields now also emit intomatchPropsOn, matching Laravel'sresolveMergeMatchingKeys(Response.php:641-652), which folds aScrollProp'smatchesOn()in the same as any other merge prop - the match entry keys off wherever the prop actually merges,<key>unwrapped or<key>.<wrap_key>under.scroll_wrap(...).Prop::merge_with_path, multi-fieldmatch_on, and resolver-backed merge props.Prop::merge_with_path(path)merges a nested field inside a prop's value instead of the whole prop -Prop::eager(v).merge().merge_with_path("data")emitsmergeProps: ["<key>.data"], and a path-merging prop never also merges its root;.deep_merge()ignores it, since a deep merge already recurses into every field.Prop::match_onnow takes one field or several in one call (match_on(["id", "slug"])) on top of thematch_on("id").match_on("slug")chainingPropcomposition already supports.InertiaResponse::merge_lazy/merge_lazy_withadd the resolver-backed siblings of.merge/.merge_with, matching Laravel'sInertia::merge(fn () => ...).- Partial-reload
only/exceptunderstand dot notation.X-Inertia-Partial-Data: user.namenarrows theuserprop to{ name: ... }instead of requiring the whole value or nothing;X-Inertia-Partial-Except: user.emailprunes just that field, leaving the rest ofuserin place.exceptwins on a path both headers name, a bare entry still means the whole prop, and an unknown or type-mismatched nested path drops silently without touching its siblings.Alwaysprops are unaffected - they always ship whole. - Dot-key prop nesting.
.with("user.name", value)(and any other prop-attaching method, eager or resolved) now nests intoprops.userinstead of shipping a literal"user.name"key, matching Laravel'sArr::set-basedresolveArrayablePropertiesunpacking. Two calls sharing a prefix -.with("user.name", …)then.with("user.age", …)- accumulate into one object; a key with no dot is unaffected.App::inertia_share*shared-registry keys nest the same way on the wire. The unpacking only ever touches top-level prop keys - it never recurses into a prop's value, so a validationerrorsbag keeps whatever dotted field names it carries internally. App::inertia_shared(key)/App::flush_inertia_shared(). Laravel'sInertia::getShared/Inertia::flushShared, reading and clearing the static share registry (App::inertia_share/_lazy/_once).inertia_sharedsupports the same dot notation asinertia_sharefor the read side; it returnsNonefor a lazy or once share (there's no request to resolve one against) and for an unregistered key.flush_inertia_sharedclears only the static registry - a trait provider registered viaApp::register_inertia_sharedis untouched, matching Laravel (there's no per-request state there to flush).InertiaResponse::always_with(key, resolver). The async-resolver sibling of.always(key, value), for an always-included prop expensive enough to be worth resolving lazily - Laravel'sInertia::always(fn () => …)(AlwaysPropaccepts any value, closures included).InertiaSharedData::sharenow receives the page component name, so a provider can vary its output by page - Laravel'sRenderContext. See Upgrading.- Inertia prop composition. A
Propnow carries orthogonal flags instead of being one of nine closed variants, so a single prop can be deferred and mergeable, mergeable and cached, or optional and cached - the combinations the Inertia 3 protocol expects and a closed enum could not spell. Build one withProp::eager/Prop::lazy/Prop::from_resolver/Prop::absent, chain.always(),.optional(),.defer(),.group(),.rescue(),.merge(),.prepend(),.deep_merge(),.match_on(),.once(),.as_key(),.until(),.fresh(),.scroll(), and attach it with the newInertiaResponse::prop(key, prop). Adefer().merge()prop is announced underdeferredPropson the first render and arrives undermergePropson the follow-up request. NewMergeModeandVisibilitytypes describe the flags; every existing builder shortcut (.with,.always,.lazy,.optional,.defer,.merge*,.once*) is unchanged. - Queue pause / resume.
Queue::pause(connection, queue)/resume/pause_all()/resume_all()/is_paused(connection, queue)/paused_queues(connection, &queues), backed byCachethe same way the restart signal is -resume_alldoes not clear a per-queue pause, matching Laravel. The worker's claim gate sits right before every pop, so an in-flight job always finishes; a global pause short-circuits--queue=...filtering the same way Laravel'spausedQueuesdoes, and a per-queue pause only takes effect on a worker started with an explicit--queue=...list. New CLI commandsqueue:pause [queue] [--all]/queue:resume [queue] [--all](aliasqueue:continue), plusQUEUE_PAUSABLE=falsefor an operator to disable the feature - an unpausable worker ignores pause signals, andqueue:pauseitself refuses to run. New events:QueuePaused/QueueResumed/QueuesPaused/QueuesResumed. suprnova::testing::TestResponse- a fluent, Laravel-TestResponse-shaped wrapper over the(status, headers, body)triple every HTTP test harness already produces:assert_status,assert_ok,assert_redirect,assert_json,assert_json_path,assert_json_count,assert_see,assert_header,assert_cookie, and (given.with_session_store(...))assert_session_has. Every assertion returns&Selfand panics on failure, the same contract asexpect!. Nothing about how a test drives a request has to change.suprnova newscaffolds an SSR entry. Every starter (Svelte, React, Vue) now shipsfrontend/src/ssr.{ts,tsx}and abuild:ssrnpm script (vite build --ssr), wired to its own output directory (frontend/bootstrap/ssr/) so the SSR bundle never collides with the client build inpublic/assets/.InertiaConfig::ssr_bundle_path(path)/.ssr_ensure_bundle_exists(bool). The SSR gateway can now check the built bundle exists on disk before dispatching a render, mirroring Laravel'sensure_bundle_existsconfig - a worker that was never started, or a bundle that was never built, fails fast instead of payingssr_timeouton a connection that was never going to succeed. Opt in with.ssr_bundle_path(...); unlike Laravel'sBundleDetectorthe path is never auto-detected, so existing SSR configs (and tests) that don't set one are unaffected.- Validation failures on an Inertia visit now redirect back instead of returning
422JSON.Inertia::installregisters a fourth middleware,InertiaValidationRedirectMiddleware, which turns a validation422on anX-Inertiarequest into a303to the form page with the errors flashed - souseForm().errorsfills in with no handler code. The Inertia client treats any response without anX-Inertiaheader as non-Inertia and shows its error modal, so the old422could never reachform.errors. Non-Inertia requests keep the422envelope, Precognition dry-runs are untouched, andX-Inertia-Error-Bagscopes the flashed bag. The redirect target is the same-originReferer, then the session's previous URL, then the request's own path run through that same sanitizer, falling back to/if even that fails it - never trusted verbatim. InertiaConfig::with_all_errors(bool)- keep every validation message per field instead of collapsing to the first. Mirrors Laravel'sInertia\Middleware::$withAllErrors.suprnova::testing::AssertableInertia- fluent, Laravel-AssertableInertia-shaped assertions over an Inertia page object, parsed from either anX-InertiaJSON response or a hard-navigation HTML shell's embedded<script data-page="app">element:component,url,version,prop,has,missing,where_,count,has_flash. Build one from anHttpResponsewithAssertableInertia::from_response, or from aTestResponsewith the newTestResponse::assert_inertia().reload_only,reload_except, andload_deferred_propsreplay a partial reload against a caller-suppliedwith_reload(...)closure - Suprnova's HTTP tests cross a real socket, so there's no single in-process test client to hardcode against.Cookie::queue/queued/unqueue/expire. A task-local cookie jar - Laravel'sCookieJar- lets any code queue a cookie for the next outgoing response without holding anHttpResponseto attach it to: an event listener, a container-bound service, middleware ahead of the handler. Backed by the same per-request slotAuth::login_rememberalready uses to carry the remember-me cookie past the handler boundary;SessionMiddlewaredrains it onto the response next to the session cookie.Cookie::expire(name, path, domain)queues a deletion cookie built withCookie::forget_with. RequiresSessionMiddlewarein the route's middleware chain - outside it, all four calls are a silent no-op, matchingApp::flash's behavior outside a flash scope.HttpResponse::event_stream(stream, end)andHttpResponse::stream_json(stream). Laravel'sResponseFactory::eventStream/streamJson, and the exact wire shapes@laravel/stream-{react,vue,svelte}'suseEventStream/useJsonStreamexpect.event_streamframes aStream<Item = sse::StreamedEvent>asevent: updateper item unless the item names its own event, JSON-encodes any non-string payload, and appends a configurable terminal frame (EndSignal::default()isdata: </stream>;EndSignal::Noneomits it).stream_jsonstreams anyStream<Item = impl Serialize>as one incrementally-flushed JSON array. Both are built on the existingsse/stream_bytesbody pipeline, so they share its cancellation and panic-isolation behavior with the rest of the framework.suprnova serverespawns a crashed dev process instead of tearing the whole session down. Exponential backoff between attempts - 200ms, doubling on each consecutive crash, capped at 5s, resetting to the floor once a process has stayed up 30s.--no-restartopts out and restores the previous behaviour.--restart-tries <N>(default5, matching Laravel's--restart-tries=5) gives up retrying a process after that many consecutive crashes instead of retrying forever, printing an actionable message and leaving the other processes - and the session itself - running.--timestampsprefixes every forwarded line withHH:MM:SS. A newSuprnova.toml[[serve.process]]array lets a project declare its own dev processes - Laravel'sDevCommands::register- to run alongside the backend and frontend, each with its own[name]prefix and an optional color; an unknown key or a blankname/commandin an entry is now a hard parse error instead of silently ignored or a later opaque spawn failure.--jsonemits one JSON object per line (NDJSON) on stdout instead - process start, output, exit, restart-scheduled, restart-succeeded, gave-up, types-regenerated, and shutdown events, including the file watcher's own regeneration notices and theCtrl+Chandler's shutdown notice, both of which now stay off stdout under--jsontoo - for scripting and log pipelines; combining it with--timestampsis harmless but redundant, since every event already carries its own timestamp.RequestBuilder::retry_when(predicate). A predicate consulted before every retry the built-in policy (.retry(...)/.retry_non_idempotent(...)) would otherwise make, receiving aRetryContext { attempt, method, url, outcome: RetryOutcome::TransportError | Status(u16) }. It composes with the policy rather than replacing it:falsevetoes a retry the policy would have made; it can never force one pastmax_attemptsor one the policy wouldn't otherwise attempt (a 4xx status, or a non-idempotent method withoutretry_non_idempotent).#[model(touches = [...])]now actually touches. After a child is created, saved, updated, or deleted, eachBelongsToowner named in the list gets oneUPDATE <owner> SET updated_at = ? WHERE <key> = ?, on the same executor as the write that triggered it - so inside aDB::transactionthe touch joins that transaction and rolls back with it. An owner whose model hastimestamps = falseis skipped, not written and not an error (Laravel 13.25 closed the same gap). Owners reached through aNULLforeign key, and soft-deleted owners, are skipped too. Atouchesentry that doesn't name a declaredBelongsTorelation is now a compile error; polymorphic owners are not supported yet.without_touching_on::<M, _, _>(fut)- Laravel'sModel::withoutTouchingOn([M::class], $cb). Suppresses bothm.touch()and any owner cascade targetingM, while owners of other types keep bumping. Scopes nest, and the existingwithout_touchingnow suppresses the owner cascade as well as directtouch()calls.Model::touch_owners()/touch_owners_with_tx(tx)- Laravel'stouchOwners(), for when you wrote the child row through a path the framework doesn't own.- Value-shaped validation rules:
ArrayKeysandDistinct. A newValueRuletrait (passes(&self, value: &serde_json::Value)) sits alongsideRule, sharing the same keyed-message contract.rules::ArrayKeys(&[...])rejects a JSON object carrying any key outside the allowed list (Laravel'sarray:keys, #60918);rules::Distinct { ignore_case, strict }rejects a JSON array with a repeated element (Laravel'sdistinct).validate!rows accept either kind of rule in the same field list - dispatch is automatic, chosen by which trait the rule implements, not by new row syntax. Job::delay()- jobs can declare a default delay (fn delay() -> Option<Duration>, defaultNone), honored byQueue::pushandQueue::bulk:available_atbecomesnow + delayinstead ofnow. An explicit call-site delay still wins -Queue::push_later(job, at)andQueue::later(delay, job)use the caller's timestamp verbatim and never consultJob::delay().Notification::{queue, timeout, fail_on_timeout, max_tries, backoff}. A queued notification (Notify::queue) now carries its own queue-tuning defaults onto every per-channelSendNotificationJobpush via theEnvelopeOverridesprimitiveMail::on_queueuses -fail_on_timeout(&self) == truedead-letters on the first timeout instead of retrying, matching Laravel's#[FailOnTimeout]notification attribute (#61072). All five default toSendNotificationJob's existingJobdefaults, so a notification that overrides nothing is unaffected.Mail::on_queue/Mail::on_connection+Queue::push_with/later_with. A queued mailable now routes itself withMail::to(..).on_queue("emails").queue(mailable), or defaults viaMailable::queue(&self). Both outrank anyQueue::routeregistered for the job and the job's ownJob::queue()/Job::connection()- the newEnvelopeOverridesprimitive behind them (Queue::push_with(job, overrides)/Queue::later_with(delay, job, overrides)) also covers timeout, fail-on-timeout, max-tries, and backoff for one push.MailFake's queued snapshots now carry the resolvedqueue, withqueued_on(...)/assert_queued_on(name, queue)to assert it.Application::http_bootstrap(f)- an HTTP-only boot hook. It runs afterbootstrapand only on theserve/web:runpath, so the queue, schedule, and workflow workers and the console binary never run it. Worker and console container images no longer need a built frontend manifest to boot:Inertia::installfails closed in production when it is missing, and that check now only runs on a process that actually serves HTTP.Router::inertia(path, component, props)- Laravel'sRoute::inertia, for a static page whose handler would be one line. RegistersGET(HEAD falls through to it) and returns aRouteBuilder, so the route can be named and given middleware.Router::viewis retained as an alias.- SES v2 send options. The SES transport now emits
TenantName,ConfigurationSetName, andListManagementOptionsonSendEmail. Each has a transport-level default (SesMailTransport::tenant_name/configuration_set_name/list_management) and a per-message header override (X-SES-TENANT-NAME,X-SES-CONFIGURATION-SET,X-SES-LIST-MANAGEMENT-OPTIONS), with the header winning. The headers are consumed when the request is built and never rendered into the message. without_cookieson every response builder.HttpResponse,Response(viaResponseExt),Redirect, andRedirectRouteBuilderall expire a list of cookies in one call, andRedirect/RedirectRouteBuildergained the single-namewithout_cookiethey were missing. NewCookie::forget_with(name, path, domain)builds a deletion cookie scoped to the path and domain the original was set with - a plainforgetnever clears a cookie set outside/.Queue::fake()stamps an envelope id on every captured push.pushed_with_id::<J>()returns(job, id)pairs, and the fake now dispatches the sameJobQueueing/JobQueuedpair a real driver push does - carrying that id - so a test can correlate a captured push with what its listeners saw. Existing fake helpers are unchanged.UniqueJobSkippedqueue event.Queue::push_uniquenow dispatchesqueue::events::UniqueJobSkipped { job_name, unique_id, connection }when it suppresses a duplicate, so a dedupe is observable instead of silent. The call's return value is unchanged (Ok(false)).model_keys()on the query builder and on collections.User::query().model_keys().await?returns every matching row's primary key without hydrating a single model, projecting the table-qualified key (users.id) so the query survives a join.Collection::model_keys()is the already-hydrated counterpart.#[suprnova::model]now also declares the key's Rust type asEloquentModel::Key, so both return the typekey_typenames rather than a caller-chosen turbofish.
Fixed
-
PostgreSQL soft deletes now use backend-aware placeholders, and generated timestamp writes honor declared casts.
delete()andrestore()render PostgreSQL ordinal placeholders instead of MySQL and SQLite?placeholders. Generated create, update, save, touch, and soft-delete writes also convert timestamps through each field's declaredCaststorage type, so nativeTIMESTAMPTZcolumns no longer receive text values. Thanks to @i-am-v-alexander-v for reporting both defects and submitting a fix in PR #3. -
Default workspace and Magnetar gate runs no longer require live PostgreSQL or MySQL services. Backend-specific behavior suites are explicit, ignored qualification tests that still fail when deliberately invoked without their configured database. Reachability-only tests and permanent gate environment requirements were removed, so unrelated changes don't pay for external database setup on every verification run.
-
PartialFilter::narrowis nowpub. Its four sibling predicates (should_include,should_include_eager,should_include_optional, and the type itself) were already public, but the narrowing pass that makesshould_include_eager'strueanswer correct - trimming a resolved value down to the dotted paths anonly/exceptentry actually asked for - waspub(crate). A caller building custom partial-reload handling on top ofPartialFilterhad no public way to reproduce that narrowing and would ship a value whole under a dottedonlyentry even thoughshould_include_eagerreported the key as included. -
MailFake'sQueuedSnapshotcan now assert on.on_connection(...).Queue::fake()gainedassert_pushed_on_connectionin Wave 3 alongsideassert_pushed_on_queue;Mail::fake()only got the queue half, so a mailable queued with a connection override was resolved and applied to the real dispatch but unassertable through the fake. NewQueuedSnapshot::connection,MailFake::queued_on_connection, andMailFake::assert_queued_on_connectionclose the gap, mirroringassert_queued_on's shape. -
A dotted shared prop was unreachable by a bare
onlyentry.App::inertia_share("auth.user", …)followed byrouter.reload({ only: ['auth'] })returnedprops: {"errors":{}}- the share vanished outright. The registry storesauth.useras one literal key and theArr::setunpacking pass only nests it after every prop has resolved, so the partial-reload gate saw the still-flat key and matched it against neitherauthnor anything else.only/exceptentries are now symmetric: an entry may name a prop's key exactly, a path inside it (user.name, which narrows), or an ancestor of it (authagainst the keyauth.user, which ships the prop whole, because the caller asked for the whole root). A bareexcept: ['auth']drops every prop key beneath it the same wayArr::forgetdrops the whole subtree in Laravel's already-nested bag. The prefix must end on a segment boundary, so an unrelatedauthAgent.userprop is untouched by either list. Laravel never hits this becauseInertia::sharerunsArr::setat share time; Suprnova's registry cannot, since a lazy share has no value to nest until the request resolves it. -
A
#[data(lazy(deferred))]field bypassed the?include=allowlist. The owner-tagged resolution path inresolve_propsselected props withProp::is_lazy(), which is false for anything carrying a flag - and a deferred field isVisibility::Deferred. The field therefore resolved off the ordinary prop path, where no include-set check exists, and shipped to any client that sent the deferred follow-up regardless of whether the request opted the field in.Prop::resolve_with_ownernow gates every resolver-backed owner-tagged prop, flags or not, andresolve_propsruns that gate ahead of every other block: a field outside?include=is dropped whole (no value, nodeferredPropsannouncement), and a field named by?include=but off the DTO's allowlist raises its400beforeX-Inertia-Partial-Datacan absorb it. Not a regression - the pre-Wave-4 code gated on theProp::Lazyenum variant, which aProp::Deferalso failed - but a real hole either way. -
deferredPropswas re-announced on a matched partial reload. A partial that named one deferred key still advertised every other deferred key back to the client, which then fetched them again, and again on the next partial. Laravel'sresolveDeferredPropsreturns[]the moment the request is partial, before it inspects a single prop (Response.php:661-663); the block is now dropped whole on any matched partial. A partial reload aimed at a different component is a standard visit for this gate, as for every other, so its announcements are unaffected. -
The
errorsbag filtered differently depending on where the errors came from. The session-flashed bag is seeded ahead of the resolve loop and no partial-reload filter could reach it, while a handler's own.with("errors", …)went through the ordinary gates - soonly: ['errors.email']shipped the whole seeded bag but a one-field handler bag, andonly: ['users']replaced the handler's bag with the seeded one instead of leaving the key alone. Both paths now treaterrorsas always-visible, matching Laravel's middleware, which shares it asInertia::always(...)and re-injects the raw value throughresolveAlwaysafter theonly/exceptrebuild. This is the shape the client needs: it folds a partial response in with{...current.props, ...response.props}, so an emptyerrorsobject wipes messages already on screen where an unfiltered one leaves them correct. An explicit visibility flag on the key still wins, so.prop("errors", Prop::eager(…).optional())behaves optionally. -
Queue::fake()can now observe per-pushEnvelopeOverrides. A job pushed throughQueue::push_with/Queue::later_withwas indistinguishable from a plainQueue::pushunder the fake -FakePushcarried only the payload andavailable_at, so the override never left the facade and nothing could assert a test dispatched to the right queue or connection. Newqueue::testing::pushed_with_overrides::<J>() -> Vec<(J, EnvelopeOverrides)>returns each captured push paired with what it declared;assert_pushed_on_queue::<J>(queue)andassert_pushed_on_connection::<J>(connection)cover the common single-field case, mirroringMailFake::assert_queued_on. Every other entry point (push,push_later,bulk,push_unique, the chain/batch dispatchers) still takes no overrides and recordsEnvelopeOverrides::default(), so a plain push reads under the fake exactly as "no override declared." -
An SSR worker that stalled mid-response body could hang a render forever.
SsrConfig::timeoutbounded only the wait for response headers; once headers arrived, reading the body had no timeout of its own, so a worker that accepted the connection, sent headers, then stopped sending data left the request hanging past the configured timeout instead of falling back to CSR (or erroring, underssr_throw_on_error). Both phases now share one deadline, so the configured timeout bounds the whole SSR call, as its own doc already promised. -
Queued cookies - including the remember-me cookie
Auth::login_remembersets - were silently dropped on three internal fail-closed paths inSessionMiddleware. A session read failure, a session write failure, and a session-cookie encryption failure each returned a synthesized500directly, bypassing the pending-cookie drain that runs at the end ofhandle. Anything queued viaCookie::queuethat request - including a remember-me token row already committed to the database - never reached the client as aSet-Cookieheader. All three paths now drain pending cookies before returning, the same as a handler-returned error or a redirect. This does not cover an uncaught panic, matching Laravel's own queued cookies being lost to one. -
Queue::push_uniquenow honorsJob::delay(), matchingQueue::push,Queue::push_with, andQueue::bulk. It previously computedavailable_atfromUtc::now()directly, so a job that declared a default delay (fn delay() -> Option<Duration>) dispatched immediately when pushed throughpush_uniqueinstead of after that delay.Queue::push_unique_laterandQueue::later_uniqueare unaffected - they already take an explicit timestamp or delay from the caller and never consultJob::delay(), the same rulepush_later/laterfollow.
Changed
- The current development branch uses SeaORM 2.0 and requires Rust 1.94.0. Suprnova preserves
its Eloquent,
#[model], migration, and database-facade source shapes. Applications that call SeaORM directly must importExprTraitfor SeaQuery expression methods and use explicit*_rawconnection methods for prebuiltStatementvalues. SeaQuery is now 1.0, and the direct MariaDB vector driver uses SQLx 0.9. Existing databases require no application data migration; fresh PostgreSQL schemas retain serial-backed primary keys. - Three more unused dependencies removed.
pretty_assertionsandqrcodeleave the framework crate (totp-rsalready carries theqrfeature, so QR provisioning for two-factor enrolment is unaffected), andnotify-debouncer-minileaves the CLI (notifyitself stays - theserveandgenerate-typeswatchers use it directly). All three were confirmed unused bycargo-udepsplus a source-wide search that covers doc tests. suprnova-macrosno longer depends onserdeorserde_derive_internals. Neither was used: the::serde::Serializepaths the macros emit resolve in the downstream crate, not in the macro crate itself. No effect on generated code.MergeStrategy'smatch_onnow carries more than one field name.Append,Prepend, andDeepeach widen frommatch_on: Option<String>tomatch_on: Option<Vec<String>>, soInertiaResponse::merge_with/merge_lazy_withcan dedupe on several fields the same way.prop(key, Prop::eager(v).match_on([...]))already could - before this, the response-builder shortcuts were strictly less expressive than building aPropdirectly. See Upgrading.- Scroll props now emit Laravel-identical
resetand merge semantics.scrollProps[key].resetistrueexactly when the client namedkeyinX-Inertia-Reset, matching Laravel'sresolveScrollProps- nottrueon every visit lacking anX-Inertia-Infinite-Scroll-Merge-Intentheader, as before. A scroll prop now also carries merge metadata unconditionally, defaulting to append: a fresh visit (no headers at all) emitsreset: falseplus amergePropsentry, where it previously emittedreset: trueand no merge metadata. A key inX-Inertia-Resetis excluded frommergeProps/prependPropsfor that response, the same exclusion a regular merge prop already had. ssr:checknow verifies the SSR worker'sGET /healthroute answers 2xx, rather than only confirming that something accepted a TCP connection. Every@inertiajs/{vue3,react,svelte}/serverworker answers/healthout of the box, so this needed no change on the worker side - matches Laravel'sInertia\Ssr\HttpGateway::isHealthy().- The Inertia
errorsprop now carries one string per field, not an array. A session-flashed validation bag renders as{ email: "The email field is required." }rather than{ email: ["The email field is required."] }, matching Laravel's default and Inertia's ownErrorValue = string.InertiaConfig::with_all_errors(true)restores the array shape. Anerrorsprop a handler sets itself is passed through untouched, and the session flash (Redirect::with_errors,session.pull_errors_flash()) still stores arrays - only the rendered page prop changes. Model::TOUCHESmoved from an inherent const toEloquentModel. The parent-touch cascade lives on aModeltrait default, and a trait default can't read an inherent const.Comment::TOUCHESstill resolves - it now needsuse suprnova::EloquentModel;in scope. Models without atouchesattribute get the trait's empty default.RelationEntrygainedrelated_updated_at_column. Anything constructing aRelationEntryby hand needs the extra field; nothing in-tree does, the macro emits them all.Router::viewnow rejects props that aren't a JSON object. It previously ignored them silently, registering a route that rendered an empty prop bag with no diagnostic.nullis still accepted as "no props";Router::try_inertiais the fallible form.- The Inertia asset version now defaults to a hash of the Vite build manifest instead of the
literal
"1.0", so a deploy invalidates long-lived clients without anyone remembering to bump a string.InertiaConfig::manifest_path(...)re-points the resolver with it; an explicit.version(...)/.version_with(...)still wins. With no manifest on disk - local development - the version falls back to"1.0", which is what every app saw before, so nothing changes until you build. NewVersionResolver::from_manifest(path)exposes the resolver directly.
Deprecated
Cookie::read_encryptedis now the v1-only legacy reader. Code that mints withCookie::encryptedand reads withread_encryptedfails at runtime on the first value written after this release; switch toread_encrypted_for(name, wire). The un-contextedCryptPurpose::Cookieentry points are also superseded. Both removals are scheduled for 1.4.0.
Upgrading
-
Cookie decrypt warnings now have two independent axes. A
KeyOrigin::Previous(index)warning means re-encrypt the value under the currentAPP_KEYand remove that previous key only after the rotation tail is gone; anAadVersion::Legacywarning means re-issue the cookie through the name-bound API before the 1.4.0 fallback removal. A value can report both. -
SESSION_COOKIE_PREFIXis opt-in. Deploy__Host-only with HTTPS,SESSION_SECURE=true,SESSION_PATH=/, and noSESSION_DOMAIN; local HTTP scaffolds leave it empty.CsrfMiddleware'swith_session_configkeeps the literalXSRF-TOKENname; use.xsrf_cookie_name("__Host-XSRF-TOKEN")when a client is configured for that separate name. -
DecryptOriginis now a two-axis#[non_exhaustive]struct. Read itskeyandaadfields independently and keep a wildcard-compatible match strategy for theKeyOrigin/AadVersionenums. -
SessionConfigandCookieOptionsare now#[non_exhaustive]. Struct literals and functional record updates in application code must move toType::default()followed by public-field assignments or builder methods. -
FrameworkErroris now#[non_exhaustive]. Amatchon it in your own code needs a wildcard arm. This is the last release in which adding a variant would have been a breaking change. -
MergeStrategy::Append/Prepend/Deep'smatch_onfield is nowOption<Vec<String>>, notOption<String>. A call site constructing the struct-literal form directly -MergeStrategy::Append { match_on: Some("id".into()) }- no longer compiles; wrap the field name in aVec:Some(vec!["id".into()]).match_on: Noneis unaffected and needs no change. -
A matched partial reload no longer emits
deferredProps. Code readingpage.deferredPropsoff a partial-reload response - a custom deferred-loading component, a test snapshot, an end-to-end assertion - will now find the key absent where it used to list the deferred props the request did not name. Read the announcements off the initial (non-partial) visit, which is where Laravel puts them and where the official client reads them. -
A bare
exceptentry now drops dotted prop keys beneath it.X-Inertia-Partial-Except: authpreviously left a prop registered underauth.userin the response, because the gate compared whole keys. It is dropped now. If a page relied on a bareexceptentry pruning only the exact key, name the exact key (except: ['auth.user']) or narrow with a dotted path instead. -
errorsignoresonly/except. A partial reload that filtered a handler-supplied.with("errors", …)prop out, or narrowed it with a dotted entry, now ships it whole. Tests asserting a sliced or emptyerrorsobject on a partial reload need updating. To keep the bag out of a response deliberately, flag it -.prop("errors", Prop::eager(…).optional())- rather than relying on the partial-reload lists. -
Prop::resolve_with_ownergates flagged props too. It previously resolved any prop that was notProp::is_lazy()- an eager value or a resolver carrying a flag - without consulting the include set. It now gates every resolver-backed prop and only lets an already-materialized value through ungated. A#[data(lazy(deferred))]field consequently needs?include=<field>on the request before it resolves or is announced, the same as every other lazy flavor. Add the field to the request's?include=list, or drop thelazy(...)attribute if it was never meant to be opt-in. -
Scroll prop
resetno longer follows the merge-intent header. Code that readspage.scrollProps[key].resetdirectly - a custom infinite-scroll component, a test snapshot - will seereset: false(plus amergePropsentry) on a plain revisit that used to readreset: trueand carry no merge metadata. The official<InfiniteScroll>component behaves differently only on a plain revisit: it listens forreseton everyroutersuccessevent, not only an explicitrouter.reload(), so a normal revisit no longer clears its accumulated state unless the server actually named the key inX-Inertia-Reset, which matches Laravel. SendX-Inertia-Reset: <key>explicitly wherever the old "any non-append/prepend visit resets" behavior was relied upon. -
Prop::match_ontakesimpl MatchOnFields, notimpl Into<String>. The new bound is what lets one call name several fields (match_on(["id", "slug"])), and its impl list is deliberately closed -&str,String,[T; N], andVec<T>only. A blanket impl overIntoIteratoris not available: coherence rejects it against the&strandStringimpls, since nothing stops those types from gaining anIntoIteratorimpl later. Three argument types that compiled before no longer do:&String,Cow<'_, str>, andBox<str>. Pass a&strat the call site instead -match_on(name.as_str())for a&String,match_on(name.as_ref())for aCow<'_, str>,match_on(&*name)for aBox<str>. -
A dotted
only/exceptentry now narrows its top-level prop instead of excluding it entirely. Before this fix,X-Inertia-Partial-Data: user.namemadeshould_include_eagerlook for an exact-match"user"entry, found none, and silently dropped the wholeuserprop - a client asking for one field ofusergot nothing. Any frontend page component that happened to rely on that gap (treating a dottedrouter.reload({ only: [...] })as equivalent to omitting the key) now receives{ user: { name: ... } }instead. No code changes are required - this is what the Inertia v3 protocol already specifies the request/response contract to mean. The same fix applies toshould_include_optional, and its effect is operationally bigger: a dottedonlyentry (permissions.read) now counts as an explicit request for anOptionalorDeferprop's top-level key, which previously required a bare entry (permissions) to trigger at all. A request that used to skip that prop's resolver entirely now runs it - if the resolver hits a database or an external service, a client already sending dotted partial-reload requests starts issuing that work on requests that previously did none. Watch resolver call volume after upgrading if your app hasOptional/Deferprops with dotted partial-reload traffic. -
InertiaSharedData::sharenow takes the page component name. Add acomponent: &strparameter afterreq:-async fn share(&self, req: &dyn InertiaRequestExt) -> Result<IndexMap<String, Prop>, FrameworkError> +async fn share(&self, req: &dyn InertiaRequestExt, component: &str) -> Result<IndexMap<String, Prop>, FrameworkError>Ignore it (
_component) if your provider doesn't need to vary by page - Laravel'sRenderContextcarries the same pairing (component,request) forProvidesInertiaProperties::toInertiaProperties. -
Propis a struct, not an enum. Its variants are gone; construct and read props through methods:Prop::Eager(v)->Prop::eager(v)Prop::EagerNone->Prop::absent()Prop::Always(v)->Prop::eager(v).always()Prop::Lazy(r)->Prop::from_resolver(r)(Prop::lazy(closure)is unchanged)Prop::Optional(r)->Prop::from_resolver(r).optional()match prop { Prop::Eager(v) => … }->prop.as_value()matches!(prop, Prop::Lazy(_))->prop.is_lazy();matches!(prop, Prop::EagerNone)->prop.is_absent()TheDeferConfig,MergeConfig,OnceConfig, andScrollConfigpayload structs are removed - their fields are flags onPropnow.Prop::is_deferred()is renamedProp::has_resolver(), which is what it always meant.DeferOptions,OnceOptions,MergeStrategy,ScrollMetadata, and everyInertiaResponsebuilder method are unchanged, so an app that only uses the response builder needs no edits. Apps that build props by hand - typically anInertiaSharedDataimplementation - need the renames above.
-
This fix protects sessions you already have, not only requests from here on. Upgrading alone is enough: a session cookie written by an earlier release can carry a
_previous.urlthat was never sanitized, andSessionData::previous_url()now discards it on read the first time that session is used post-upgrade, rather than trusting it because it's already stored. You don't need to invalidate existing sessions, migrate the session table, or force a re-login. A request whose path looks protocol-relative (//host) also no longer updates the recorded previous URL going forward - if your app'sfallback!route (or any 200-answering route reachable on an unusual path) ever legitimately relied on such a path becoming theRedirect::back()target, it won't anymore. Either way, the previous, safe value in the session is left in place instead (orRedirect::back(fallback)'s own fallback wins, if nothing safe was ever recorded). No code change is needed unless you were depending on the exact edge case this closes, which was already an open-redirect risk. -
Drop the
[0]from everyerrors.<field>binding in your pages. With the new default shapeerrors.emailis a string, soerrors.email[0]renders its first character instead of the message. Change the TypeScript type fromstring[]tostringat the same time. If you would rather not touch your pages, setInertiaConfig::with_all_errors(true)on the config you pass toInertia::installand add theerrorValueType: string[]module augmentation for@inertiajs/core. The starter frontends ship the new shape. -
A handler that hand-rolled the redirect-back after a validation failure can delete it. The bridge is automatic now; a handler that still redirects itself keeps working, because the middleware only acts on a
422that carries a populatederrorsobject. -
A crashed
suprnova servechild now respawns instead of ending the session. If you relied on a crash stoppingsuprnova serveoutright (a CI smoke check, a script that treats exit as "something's wrong"), pass--no-restartto restore that behaviour exactly. Retries are also bounded by default: a process that crashes 5 times in a row stops being retried (raise the limit with--restart-tries, or use--no-restartfor the original one-crash-and-done behaviour). -
Model::TOUCHESis no longer an inherent const. Code that readComment::TOUCHESdirectly needsuse suprnova::EloquentModel;(orsuprnova::eloquent::EloquentModel) in scope - the const moved there so the parent-touch cascade, aModeltrait default, can read it. Agrep -rn TOUCHESover your app finds every call site; most apps have none, since the const previously did nothing at runtime. -
RelationEntrygained a field. Only code that constructs aRelationEntryby hand needs a change - addrelated_updated_at_columnto the literal. The macro-generated relation registrations the framework ships already emit it, so an ordinary app doing nothing but declaring relations through#[suprnova::model]is unaffected. -
Router::viewwith non-object props now panics at boot. It previously registered silently with an empty prop bag;viewdelegates toRouter::inertia, which requires an object (ornull) and panics otherwise. If aviewcall might carry non-object props, switch toRouter::try_inertiaand handle theErr- otherwise nothing changes for you. -
The Inertia version manifest default can change your version string the moment a build exists. An app or test that hardcodes
X-Inertia-Version: 1.0keeps working only until a Vite manifest shows up on disk; once one does, the version becomes the manifest hash instead. If you need the old constant, read it fromVersionResolver::from_manifest(path)yourself or pin.version(...)explicitly. Expect the first deploy after upgrading to force one full-page reload cycle for already-connected clients - one-time, and the point of the change. The no-manifest fallback value is exported assuprnova::MANIFEST_VERSION_FALLBACK, so you never need to hardcode"1.0"again. -
Move
Inertia::installandglobal_middleware!registration out ofbootstrap::register. Put them in a new function and pass it to.http_bootstrap(...)instead - the scaffold's new shape is a syncregister_http_stack()called as.http_bootstrap(|| async { bootstrap::register_http_stack() }). Apps that skip this keep today's behavior, worker-boot failure on a missing frontend manifest included.
1.2.4 - 2026-08-18
Security
-
The maintenance-mode bypass secret is compared in constant time.
MaintenanceMiddlewarematched the secret URL with a plain string compare, which returns at the first differing byte. Because the secret is a bearer credential carried in the request path, that timing difference told an attacker how long a prefix they had guessed correctly. The compare now runs over the full byte length viasubtle::ConstantTimeEq, short-circuiting only on a length mismatch - the same shape as the bypass-cookie compare next to it. -
rules::Urlnow rejects script URIs. The rule accepted any schemeurl::Urlcould parse,javascript:andvbscript:included, so a validated URL could still be a script-execution sink when rendered into anhref. It now applies Laravel'surlrule shape (Illuminate\Support\Str::isUrl's^(PROTOCOLS)://HOSTpattern): the scheme must be on Laravel's allowlist, be followed by://, and be followed by a non-empty host - Laravel's host group has no?, so an absent or empty host never matches even with a listed scheme. The scheme list and the://-plus-host requirement are Laravel's verbatim; the host itself is parsed by theurlcrate rather than Laravel's regex, so a few edge cases still differ - an out-of-range port is rejected here and accepted there, and IDN hosts normalise differently. NewUrl::protocols(&[...])mirrors Laravel'surl:http,https;HttpUrlis now literal sugar for it and keeps its own message. Behaviour change: a URL with an unlisted scheme that used to validate now fails - name the scheme withUrl::protocols(&["myapp"])if you meant to accept it. Two more behaviour changes:mailto:,data:, andtel:are on Laravel's allowlist by name but don't carry an authority component, so they now fail; andfile:///etc/passwd-style paths -scheme://with nothing between the last two slashes - now fail too, since an empty string isn't a host either. Both follow from Laravel's own://-plus-host rule. -
Inertia responses now advertise
Vary: X-Inertiaeverywhere. The header was set only on the page-object responses themselves. Redirects, 404s, 422s, and static responses carried none, so a shared cache keyed on the URL alone could serve the JSON page object to a hard browser navigation, or the HTML shell to an Inertia XHR. The newInertiaHeadersMiddleware- registered byInertia::installas the outermost of the three - sets it on every response, and turns an empty200on an Inertia visit into a303back rather than a response the client rejects as non-Inertia.InertiaVersionMiddlewarenow re-flashes the session before its409, so a flashed error survives the client's follow-up full-page GET. -
Three Inertia response fixes.
InertiaResponse::location_for(&req, url)returns409+X-Inertia-Locationfor an Inertia XHR and a plain302+Locationfor a hard navigation, so an OAuth or SSO bounce entered outside the SPA no longer dead-ends on a body-less409. The existinglocation(url)keeps its always-409shape. NewApp::clear_history()flashes the history-clear flag into the session so it survives the logout redirect and lands on the page that actually renders - the per-response.clear_history()marked only the redirect the browser throws away, leaving the previous session's encrypted history decryptable. And aonceprop is now skipped only on a full Inertia visit: an explicitrouter.reload({ only: ['stats'] })re-resolves it instead of returning nothing. -
The SES transport now sends custom message headers.
Mail::to(..).header("List-Unsubscribe", ...)andMailable::headers()were dropped silently underMAIL_DRIVER=ses: theContent.Simplerequest body had noHeadersfield and the raw-MIME builder never readOutgoingMessage::headers, even though every other transport forwards them. Both SES paths now carry them -Headersas SES v2's{Name, Value}list, raw MIME as real header lines - so unsubscribe links, threading headers and routing hints survive a driver swap. Header names are validated up front on both paths - CR, LF and NUL (the injection bytes, as the Mailgun transport already refuses) and anything that is not a valid RFC 5322 field name (spaces, colons, non-ASCII) - so attaching a file never changes whether a message is accepted.
Fixed
-
Nested validation failures now reach the 422 body.
#[validate(nested)]failures on a nested struct or on an element of a validatedVec<T>were dropped between the validator and the response: the request was correctly rejected with 422, but theerrorsmap came back empty, so no message rendered and the client could not tell which field was at fault. Nested failures are now flattened into Laravel's dotted notation -address.street,items.1.name,order.items.2.sku- alongside the top-level ones. -
The Inertia page object's
urlkeeps the query string.page.urlwas the request path only, so the client recorded/usersfor a visit to/users?page=2&sort=name. Every back/forward navigation and everyrouter.reload()then replayed the page without its pagination cursor, sort, or filters. It is now path plus query - the same derivationInertiaVersionMiddlewarealready used forX-Inertia-Location, so by default the two agree byte for byte. NewInertiaConfig::url_resolver(...)overrides how the page object names the page (Laravel'sInertia::resolveUrlUsing); the version bounce keeps naming the URL that arrived, because that is the URL the browser has to fetch. -
Inertia::installnow applies its config to every response. The config handed toInertia::installwas read for three fields and then dropped, so everyInertiaResponsebuilt without an explicit.with_config(...)rendered fromInertiaConfig::default(). An app scaffolded with--frontend reactserved the Svelte entry point and no React refresh preamble unlessSUPRNOVA_FRONTENDwas set in the environment; SSR enabled on the config never reached a response; and the page object's asset version came from a different config than the version middleware's resolver. The installed config is now retained on the container's Inertia registry and is whatInertiaResponse::newstarts from. Per-response.with_config(...)still overrides, apps that never callInertia::installare unchanged, and a failed (fail-closed) install retains nothing. As a side effect the production Vite manifest is now parsed once per process rather than once per response. -
Scaffolded apps now install the Inertia protocol middlewares. The
bootstrap.rswritten bysuprnova newregistered the session, locale, CSRF and include middlewares but never calledInertia::install, so a generated app had neitherInertiaVersionMiddlewarenorInertia303Middleware: a browser still running the previous bundle was never told to reload after a deploy, and aPUT/PATCH/DELETEthat redirected stayed on a302the client could follow with the original verb. The call now lands afterSessionMiddleware- where the version middleware's session re-flash works - with a namedINERTIA_VERSIONconstant to bump when assets change, and it pins the frontend the project was generated with (.frontend(Frontend::React)for--frontend react), so the HTML shell loads that framework's Vite entry point instead of falling back to Svelte's. The generated.envnow setsSUPRNOVA_FRONTENDto match. The--apistarter is unchanged; it has no frontend. -
Queue::push_uniqueno longer reports a queued job as skipped. The return value was computed withmatches!(outcome, Idempotent::Fresh(())), which foldedIdempotent::FreshUnfencedintofalse- the outcome where the envelope was pushed but the dedupe lease was lost mid-push. Callers branching on that boolean were told a job that was about to run had been suppressed as a duplicate. All three outcomes are now matched exhaustively: a lost lease returnstruewith awarnnaming the job and its unique key, and only a real duplicate returnsfalse.push_unique_laterandlater_uniqueshare the path and are fixed with it.
Changed
- Parity baseline moved to Laravel 13.25.0. The 13.23.0, 13.24.0 and
13.25.0 release notes were traced item by item to the framework's own
surface. Everything that reached a Suprnova code path is either fixed in
this release or has a row in
manual/parity.mdmarkednot yetorby design no.
Upgrading
Two changes can alter a running app without any code change on your side.
-
Settings on the config you pass to
Inertia::installnow take effect. They were read for three fields and dropped. If your install config sets.ssr(...), SSR is now on: start the worker (suprnova ssr:start) before deploying, or drop the.ssr(...)call..entry_point,.assets_base_url,.default_titleand.encrypt_history(...)set there also reach the page now. -
rules::Urlrejects more. Values that used to pass and no longer do: any scheme outside Laravel's allowlist,javascript:andvbscript:among them;mailto:,data:andtel:, which are on the allowlist but carry no://host; andscheme://with an empty host, such asfile:///path. If you meant to accept a scheme, name it:Url::protocols(&["myapp"]).
1.2.3 - 2026-08-16
Fixed
- Datetime casts now read database-native
CURRENT_TIMESTAMPtext.AsDateTime,AsImmutableDateTime, andAsOptionalDateTimecontinue to write canonical RFC-3339, while reads also accept PostgreSQL's timezone-bearing text and timezone-free SQLite/MySQL text. Timezone-free values are interpreted as UTC, matching the framework's UTC timestamp contract.
1.2.2 - 2026-08-14
Fixed
- Nullable non-text values now work across attribute-based writes on
PostgreSQL. Typed
Builder::update_allandBuilder::upsert, model-lessDB::table().insert/update, and many-to-many pivot extras render explicit JSON nulls as SQLNULLwhile continuing to bind every non-null value. This preserves the target column's type instead of sending a text-typed null parameter that PostgreSQL rejects for bigint, integer, boolean, timestamp, and other non-text columns. Multi-row upserts now also reject missing or extra columns instead of silently converting a malformed row shape to null. Automatic many-to-many pivot timestamps are bound as typed UTC datetimes instead of text.
Security
- The release gate now distinguishes dormant lockfile metadata from compiled
dependencies across the whole workspace. Cargo records rust_decimal's
unused optional rkyv 0.7 compatibility dependency in
Cargo.lock; the gate now proves that neither rkyv nor its derive crate is reachable from any workspace member, feature, target, or dependency edge. The corresponding RustSec exception is owned, expires on 2026-11-14, and must be removed when rust_decimal no longer records that legacy optional dependency.
1.2.1 - 2026-08-09
Changed
- Suprnova moved to the
eas4aiGitHub organization. Repository URLs in package metadata, documentation, dependency examples, and scaffold templates now usegithub.com/eas4ai. New projects also use the monitoredshawn@eas4ai.comauthor email. This release made no runtime behavior changes.
1.2.0 - 2026-08-05
Added
-
The manual ships in seven languages.
manual/es/,manual/fr/,manual/de/,manual/pt-BR/,manual/ja/andmanual/zh-Hans/each carry the full 104-chapter manual - every chapter, the table of contents, and this changelog - translated from the English source. English remains canonical: chapter structure, code blocks, identifiers, CLI commands and environment variables are held byte-identical to the source, so a translated chapter can never disagree with the English about what the framework does, only say it in the reader's language.The translations were produced and reviewed for suprnova.app, which renders this manual as its
/docs. Every section carries a review ledger there: verdicts are recorded against content hashes of both the English and the translation, two independent reviewers must pass the exact bytes for a section to count as approved, and per-locale glossaries pin the terminology rulings (which terms stay English, which take the native word, and why). Corrections are welcome in either repo - a fix here reaches the site on its next sync.
1.1.0 - 2026-08-02
Added
-
Per-locale fallback chains.
LocalizationConfiggainsparents(APP_LOCALE_PARENTS, comma-separatedchild=parentpairs, or the chainable.parent(child, parent)builder): a locale can inherit from a configured sibling before falling further back to the globalfallback_locale-pt-PTfrompt-BR,en-AUfromen-GB, and so on, transitively.Lang::get/try_get/get_with/try_get_with/hasall walk the chain, current locale first, so this works for anyTranslatordriver, not just the bundled one. A malformed pair, an invalid locale, a child named twice, or a cycle (including a locale naming itself as its own parent) fails loudly at config load rather than degrading at request time.Served catalogs stay chain-flattened ahead of time:
FluentTranslatornow builds each locale's/_suprnova/lang/<locale>.ftlcatalog as a fold - the embedded framework catalog at the bottom foren/en-*locales, then the locale's configured parent chain, then its own*.ftlfiles - so a chained locale is still one self-contained file the browser fetches once, with no client-side chain awareness needed. Flattening covers configured parents only; the terminalfallback_localeis still aLang-facade-level fallback, not baked into the served bytes.This makes delta-style catalogs practical: a
lang/pt-PT/directory can hold only the handful of strings that actually differ fromlang/pt-BR/, rather than a full duplicate catalog. The merge that makes it possible works at the Fluent AST level - a child's value replaces the parent's, attributes merge by name (an override that doesn't mention an attribute no longer loses it), select expressions replace whole (CLDR plural categories are locale-dependent, so variant-by-variant merging isn't coherent), and child-only entries append. Seemanual/localization.md's new "Fallback chains" section for the full contract.
Changed
LocalizationConfiggained theparentsfield.from_env()and the builder are unaffected; a literal struct constructor (tests building aLocalizationConfigby hand) needs one more field.- Served catalog text is now serializer-normalized for every locale,
and intra-locale multi-file merging (several
.ftlfiles in one locale directory) now goes through the same AST-level merge as parent chains rather than simple bundle-overriding. Resolved translations are unchanged except for the two strict improvements below; the underlying bytes rotate regardless -ETag/?v=<hash>rotates once on upgrade. The improvements: an override no longer silently drops the attributes it doesn't mention, and an attributes-only override no longer strips the message's own value (previously an error or a fallback resolution; it now resolves to the earlier override's value).
1.0.0 - 2026-08-02
Added
-
Localization. Message catalogs in
lang/<locale>/*.ftl(Fluent), aLangfacade with the__!("key", name: value)macro, per-request locale detection (LocaleMiddleware: session → cookie →Accept-Language→APP_LOCALE), and locale-aware formatting for numbers, currency, dates, times, lists, and relative times over ICU4X.manual/localization.mdis the chapter.The built-in validation rules stop hardcoding English. Each returns a keyed message (
validation-minplus its arguments and an English fallback), translated once at the serialization boundary - so a Spanish app gets Spanish validation errors by dropping inlang/es/validation.ftl, with no rule wrapping and no forked copy of the framework's messages. Field names humanize through afield-<name>lookup.Rule::passes(andContextualRule/AsyncRule) now returnResult<(), ValidationMessage>; a custom rule'sErr("…".into())body still compiles and still renders verbatim, but the signature in yourimplneeds the new type.The browser gets the same bytes the server resolved: the merged catalog is served at
/_suprnova/lang/<locale>.ftlwith an ETag and an immutable?v=<hash>form, the three starter kits parse it with@fluent/bundle, andsuprnova generate-typesemits aMessageKeyunion so renaming a message points the TypeScript compiler at every call site.Fluent rather than Laravel-style PHP arrays because one format has to serve both the server and the browser, and because CLDR plural categories are what gets Russian, Polish, and Arabic right -
trans_choice's integer ranges cannot, which is why there is notrans_choicehere. Behind a default-onlocalizationfeature;--no-default-featuresstill compiles and still validates, using the embedded English fallbacks. -
IntoInertiaScrollforPaginator. The trait was implemented forLengthAwarePaginatorandCursorPaginatorbut not for the simple paginator, sosimple_paginateresults could not feedInertia::paginateat all - despitesimple.rs's own module docs pointing at it as the URL-generation path. That left offset-paginated Inertia collections with a choice between aCOUNT(*)per request and hand-rolling the scroll metadata.next_pagecomes from theLIMIT n+1overflow probe rather than a computed last page, there being no total to compute one from.
Fixed
-
suprnova generate-typesemitted a different file on every run. The topological sort seeded its work queue by iterating aHashMap, and Rust randomises hash iteration order per process, so consecutive runs ordered the same interfaces differently. The output is a checked-in artifact, so every run produced a diff - and a generated file that churns for no reason is one people stop regenerating, after which it quietly stops describing the Rust it claims to. The directory walk is sorted too, so the output no longer depends on filesystem order either. Two runs of the same source are now byte-identical. -
topological_sortdid the opposite of its doc comment, emitting dependents before dependencies. Harmless - a TypeScript interface may reference one declared later in the same file - so the comment is corrected rather than the order, which would have reshuffled a tracked file for no benefit.
0.9.1 - 2026-08-01
Three defects, all found by running the dogfood app under a containerised harness rather than by reading the code. Every one of them is invisible to a test suite that never stops a process the way production stops it.
They compound in a specific order: a rolling deploy SIGKILLs a worker mid-job (the first), and that job then takes a reclaim path that never counted the attempt (the second).
Fixed
-
schedule:work,queue:workandworkflow:workignored SIGTERM. Each selected ontokio::signal::ctrl_c()alone, which installs a SIGINT handler - so SIGTERM had no handler anywhere in the process, and SIGTERM is whatdocker stop, Coolify, systemd and Kubernetes send. All three already had a careful bounded drain behind thatselect!; none of it had ever executed under a supervisor. Measured before the fix: adocker stopon aqueue:workcontainer burned its whole 40s grace window and exited 137 with the in-flight job destroyed. As PID 1 - which is what a container runs - the kernel discards an unhandled SIGTERM outright, so the process did not die badly; it did not die at all until SIGKILL.Server::runalready handled both signals correctly and its listener is now shared, which also closes a missed-signal window in the scheduler's loop. -
A job that killed its worker could never be dead-lettered. A job whose handler fails is nacked and its attempt counted, so it dead-letters after
max_tries. A job that kills its worker - OOM, abort, segfault, or the SIGKILL above - settles nothing; its reservation merely lapses, and every driver used to redeliver it byte-identical. Such a job is immortal: it kills each worker that claims it, comes back unchanged, and kills the next one, for as long as anything restarts workers. All three drivers now charge the attempt where they learn a worker died, because swappingQUEUE_DRIVERmust not change whether a poison job can be stopped.attemptsnow means "deliveries to a worker" rather than "handler failures" - documented inmanual/queues.md, because a worker lost for unrelated reasons burns an attempt too. -
…and the exhausted job is now dead-lettered before it is dispatched. Counting the attempt was necessary and not sufficient. Every dead-letter decision lived in the worker's settlement path, which assumes the handler returns - so it never ran for exactly the jobs that could not return. With the driver fix alone the counter climbed (measured: 0 → 1 → 2 across three killed workers) and nothing acted on it. The budget is now spent before the handler runs. Caught only by re-running the container experiment after the first fix looked correct.
-
The daemons had no tracing subscriber.
servegets one frominit_telemetry;queue:work,schedule:work,schedule:runandworkflow:workcome through a different boot path and got nothing, so everytracing::line they emit went nowhere andLOG_LEVELwas inert for them. That is most of what they have to say - a worker dead-lettering a job, a scheduler skipping a tick it lost, a lock it could not release. In a container the only visible output was the startup banner, and the process looked idle while doing all of it. Two of the defects in this release were invisible until this was fixed. -
A dead-letter with no failed-jobs store bound was a silent deletion. The persist step sat inside
if let Some(store) = .., so with no store the arm did not match and execution fell through to the ack - quieter than the failure path directly above it, which at least leaves the reservation intact. An absent store was treated as more successful than a broken one. It now logs the full envelope at ERROR, because that is whatqueue:retryre-pushes: the difference between work recoverable by hand and work that ceased to exist. -
QUEUE_DRIVER=databasenow binds a failed-jobs store.failed_jobsis part of that driver's contract -queue:retryreads it andQueue::retry_failedcannot work without it - butbootstrap_from_envwired the driver and left the store unset, so a database-backed queue dead-lettered into nothing unless the app bound one by hand. Configurable viaQUEUE_FAILED_DB_TABLE. Only for this driver:memoryis ephemeral by construction andredishas no table to write to. -
Redis reclaim latency now follows
--visibility-timeout. The flag sets XAUTOCLAIM's idle threshold, but a separate clock governs how often a consumer looks, and the driver left it at sea-streamer's 30s default - so--visibility-timeout 5really meant "up to 35 seconds". The interval now tracks the configured timeout, clamped to 1s..=30s so a short timeout cannot become an XAUTOCLAIM storm and a long one can only make reclaim faster than before.
Added
-
TaskBuilder::on_one_server()/on_one_server_for(ttl)- run a scheduled task exactly once per due tick across replicas. Without it nothing elects a leader for a tick: eachschedule:workprocess evaluates the schedule independently, and three replicas were measured running every due task three times, every minute, with no variance. A nightly billing job on three replicas billed every customer three times.without_overlapping()does not cover this and cannot: its lock is keyed on the task and released when the handler returns, so a fast task frees it before a second replica looks.on_one_serverkeys on the task and the tick and holds the lock past the handler, letting it expire on TTL. The two compose.Opt-in, matching Laravel. Diverges from Laravel in failing closed: the election is only as shared as the cache behind it, so a production boot with
CACHE_DRIVER=memoryand a single-server task is refused, naming the offending tasks, withSCHEDULE_ALLOW_MEMORY_LOCK_IN_PRODUCTION=truefor deployments that genuinely run one scheduler.
Changed
manual/deployment.mdno longer says "run exactly oneschedule:workprocess" as the only option, and gains a Stopping cleanly section covering the drain windows per subsystem, how to size a platform's termination grace above them, and why PID 1 makes a missing signal handler worse than it sounds.
0.9.0 - 2026-07-31
Security
-
Auth issuance could only be throttled per caller, never per recipient. An address-keyed limit answers "is one client noisy"; it cannot answer "is one mailbox being flooded". An attacker spread across a botnet or a single IPv6
/64stayed under every per-IP budget while filling one victim's inbox with password-reset mail, and nothing in the framework could express the limit that would have stopped it - a key function could read the path, headers, and query string, but not a form-encoded body, so the address was invisible on exactly the route that carries it.identity_keykeys a bucket on the account being acted on. It reads the query string first and then a buffered form body, so one key function covers both shapes; the value is trimmed and lowercased, becauseAlice@Example.comreaches the same mailbox asalice@example.comand a limit bypassed by holding down shift is not a limit; and it is hashed, because a rate-limit backend is frequently a shared Redis with weaker access control than the primary database.Two new middleware builders support it.
key_reads_body(cap)buffers the body before keying - opt-in, because buffering is work an unauthenticated caller gets to make you do, and a body over the cap is refused with 413 rather than passed through unkeyed.only_when(pred)skips a limiter entirely for requests it has nothing to say about, which is what keeps a stacked per-recipient budget from silently becoming the binding limit on routes that name no recipient.The dogfood app now stacks both on its issuance group: 10 per 5 minutes per address, 3 per 15 minutes per recipient.
A review of Torii's session, password, OAuth, and passkey paths turned up
eight defects, all fixed in the pinned fork (suprnova-torii-rs 968b0be).
- Expired sessions could be refreshed back to life. The SeaORM session
repository's
refreshhad no expiry predicate and unconditionally extendedexpires_at, andOpaqueSessionProvider::refresh_sessionskipped theis_expired()check thatget_sessionperforms. A token held past its expiry could be renewed indefinitely. Fixed at both layers. Not reachable through Suprnova's own surface - neitherToriinor the framework exposes session refresh - but it is public API of both crates. - The login form leaked which accounts exist, by timing. Authentication returned as soon as the email missed, skipping Argon2 entirely: measured at 54µs for an unknown address against 719ms for a wrong password, a ~13,000x gap readable over a network. Both failure paths now verify against a dummy hash so they cost the same. This one was reachable through Suprnova's password login.
- The JWT
issclaim was written but never verified. Algorithm pinning was already correct -alg: noneand HS/RS confusion were never possible - but the issuer was decoration, so two services sharing a signing key would accept each other's sessions. Now enforced when an issuer is configured. - A single-use PKCE verifier could be claimed twice. Consumption was a
read followed by a delete, so two OAuth callbacks for the same
csrf_statecould both read it before either delete landed. Now claimed in one operation -DELETE ... RETURNINGon Postgres, a primary-key delete whose affected-row count picks the winner on SeaORM. - Expired sessions were listed as active.
find_by_user_idhad no expiry filter, and expired rows survive until cleanup runs, so a "devices you're signed in on" screen offered users dead sessions to revoke while saying nothing about the live one. - A passkey lookup was named
authenticate. Torii'sPasskeyService::authenticate_credentialtook a credential ID and returned the owning user, andPasskeyAuth::authenticateminted a session from it. Torii stores passkeys - it carries no WebAuthn dependency and cannot verify an assertion, so the only thing those calls proved was that the caller knew a credential ID: a value the browser sends in the clear andallowCredentialshands to anyone who can start a ceremony. Renamed tofind_user_by_credentialandcreate_session_for_verified_credential, both documenting that verification is the caller's job. Not reachable through Suprnova, which driveswebauthn-rsitself (seetorii_integration::passkey) and reaches Torii only for credential storage. - A WebAuthn challenge was replayable for its whole TTL. Neither backend
consumed a challenge on read, and the SeaORM
get_challengealso ignoredexpires_atentirely, returning expired challenges as live. Reads now exclude expired rows on both backends, and a newtake_challengeclaims one exactly once - the same delete-decides-the-winner shape as the PKCE fix.
Breaking
-
Azure Blob Storage and Google Cloud Storage moved behind the new
filesystem-azureandfilesystem-gcsfeatures.Storage::register_azblob,register_azblob_with,register_gcs,register_gcs_with,AzBlobConfigandGcsConfigno longer exist unless you enable the matching feature. If you use either backend, add it to your dependency:suprnova = { git = "…", tag = "v…", features = ["filesystem-gcs"] }You get a compile error naming the missing item, not a runtime failure.
Both opendal service crates pull
rsa, which carries RUSTSEC-2023-0071 (the Marvin timing attack) with no fixed release upstream. They were the only crates enablingreqsign-core/jwt, the featurereqsign-core's optionalrsasits behind, so gating them severs all three opendal paths to it at once.rsais now avoidable:--no-default-features --features filesystem,database-postgresresolves without it and still has the storage subsystem. Previously no feature combination could shed it while keeping storage at all.A stock default build still carries
rsa-database-mysqlis a default feature andsqlx-mysql 0.8.6depends on it non-optionally - so the audit exception stays open. S3 is deliberately not gated:reqsign-aws-v4takesreqsign-corewithoutjwt, so the S3 driver never contributed a path, and gating it would break the most-used cloud backend while removing nothing.
Added
suprnova --version, with-vas well as clap's default-V. Asking a CLI its version with the flag every other CLI uses should not print a usage error.
Fixed
- Two Redis operations had no upper bound. The cache's tag flush read a
tag's whole member set with
SMEMBERSand deleted key by key, so a tag with a large membership stalled the connection and a concurrent write could be lost between the read and the delete; tags are now generation-based, flushed atomically, and scanned with a boundedSSCAN. The delayed-queue promotion pass moved every due job in one unboundedZRANGEBYSCORE, so a backlog that came due together produced a single enormous script; it now promotes in batches. - Two shutdown drains waited forever.
schedule:workon Ctrl-C and the workflow worker after cancellation both awaited every in-flight task with no deadline, so one task that never returned held the process open untilSIGKILL- an operator sees a daemon that "doesn't stop". Both now wait a bounded grace, then abort what remains and report the count. - The release version-pin sweep only recognised one of the two pin
syntaxes, so every file carrying a
cargo install --tag vX.Y.Zline and no dependency snippet was never discovered.suprnova-cli/README.mdhad been telling readers to install v0.6.0 for three releases;manual/cli.mdandmanual/cli-new.mdsat at v0.7.2;manual/installation.mdcarried both forms and had one bumped while the other froze. Discovery and rewrite now read from one pattern table, and a file's rules are derived from its content. cargo docfailed for any build withfilesystembut withouttesting- sevenStorage::fakeintra-doc links could not resolve, andlib.rsdenies broken links.testingis a default feature, so no gate step had ever built that combination;check-feature-matrix.shnow does.- Torii's migrations could not be replayed over their own schema, so a
database holding it without the
torii_migrationstracking table - restored from a dump that skipped it, or migrated by hand - could not be brought under management. EveryTable::create()carried.if_not_exists(); none of the 19Index::create()calls did, nor did theADD COLUMN locked_atalter, so replay sailed through the tables and died on the firstCREATE INDEX. Fixed in the pinned fork (suprnova-torii-rsa0f956d) viahas_index/has_columnrather thanIF NOT EXISTS, which sea-query silently drops for MySQL - the syntactic fix would have left a default-featured build broken. - A failed Torii migration aborted the process instead of returning an
error.
SeaORMStorage::migrateunwrapped the migrator and returnedOk(())unconditionally, soinit_torii's mapping of the failure into aFrameworkErrorwas unreachable code. - An app's own
userstable silently suppressed Torii's, because.if_not_exists()cannot tell "already mine" from "already somebody else's". The migration reported success and authentication failed later on a missing column - the reason the--apistarter names its tableapp_users. Torii's migration now warns at migrate time when an existinguserstable lacks columns it requires, naming the columns and the remedy. It stays a warning rather than a hard failure so existing deployments keep booting. - The Railway and DigitalOcean deployment guides pointed the platform
health check at a path that could probe Postgres. Both platforms restart
the container when that check fails, so following the advice turned a
database blip into a restart loop across every replica. Both now use
/_suprnova/health/live, with the database probed by hand from the console. The legacy paths still resolve; nothing already deployed needs changing.
0.8.0 - 2026-07-30
Remediation of an external red-team audit. The audit returned 19 P1 findings and a NO-GO verdict for 1.0; this release closes all nineteen, plus a number of defects found while fixing them that the audit had not named.
Several fixes deliberately turn a silent misconfiguration into a refused boot. Read Upgrading before deploying - a production app that has been running happily may not start.
Upgrading
Three configurations that used to boot with a warning (or in silence) now fail closed in production. Each error names the variable that unblocks it, and each has an explicit override for the deployment where the risk is genuinely absent.
- A non-delivering mail driver.
MAIL_DRIVERunset,log,memory, or an unrecognised value all resolved to a transport that renders mail and discards it - so password resets reported success while nothing was sent. Override:MAIL_ALLOW_NON_DELIVERING_IN_PRODUCTION=true. - Cleartext SMTP. Three of the four credential combinations landed on
an unencrypted transport, and the both-unset case logged a warning and
sent anyway. Override:
MAIL_ALLOW_INSECURE_SMTP_IN_PRODUCTION=true. - The in-memory rate limiter. Its buckets live in one process's heap,
so behind N replicas every quota is really N× and each deploy resets
them. Point
RATE_LIMIT_DRIVERatredis, or setRATE_LIMIT_ALLOW_MEMORY_IN_PRODUCTION=trueif you genuinely run one process. An unrecognised driver value fails for the same reason, because it fell back to memory -RATE_LIMIT_DRIVER=Redis, capitalised, is the case most likely to reach production because it looks configured.
Development, testing and staging are unchanged in all three cases. Staging is deliberately not gated: hard-failing it pushes teams to set the override globally, which disarms the check where it matters.
Two behaviour changes that are not boot failures:
fillandfirst_or_newreject malformed values. A value that cannot decode into its field's type used to become that field'sDefaultand returnOk-fill(attrs!{ age: "abc" })setage = 0and reported success. It now returns aValidationErrornaming the field, and leaves the model untouched. Unknown columns are still skipped silently (Laravel parity), and numeric widening still works./_suprnova/health?db=trueno longer returns the driver error. The detail moves to the log; the body keeps"database": "error". Debug builds still include it. Dashboards parsingstatus/databaseare unaffected.url::signature_has_not_expirednow requires a valid signature, and is deprecated. It used to answertruefor a forged URL - a bad signature is not "expired", because it never had an expiry to miss - so any handler guarding on it alone accepted forgeries. It is now identical tohas_valid_signature. If you were using it to tell expired from invalid (to render "request a fresh link" rather than a 403), switch tourl::signature_verdict, which returns all three states. This diverges from Laravel'sURL::signatureHasNotExpired, deliberately.
Two additions that need something from you only if you opt in:
QueueDrivergainedsettleandrelease, both with default implementations, so existing driver impls keep compiling unchanged. Implementsettleif your backend can commit a follow-up write and an acknowledgement in one transaction; implementreleaseif it can requeue a reserved message in place.- Batch accounting can now be durable.
DatabaseBatchRepositoryneeds two new tables,job_batchesandjob_batch_settlements- add them to your migrations, as withjobsandfailed_jobs. The schema is inmanual/queues.md. Nothing changes if you stay onMemoryBatchRepository.
Security
-
Slowloris (SEC-07). hyper's header-read timeout was documented as 30s but inert - it only arms when a timer is installed on the connection builder, and none was. A client could hold a connection, and a
SERVER_MAX_CONNECTIONSpermit, indefinitely. Now armed and configurable viaSERVER_HEADER_READ_TIMEOUT. -
Multipart uploads (SEC-05). The cap applied to individual part payloads but not to the raw stream, so a body could exceed the limit in aggregate. Now capped at the stream.
-
Webhook HMAC with an empty key (SEC-08). Both payment adapters accepted a blank secret, which verifies anything. Refused on both.
-
Paddle signature parsing (P2-11). An odd-length or non-hex
paddle-signaturereached the pinned SDK and panicked inside it. Now validated first: a malformed signature is a 401. -
Passkey enrolment and reset tokens (SEC-01, SEC-02). Anonymous enrolment against an existing email, non-owner enrolment, and owner enrolment without recent reauth are each refused with distinct statuses. A password login now stamps the reauth window.
-
dev:tls(SEC-10). A project could choose the CA the command trusts. -
Generated Docker Compose (P2-12). Published Postgres and Redis on all interfaces with credentials committed in this repository. Now bound to loopback with per-scaffold generated passwords,
.envwritten 0600, and symlinked targets refused. -
Health endpoint (P2-01, CI-05). It decided whether to query the database with
query.contains("db=true")- a substring test, so?nodb=trueran the probe too. Now parsed properly. The 503 no longer embeds the driver error, which named hosts, ports, schemas and versions. -
Credential issuance throttling (P2-02). The four auth-issuance routes in the reference app carried no rate limit at all, and the one route that did keyed its bucket on the raw
x-forwarded-forheader - which any client can vary per request to get a fresh bucket. Both fixed; the issuance budget is shared across the four routes so rotating between them does not multiply it. -
A redelivered chain step re-pushed its successor under a new id (DATA-02b, partial). Settlement pushes the next chain link before acking, deliberately: acking first means a crash in that window loses the chain permanently, and a duplicate is recoverable where silent loss is not. But the successor's envelope got a fresh
Uuid::new_v4()on every push, so the duplicate produced by that trade was indistinguishable from a legitimate new step - to the driver, to an outbox, and to the handler.That last one is the real cost. The framework's delivery contract is at-least-once and its answer to duplicates is "handlers must be idempotent" - but a handler keyed on
env.id, the only identifier it receives, could not satisfy that contract for a chained job, because the duplicate arrived under a new id every time. The contract was unsatisfiable by construction.The successor's id is now a UUIDv5 derived from its predecessor's, which is stable across that predecessor's own redeliveries. A redelivered step re-pushes the id it pushed before. No schema change, no new field, no new dependency.
This makes the duplicate detectable, which is the primitive the rest of DATA-02b was missing. It does not make the push atomic with the ack (that needs the outbox), and nothing yet rejects the duplicate on the way in. Both remain open.
-
Signed URLs verified one URL and executed another (SEC-04). The canonical form collapsed query pairs into a map, so a repeated key kept only its last value - while
Request::query_paramreturned the first. A legitimately signed?user=victimcould therefore be replayed as?user=attacker&user=victimwith the original signature untouched: verification canonicalised overvictimand passed, and the handler acted onattacker.The canonical form now carries every pair, sorted by
(key, value), so the signature covers the exact multiset of parameters - adding, removing, or substituting any value breaks the HMAC. A repeatedsignatureorexpiresis refused outright, since two of either leaves no non-arbitrary answer to which one governs.Request::query_paramnow resolves a repeated key to its last value, matchingquery_paramsandContext::query_param; it was the only one of the three that disagreed, and that disagreement was the other half of the defect. Existing signed links keep working - with no repeated keys the payload bytes are unchanged, which a test pins, because a canonical-form change that silently invalidated every outstanding password-reset link would be worse than the bug.Six regression tests, including both attack orderings, a legitimately repeated key that must still sign and verify, and the reordering guarantee. Not changed:
signature_has_not_expiredstill reports a forged signature as "not expired". That is Laravel's behaviour, was settled deliberately as a documentation fix, and has its own test pinning it against a well-meaning "correction". -
RBAC under Postgres. Verified against a real Postgres rather than SQLite alone.
-
Four RustSec advisories eliminated, not renewed. The Pinecone driver was rewritten against Pinecone's REST API, dropping
pinecone-sdk 0.1.2- whose newest release dates from 2024-09-06 - and with ittonic 0.11 → rustls 0.22 → rustls-webpki 0.102and RUSTSEC-2026-0049 / -0098 / -0099 / -0104. All four were fixed upstream inrustls-webpki >= 0.103.13, which this workspace already resolved for its other TLS users; one abandoned crate held the tree on the vulnerable line..cargo/audit.tomlis down from five ignores to one. See Changed for what this means for the driver's API. -
Audit exceptions now expire. Every entry in
.cargo/audit.tomlcarries anOWNERand anEXPIRESdate, andscripts/check-audit.shfails the release gate on a missing owner, a missing or unparseable date, or a lapsed one.cargo audithas no notion of an expiring ignore, so one added "temporarily" stayed until somebody re-read the file. The remaining entry (RUSTSEC-2023-0071,rsa, which has no fixed release at all) is owned and dated. -
Reachability claims are checked, not asserted.
scripts/check-feature-matrix.shresolves real dependency trees and asserts that no build - including--all-features, which is whatcargo auditactually reads - containspinecone-sdk,rustls-webpki 0.102.xortonic 0.11.x. An exception justified by a comment nothing verifies stops being true the first time someone adds a dependency.
Fixed
- Every release on a database-backed queue was silently a no-op.
JobOutcome::Released- a busyWithoutOverlappinglock, a rate-limiter backoff - was implemented as "push a copy, then ack the original". The envelope id is thejobstable's primary key, so the copy collided with the row still holding the live reservation and the push failed withUNIQUE constraint failed: jobs.id. The worker then correctly declined to ack, so the requested delay was never applied, noJobReleasedevent fired, and the job simply parked until visibility expiry redelivered it. Releases are now one driver call, done in place. - A partial batch dispatch orphaned the jobs it had already queued
(DATA-02). When a
driver.pushfailed mid-loop,PendingBatch::dispatchdeleted the batch row - but the envelopes already in the queue were still stamped with that batch id, so each of them settled against a batch that no longer existed, returningErr(batch not found)on every delivery, forever. The batch is now settled instead: undispatched jobs are recorded as failures and the batch is cancelled, so the queued ones settle normally and the terminal callbacks still fire. - Nothing tested that
url::has_valid_signaturerejects a forged URL. Found while verifying the SEC-04 fix: the entire framework suite passed with the primary signed-URL guard rewritten to accept any signature. - A scaffolded app could not migrate its database or build its image
(REL-01b). Neither scaffold declared
default-run, so all nine CLI wrappers that shell out tocargo runfailed on a fresh project. The generated Dockerfile had five independent defects - a missing lockfile COPY,npm ciwithout a lock, a cache stage stubbing one of two declared binaries, a frontend build copied from a path vite never creates, and a missingfrontend/src/pagescopy thatinertia_response!validates at compile time. A stock scaffold's image could not build. docker:initemitted one Dockerfile for every project type. On an--apiproject its first instruction,COPY frontend/package.json, failed outright. API projects now get a frontend-free Dockerfile.- SQL placeholders (DATA-01). Rendered per backend rather than assuming one dialect.
- Queue settlement (DATA-02a, P2-06c). Follow-ups settle before the reservation is acked, and a lock-release error no longer converts an already-succeeded job into a retry.
- A cancelled batch fired
Catch, neverThen. Builder::clonesilently dropped the eager-load plan (P2-09a).User::query().with("posts")cloned anywhere - pagination,count(), any scope that clones - returned rows with no relations and no error.- Presence rosters lost members (P2-08). The roster was snapshotted before subscribing, so anyone joining in that window appeared in neither, permanently.
- Pinecone serialised every index acquisition (P2-14). The write lock
was held across two network round trips, and
tokio's fairRwLockmeant one cold index stalled every warm one. - The type watcher discarded bursts (P2-13). Leading-edge debounce regenerated on the first file of a burst and dropped the rest with no trailing run, so the last save never took effect.
ssr:checkcould hang, and tried one address (P2-13). DNS ran outside the timeout entirely, and only the first resolved address was tried - so a host with an AAAA record and no IPv6 route reported the worker down while it was listening on v4.suprnova serveinstalledcargo-watchunpinned (P2-13). Now--lockedwith a major-version bound.- The release bumper rewrote five READMEs and nothing else. Four manual chapters and a public doc comment pinned tags that no release ever updated - the doc comment was two releases stale. Discovery now replaces the hand-maintained list, and the smoke test greps the bumped tree independently rather than trusting the bumper's own verify step.
db:synctreated the database schema as trusted input (CLI-01).migrate:freshis gated behind--forceplus a typed confirmation (CLI-02), in the app binary as well as the CLI.- The
logmail driver now logs the whole message, as Laravel does, and no longer writes bearer links to the log in production.
Added
- Atomic terminal settlement (
QueueDriver::settle, DATA-02). The chain successor and the acknowledgement now commit together onDatabaseQueueDriver, closing the window where a crash between them either lost the rest of a chain or ran its next step twice. The reservation-keyed delete doubles as a fence: a worker whose visibility expired mid-run commits nothing and reportsSettled::Stale, so it cannot enqueue work for a message another consumer now owns. Drivers that cannot do this answerSettled::Unsupportedand keep the documented push-before-ack ordering. DatabaseBatchRepository(DATA-02). Batch accounting survives a restart, andpending_jobs/failed_jobsare derived from settlement rows keyed(batch_id, job_id)rather than stored and decremented - so a redelivered job cannot drive a batch to "finished" while its other jobs are still running, and the guard holds across processes rather than within one./_suprnova/health/liveand/_suprnova/health/ready. Liveness touches nothing; readiness probes dependencies. Wiring a database check into a liveness probe turns a database blip into a rolling restart of every replica, which the single previous endpoint invited./_suprnova/healthkeeps working exactly as documented.SERVER_HEALTH_READINESS_TOKEN. Optional shared secret for the readiness probe, compared in constant time. Without it, readiness answers 404 - indistinguishable from an unrouted path, because it is the router's own 404. Unset by default so existing probes keep working.MAIL_SMTP_ENCRYPTION-starttls|tls|none, withsslandnullaccepted as Laravel-compatible aliases. Unset derives from the credentials, reproducing the previous behaviour exactly. This also makes implicit TLS on port 465 reachable: the transport supported it, but no combination of environment variables could select it.SERVER_MAX_CONNECTIONSandSERVER_HEADER_READ_TIMEOUTdocumented inmanual/env-vars.md, where they had been missing entirely.
Changed
The audit's own conclusion was that the gate passed in 470s and caught none of the 19 P1s. Most of this release's test work is aimed at that.
- Postgres runs in the gate. Twelve tests across six files had never
executed. Two of them turned out to aim
DROP TABLEat whatever Postgres was onlocalhost:5432by default, and neither had ever initialisedCrypt, so both failed the first time they ran. - Scaffold assertions read the bytes a user receives, after
substitution, rather than the template source. Found an API project
shipping a doc comment naming a database literally
{package_name}, and a.env.exampleadvertising five mail keys the framework never reads. - Queue fault injection. ACK loss, redelivery, lease lapse and partial dispatch are driven by a decorator that fails a named operation on a named call, so every case is deterministic rather than a sleep race.
- Payment adapters have negative tests. Stripe's
verify()had never been exercised with a valid signature, so every rejection path that depends on reaching the HMAC comparison was unproven. - The Pinecone driver speaks REST. Breaking, behind the
off-by-default
vector-pineconefeature. Motivation is under Security; the surface changes are:client()is gone - there is noPineconeClientany more. Replacing it arecontrol_plane_get,control_plane_postanddata_plane_post, which reach any Pinecone endpoint with your own request and response types over the driver's authenticated, host-resolved transport. That is strictly more reach than the old trapdoor had.json_to_metadata→metadata_from_json, and metadata is nowserde_json::Maprather thanprost_types::Struct.decode_match_fields→decode_match, taking aPineconeMatch.namespace()returns&str.- New:
with_control_plane,with_api_version,with_index_host(pins a known host and skips the control-plane round trip),index_host, and thePineconeVector/PineconeMatchwire types. from_envstill readsPINECONE_API_KEYandPINECONE_CONTROLLER_HOST, and now alsoPINECONE_API_VERSION.- The REST API version is pinned, not floated -
2025-04, the version the driver's request and response shapes were written against. - Nothing serializes any more. The old driver cached one
Indexper name behind atokio::Mutexbecausepinecone-sdkexposed it only behind&mut self; the new one caches a host string and sharesreqwest's connection pool. - A host learned from the control plane is always contacted over
https, whatever scheme the response carries. Debugis implemented by hand with the API key redacted, so a#[derive(Debug)]on a struct holding a driver can't print it.
- Wire-contract tests for Pinecone. The live integration tests need a
PINECONE_API_KEYand so cannot run in the gate - which left a REST rewrite's field names (topK,includeMetadata,vectorCount) resting on nothing. Thirteen tests now drive the driver against a localwiremockfake and assert the exact method, path, headers and JSON body it puts on the wire, plus that a non-2xx is never decoded as a result and that an error message never carries the API key. They pin the driver to Pinecone's documented contract; only the#[ignore]d tests can confirm the documentation matches the live service.
0.7.2 - 2026-07-28
Fixed
generate-typesresolves nested prop structs without derives. 0.7.1's generator degraded any prop field whose type didn't deriveInertiaProps/Datatounknown- so re-running the generator (or thesuprnova servewatcher) over a project with a committed types file replaced real interfaces likeArray<AdminArticleRow>withunknownand broke type-checking across the app. Plain structs defined anywhere insrc/now resolve to their real interfaces, transitively from the prop roots;unknown(with a warning) is reserved for types the project genuinely doesn't define - external crate types, enums, tuple structs.
Changed
-
routes.tsgeneration is opt-in.generate-typesno longer dropsfrontend/src/types/routes.tsinto every project unasked; pass--routesto generate it. -
Frontend starter dependencies refreshed. New scaffolds from
suprnova newnow pin current versions: Vite ^8.1.5, Tailwind CSS ^4.3.3, Svelte ^5.56.8 (vite-plugin-svelte ^7.2.0, svelte-check ^4.7.4), React ^19.2.8 (plugin-react ^6.0.4), Vue ^3.5.40 (plugin-vue ^6.0.8, vue-tsc ^3.3.8), and@types/node^24 (the Node 24 LTS types line). TypeScript stays at ^6.0.3 deliberately: it is the latest 6.x, and svelte-check's peer range (^5 || ^6) does not yet admit TypeScript 7. All three starters were verified end to end (npm install+npm run build) against the refreshed set.
0.7.1 - 2026-07-27
A defect-fix pass over 0.7.0's queue routing, from a full post-release review.
Fixed
-
Chained jobs no longer lose their declared queue.
ChainLinkcaptured a job'smax_tries,timeout, andbackoffat chain-build time but not itsJob::queue(), so a job that landed on its declared queue when pushed directly landed ondefaultwhen dispatched as part of a chain - the "job" tier of the route → job → default resolution order silently vanished for chains. The declared queue is now captured on the link and resolved exactly like a direct push. Chain payloads written before this release decode unchanged (serde(default)), and a link with no declared queue serializes byte-identically to what 0.7.0 wrote. -
Failed-job records carry the queue the job died on. The worker's dead-letter path hardcoded
queue = "default"into everyFailedJobrecord, so failures of a routed job were invisible to an operator filtering the failed store by the pool that owns them. The record now carries the envelope's queue (defaultfor unrouted jobs). -
The 0.7.0 upgrade note understated the
jobsmigration. It read "unfiltered workers are unaffected and need no migration", butDatabaseQueueDriver::pushnames thequeuecolumn in itsINSERTwhether or not the job is routed - a 0.7.0 binary against an un-migrated table fails every push, filtered or not. The 0.7.0 section below andmanual/queues.mdare corrected: on the database driver theALTER TABLEis required for every deployment, and it must run before binaries roll (older binaries list their columns explicitly, so migrating first is safe). -
README no longer advertises a
#[job]macro. No such macro exists - jobs implement theJobtrait. The queues row now describes the real surface, including 0.7.0's queue routing.
Changed
- The release path now bumps README version references.
bump-workspace-version.pyrewrites the README's pinned install tag, the distribution-model example, and the MSRV line atomically with the manifests, and a reworded README that stops matching a pattern fails the release loudly. The README had advertised v0.6.0 since v0.7.0 shipped because nothing in the release path touched it. - Connection routing is documented as name-resolution only.
Job::connection()and the connection field ofQueue::routeresolve the connection name carried on theJobQueueing/JobQueuedlifecycle events; a single process-global driver still receives every push, so they do not select a different driver. The rustdoc andmanual/queues.mdpreviously implied driver selection that does not exist. The queue dimension is unaffected - it is honored end to end. Per-connection drivers remain future work. ChainLinkgained a publicqueue: Option<String>field, which breaks struct-literal construction of chain links. Links built throughChainLink::from_job- the normal path - are unaffected.
Upgrading
Coming from ≤ 0.6.x on the database queue driver, apply the 0.7.0 migration
below before rolling binaries; it is required for every deployment on
that driver, not just ones using --queue. 0.7.1 itself needs no migration.
0.7.0 - 2026-07-26
Security
- Upgraded
ammoniato 4.1.4 (RUSTSEC-2026-0213). Versions through 4.1.3 allow XSS via SVGanimateandsetanimation tags.ammoniais the sanitizer at the end of Suprnova's markdown pipeline (comrak→syntect→ammonia), so any app rendering user-supplied Markdown throughcontentwas exposed. The advisory was published 2026-07-21 - after v0.6.5 shipped - so every release up to and including v0.6.5 is affected. Upgrading the framework is the fix; no application code changes are required.
Added
- Queue routing. Jobs can be dispatched to a specific queue and connection,
and workers can be dedicated to specific queues - the Laravel 13
Queue::route(...)surface, typed. A job states its own home withJob::queue()/Job::connection(); an operator overrides it centrally withQueue::route::<SendInvoice>(Some("redis"), Some("billing"))inbootstrap::register(), without editing the job. Resolution is route, then job, then global default, and aNonefield in a route defers rather than clearing.queue:work --queue=billing,defaultdrains only those queues. Unrouted jobs belong todefault, so they are never stranded. Chained jobs resolve routes by name, since a chain link stores its job erased. QueueDriver::pop_from. Filtering pop, with a default implementation that rejects a filter it cannot honor rather than silently draining every queue - a worker told to drainbillingthat quietly drains everything is indistinguishable from a working deployment until the wrong pool eats the wrong jobs. The memory and database drivers filter natively. Custom drivers keep compiling and inherit the loud default.- Documented the
jobstable schema.manual/queues.mdnow carries the DDLDatabaseQueueDriveractually expects, which was previously only discoverable by reading the driver's SQL. - Documented Inertia's
serverHeadoption. Server-driven<head>elements (Inertia 3.5.0) need no framework support: the client reads them from an ordinary prop, so any handler can already supply them. Seemanual/frontend-inertia-responses.md.
Changed
Envelopegained aqueue: Option<String>field. It isserde(default)and skipped when absent, so an unrouted envelope serializes byte-identically to what previous versions wrote - the frozen wire-format test passes unchanged, there is noschema_versionbump, and mixed-version fleets interoperate during a rolling upgrade.WorkerConfiggained aqueues: Vec<String>field (empty = drain everything, the previous behaviour).- Removed
ROADMAP.md. Its design principles live inmanual/introduction.md, the working agreement inmanual/contributions.md, and the deployment and scale-out material inmanual/deployment.md; the shipped/planned checklists had gone stale.README.md's pointer to it for "the relationship to upstream" was already dangling - that attribution lives inLICENSE. - Scaffold frontends now pin
@inertiajs/{svelte,react,vue3}at^3.6.1(from^3.4.0). The 3.4.0 → 3.6.1 range is client-side only - audited against the upstream changelog and thePagecontract inpackages/core/src/types.ts, everyX-Inertia-*header the 3.6.1 client sends was already handled. scripts/release.shnow publishes the GitHub release itself, with notes taken from the version'sCHANGELOG.mdsection. Previously this was a manual "next step" that got skipped, which is why v0.5.10 and v0.6.1-v0.6.3 are tag-only and the Releases page sat on a stale version. Preflight runs before the gate so a missingghor changelog section fails in seconds, and publishing is skipped automatically unlessoriginis GitHub.
Upgrading
Existing jobs tables on the database queue driver must add the new
column - push names it in its INSERT whether or not the job is routed, so
an un-migrated table fails every push. Migrate first, then roll binaries
(older binaries list their columns explicitly and ignore the new one, so that
order is safe):
jobs ADD COLUMN queue TEXT NULL;
ON jobs(queue);
(Corrected in 0.7.1 - this note originally claimed unfiltered deployments needed no migration.)
0.6.5 - 2026-07-21
Added
- Hosted one-off Checkout in the Stripe adapter.
Checkout::start_sessionwithSessionMode::OneOffand non-emptyprice_refsnow creates a hosted Checkout Session (mode=payment, one line item per price ref,allow_promotion_codes=true) and returnsSessionPayload::StripeCheckoutRedirect. Theamount_hint-only Elements path is unchanged; the two shapes are picked per request. - Stripe Managed Payments (merchant-of-record) support.
StripeProvider::with_managed_payments(true)- orSTRIPE_MANAGED_PAYMENTS=trueinfrom_env()- sendsmanaged_payments[enabled]=trueon hosted one-off session creation. Off by default; the field is omitted entirely so non-enrolled accounts are unaffected. Checkout::session_status. New trait method (default:PaymentError::NotSupported) reporting a session's provider-side state as the new neutralCheckoutSessionState(Open/Complete { paid, payment_ref, amount_total }/Expired). The Stripe impl mapsGET /v1/checkout/sessions/{id};payment_refcarries the session's PaymentIntent id for mirror-table correlation. This is the server-side verification primitive for redirect return pages and reconciliation sweeps.Promotionscapability trait.create_promotion_codemints a customer-restricted, optionally expiring, redemption-capped code off a pre-created coupon. Queried via the newPaymentProvider::as_promotions()(defaultNone). Implemented for Stripe (POST /v1/promotion_codes) and the mock.MockPaymentProviderupgrades for the above. Records everystart_sessionrequest (recorded_sessions()), scriptssession_statusper session id (script_session_status()- unscripted known sessions reportOpen, unknown idsNotFound), and implementsPromotionswith recorded requests (recorded_promotion_requests()).
0.6.4 - 2026-07-17
Fixed
- Eloquent aggregates decode consistently across database backends. Generated
count,sum,avg,min, andmaxexpressions now use one stable internal result alias. PostgreSQL no longer returns false zeroes orNonebecause its driver labels aggregate columns differently from SQLite, and missing-column or incompatible-type errors now propagate instead of being silently defaulted. - Mass deletes cannot use caller-supplied table expressions. Executable
delete SQL always derives its target from the model's validated static
M::TABLE. The legacy public renderer argument remains source-compatible but cannot redirect or inject the delete target.
0.6.3 - 2026-07-15
Added
- Typed raw reads can stay on a transaction's pinned connection.
Transaction::backend()exposes the active backend andTransaction::query_all(Statement)executes typed aggregate or custom SQL through the transaction while preservingQueryExecutedinstrumentation. Applications no longer need a pool-level query or private executor access when a lock-scoped decision depends on computed result columns.
0.6.2 - 2026-07-15
Fixed
- Bound raw predicates are backend-neutral. Eloquent
filter_rawandwhere_rawnow accept portable?bind markers on every database backend; PostgreSQL rendering rebases them to monotonic$Npositions across prior predicates, relationship subqueries, HAVING clauses, and UNION arms. Existing numbered PostgreSQL fragments are normalized by their local marker order, while mixed styles and bind-count mismatches fail validation before I/O. The SQL-aware scanner preserves question marks inside quoted strings, identifiers, comments, and dollar-quoted bodies;??emits a literal question-mark operator in a bound raw fragment.
0.6.1 - 2026-07-15
Added
- Observable supervised session cleanup.
SessionMiddleware::installuses the configurableSESSION_GC_INTERVALcadence (one hour by default), whilesession_gc_metrics()exposes process-local run, success, failure, removed-row, and last-result timestamps for protected operations surfaces. - Bounded sliding-session touches.
SESSION_TOUCH_INTERVALcontrols the minimum activity-write cadence (five minutes by default) and is capped at half the session lifetime so active sessions cannot expire between touches.
Fixed
- State-free requests no longer create durable sessions. Requests without a valid session cookie perform no session-store read or write and receive no session cookie unless handling creates state. Existing clean sessions avoid unconditional upserts and cookie churn, legacy cookies migrate on their next request, and cookies whose backing rows have expired are cleared without recreating empty sessions.
0.6.0 - 2026-07-10
Added
- Opt-in framework subsystems with backward-compatible defaults. Filesystem
storage, SQLite/Postgres/MySQL database drivers, the MariaDB vector driver,
and Web Push now have explicit Cargo features. Existing default builds retain
all of these capabilities, while
default-features = falseconsumers can select zero drivers or only the storage/database/vector/push surface they use. The executable feature matrix verifies zero-driver, individual-driver, Nation X minimal, default, and all-feature profiles. - Raw P-256 VAPID private-key import.
VapidKey::from_bytesaccepts a validated 32-byte big-endian P-256 scalar alongside the existing PKCS#8 PEM import/export path.
Changed
- VAPID JWTs are signed directly with P-256. Web Push now serializes the
RFC 8292 ES256 header/claims and signs them with
p256, removing the generic JWT dependency while preserving generated keys, PEM round trips, public-key encoding, and the 24-hour lifetime bound. - Security dependency refresh. Updated vulnerable framework dependencies, including bcrypt and ammonia, and narrowed Comrak's enabled features while retaining syntax highlighting.
- Rust 1.91.1 is the release MSRV. Every workspace package declares the
same
rust-version, generated Dockerfiles pin the matching builder image, and the full release gate compiles the supported filesystem profile with the exact Rust 1.91.1 toolchain. - OpenDAL 0.58 security pin. The filesystem feature pins
eas4ai/opendalcommit88717391eb72c9839d3f8e79fccad9f22fc3a1b4, a minimal fork based exactly on official Apache OpenDAL commitae99a3b016e354a1b2bb2baf0c70f9f9e134970a. The fork changes only the Reqsign declarations used by OpenDAL core plus S3, GCS, and Azure Blob so downstream consumers resolve official Apache Reqsign commitb49cd2996b9d2d9944e84481f8835ff55b188b97andquick-xml0.41.0. A fork is required because a dependency repository's root Cargo patches do not propagate to consumers; the published graph could otherwise restore vulnerablequick-xml0.38/0.40.
Fixed
- Atomic release version metadata. The release bump now updates
workspace.package.versionand every versioned internal path dependency in one validated operation, stages every affected manifest, and proves a temporary0.6.0workspace withcargo check --workspacebefore release. Release versions are validated as strict SemVer 2.0, including the numeric prerelease leading-zero rule. Version-agnostic disposable bare-remote smokes derive a later patch release from both the current source and an already0.6.0source, reject staged/unstaged/untracked release trees before the gate, prove atomic commit/tag publication rolls both refs back when a tag is rejected, and prove the normal release sequence without touching the real remote. Release versions must increase by SemVer precedence, including prerelease transitions. Smoke build artifacts always stay inside their temporary workspace, ignoring any callerCARGO_TARGET_DIR. - Rustdoc covers every supported feature boundary. The OAuth module links
to public
OAuthAuth::complete, and the executable matrix builds zero-driver, default, and all-feature rustdoc with no dependencies. - Filesystem stream validation is session-scoped. Local filesystem writers, listers, and copiers resolve and confine their paths once before first I/O instead of once per chunk/item, while activated close/abort operations always reach the backend for cleanup. Existing traversal and symlink confinement remain enforced for a trusted filesystem; canonicalize-then-open checks do not eliminate races against a principal concurrently mutating the tree.
Security
- The release gate fails closed.
release.shdelegates to the canonical full gate before editing manifests or creating commits/tags; that gate always runscargo audit, treats a missingcargo-auditbinary as an error, and stops on any audit failure. It also builds and audits an isolated downstream filesystem consumer, asserting exact OpenDAL/Reqsign source revisions and noquick-xmlbelow 0.41. No new advisory ignores were added.
0.5.10 - 2026-07-03
Fixed
generate-typesno longer drops self-referencing structs. A struct with a field that references its own type (a tree node withchildren: Vec<Self>, e.g. a threaded-comment view) created a self-edge in the type-dependency graph, pinning its in-degree above zero so Kahn's topological sort never emitted it - leaving every interface that referenced it with a dangling type name that failedsvelte-check/tsc. Self-edges are now stripped before sorting, and any structs trapped in a reference cycle (mutual recursion) are emitted in arbitrary order rather than dropped, since TS interfaces may reference one another regardless of declaration order.
0.5.9 - 2026-07-01
Added
MAIL_FROM_NAME- optional display name on auth-flow emails. The email-verification, password-reset, and password-changed mailables now render theirFromheader as"Name <address>"whenMAIL_FROM_NAMEis set (read at send time so it survives the queue's serde round-trip).MAIL_FROMstays a bare address; leavingMAIL_FROM_NAMEunset or blank keeps the previous bare-address behavior. No change to any call site - the mailables read the env var themselves.
0.5.8 - 2026-06-30
Fixed
generate-typesroute helpers are always valid TypeScript. When several routes in a module share one handler (e.g. astatic_files::servewhitelist mapping many favicon/asset URLs), the first kept the handler name and the rest got a key derived from the route path - but the path was only partly sanitized (/ { } -→_), so a file extension leaked a.into the key:favicon_16x16.png: (...) => .... That is member access, not a property name, sotsc/svelte-checkrejected the generatedroutes.ts. Derived keys are now sanitized to legal identifiers - every non-alphanumeric character becomes_and a leading digit is prefixed - sofavicon-16x16.png→favicon_16x16_pngand2fa.json→_2fa_json. Unique handler names are untouched.
0.5.7 - 2026-06-30
Fixed
generate-typesno longer emits dangling type references. A prop field whose type is a struct that doesn't deriveInertiaProps/Data(or an external type the generator can't see) was emitted as a bare identifier - e.g.user: UserInfo- producing TypeScript that failstsc/svelte-checkbecause that interface is never written. Such references now degrade tounknown(user: unknown;Vec<T>→Array<unknown>;Option<T>→unknown | null), so generated output always type-checks, andgenerate-typesprints a warning naming the unresolved type and the field that references it, with the fix (deriveInertiaProps/Dataon it). Generic parameters and resolved nested InertiaProps/Data types are unaffected.
0.5.6 - 2026-06-29
Changed
- Sign in with Apple: RS256 JWKS verification. Bump
suprnova-apple-rsto v0.3.1 - Apple ID tokens are now verified against Apple's published JWKS (RS256) instead of being trusted structurally.
0.5.5 - 2026-06-28
Added
MagicLinktoken purpose. NewMagicLinkvariant on the auth-flowTokenPurposeenum, for passwordless magic-link sign-in tokens.
0.5.4 - 2026-06-28
Changed
- Composable OAuth completion. Split the generic OAuth completion into
verify_oauth_identity(verify + resolve the identity) and a thincomplete, so apps can verify an OAuth identity without triggering the full session-completion side effects.
0.5.3 - 2026-06-28
Fixed
- Correct workspace version metadata. v0.5.2 was tagged and pushed before
its
Cargo.tomlversion bump was staged, so the pushed v0.5.2 tag still readsversion = "0.5.1". v0.5.3 re-cuts the release with the correct workspace version - no code change (the v0.5.2 OAuth split is unaffected).
0.5.2 - 2026-06-28
Changed
- Composable Apple completion. Split Apple Sign-In completion into
verify_apple_identity+ a thincomplete_apple, mirroring the generic OAuth split. (Note: the pushed v0.5.2 tag carries a stale0.5.1version field - fixed in v0.5.3.)
0.5.1 - 2026-06-28
Changed
- Renamed Apple crate. Repoint the Apple dependency to the renamed
suprnova-apple-rsrepository.
0.5.0 - 2026-06-28
Added
- Sign in with Apple. OAuth token exchange + ID-token verification + user
upsert for Apple; Apple well-known endpoints and the
form_postresponse mode; Apple-specific fields onOAuthProviderConfig;AppleKeyPairre-exported so apps configure Apple Sign-In without a directappledependency.
Fixed
- Omit PKCE parameters from the Apple authorize URL (Apple rejects the request when they are present).
Dependencies
- Consume the
toriimagic-auth fix; addapple-rsv0.3.0.
0.4.1 - 2026-06-26
Performance
- Pre-size
MiddlewareChainto eliminate per-requestVecreallocations.
Fixed
- Make the maintenance down-file path collision-proof under parallel test runs.
Docs
- Compile-check the framework's doc examples (
ignore→no_run); reconcile the distribution notes with the tagged GitHub Releases; ignore the wholedocs/tree.
0.4.0 - 2026-06-22
Changed
- Distribution is git-tracked; you don't pin to tags. Scaffolded apps
depend on
suprnova = { git = "…/suprnova.git" }and track the default branch; pull updates withcargo update -p suprnova. Versions are published as tagged GitHub Releases (v0.4.0, …) for the changelog, butCargo.lockalready pins the exact resolved commit - so builds stay reproducible without hand-pinning atagorrev. The installation docs no longer present commit-pinning as the update path.
0.3.0 - 2026-06-21
Added
- Query instrumentation for Eloquent reads -
Builder::get,Model::find,find_many, andallnow emitQueryExecuted, so model SELECTs and eager-load queries surface inDB::listenand the in-memory query log alongside writes and raw queries. Adds the instrumentedExecutorChoice::statement_allread terminal. - Resource-route authorization -
ResourceRoutes::authorize_resource::<U, R>()attaches the conventional ability check to every generated resource route as per-route middleware (LaravelauthorizeResourceparity). The action→ability map isindex/show→view,create/store→create,edit/update→update,destroy→delete. One call gates the whole seven-action surface instead of relying on every controller body to remember aGate::authorize. - Atomic rate-limit hit -
RateLimiter::hit_and_check(key, max, decay)increments a fixed window and tests it in a single round-trip, returning whether the bucket is now over its limit (i64::MAXmeans unlimited). - Constant-time comparison helper -
constant_time_eq(a, b)(subtle-backed) for webhook signature verification;WebhookHandler::verifydocs now mandate constant-time digest comparison. - Inertia client to 3.4.0 - the Svelte/React/Vue scaffolds now pin
@inertiajs/{svelte,react,vue3}at^3.4.0(from3.1.1), picking uprouter.pollmodes, dynamicusePoll,Inertia.once, the InfiniteScroll cancel fix, and awaited FormonSuccess. The server already emits the full 3.4.0 page-object and header surface (once-props, the prepend/deep-merge scroll family,matchPropsOn, rescued/shared props), so this is a client-currency bump with no protocol change. - Optional connection cap -
SERVER_MAX_CONNECTIONS(and the programmaticServer::max_connections(n)) bounds concurrently active connections with a semaphore on the accept loop, applying back-pressure at the TCP level. Unset - or0- leaves connections unbounded (the default, unchanged). A backstop to pair with a reverse proxy andLimitNOFILE, not a replacement for upstream rate limiting. - Opt out of redirect-following -
RequestBuilder::no_redirects()routes a request through a non-following HTTP client so a3xxis returned as-is instead of chased. Use it when the request URL is influenced by untrusted input, to close a redirect-based SSRF vector (a hostile endpoint redirecting toward an internal or cloud-metadata host). The default client still follows redirects, matching general-client convention.
Security
- Resource routes fail closed on the authorization registry's type-erased
downcast instead of panicking, and
authorize_resourcedenials / unauthenticated requests are refused before the handler runs. - Rate limiter closes a fixed-window check-then-hit race by incrementing and
comparing atomically (
hit_and_check). - Queue
RateLimitedmiddleware now admits jobs through that atomichit_and_checkinstead of a separatetoo_many_attempts+hitpair, so concurrent workers can no longer all pass the budget check before any of them increments and over-admit pastmax_attempts. - Upload validators (
mimetypes/mime) content-sniff the uploaded bytes instead of trusting the client-suppliedContent-Type. - Filesystem path guard canonicalizes paths to catch symlink traversal out
of the storage root, beyond the prior lexical
..// absolute / UNC checks. - Auth closes a passwordless-login timing oracle - a matched-but-passwordless
account given a password now runs a fixed-cost verify, across both the Eloquent
and database user providers - and
dummy_verifydrives the configured hasher so the unmatched-user path is constant-time. - Eloquent validates column identifiers on the
pluck/value/pluck_keyed/sole_valueandsum/avg/min/maxprojection paths. - Payments - the mock provider's verifier fails closed outside a development
environment, and webhook source IPs resolve through
TrustedProxiesConfig(req.ip()) rather than a rawX-Forwarded-Forheader. - Filesystem path guard now walks to the nearest existing ancestor when a write target doesn't exist yet, closing a symlink escape where a planted intermediate symlink with a missing immediate parent slipped past the guard.
DB::init_withvalidates the environment before connecting (matchingDB::init), so the dev SQLite fallback can no longer boot silently in production through that entry point.- Static-file serving rejects dotfiles (
.env,.git/config,.htpasswd, any leading-.segment), not just./..traversal. - Payment webhooks serialize concurrent retries of the same unprocessed
event with a
FOR UPDATElock + re-check, and treat mirror-table unique violations as benign already-applied;payments_subscription_itemsgains aUNIQUE(subscription_id, provider_item_id). - RBAC defaults the model discriminator to the fully-qualified type name, so two authenticatable types sharing a leaf name can no longer inherit each other's roles/permissions.
invalidate_session()rotates the session id (not just flushes), closing a session-fixation gap; the queueWithoutOverlappingmiddleware releases its cache lock even when the job panics.- Mail providers cap error-response body reads (8 KiB), matching the web-push client, so a hostile endpoint can't drive sender memory.
- Web push disables HTTP redirect-following on the default client, so an
attacker-influenced push endpoint can no longer
3xx-redirect a notification POST toward an internal or cloud-metadata host (SSRF). A redirect now surfaces as a rejected push rather than a silently followed request. - Stripe adapter
Debugredacts the webhook signing secret and prints a placeholder for thestripe::Client(which carries the API secret key in its auth header), so neither secret can reach logs through a{:?}ofStripeProvider, regardless of the upstream client's ownDebug. - Stripe adapter
from_envrejects present-but-blank credentials, failing closed instead of constructing a client with an empty (and therefore forgeable) webhook HMAC secret. - OAuth email verification fails closed for unrecognised providers: a
userinfo payload carrying an
emailbut noemail_verifiedflag is no longer treated as verified. An unknown provider must now assertemail_verified: trueor expose a verified-emails endpoint, closing an account-link/takeover vector for apps that key accounts on email. Google (explicit-true-only) and GitHub (verified-by-the-/user-contract) are unchanged.
Fixed
- Nested eager loading (
with(["posts.comments"])) is now a constant number of queries - the tail segment loads in one batched IN query across all parents instead of one query per parent (N+1). where_has/where_doesnt_havequalify closure columns with the target table, so a column present on both pivot and target no longer produces an ambiguous-column error on many-to-many relations.- Soft-delete
delete/force_delete/touchand factorypersisthonor a model's#[model(connection = "…")]routing (matchingrestoreand the other write paths) instead of falling back to the primary pool. - JSON:API
Maybe::Missinguses a non-collidable wire sentinel, so user data shaped like{"__missing__": true}is no longer silently stripped. - Queued notifications honor
should_send(per-channel veto) andafter_sending, re-checked on the worker - previously only the synchronous path did. - Released jobs push the retry copy before acking the original, so a transient driver push error no longer drops the job.
- Paddle adjustment (refund) webhooks key the mirror update off the referenced
transaction id and read amounts from
data.totals, instead of inserting a zero-amount row under the adjustment id. - SQLite URLs carrying a query string (
sqlite://db.sqlite?mode=rwc) build a valid single-query connection URL and a clean on-disk filename. - HTTP clamps
Acceptq-values to[0,1]and enforces aFormRequest'smax_body_byteseven when the body was pre-buffered; WebSocket config rejectsmax_missed_pings < 2(1 closed every connection on its first ping). - Cron day-of-month and day-of-week use OR semantics when both are restricted
(Vixie/POSIX parity); Markdown
plain_text/excerpts preserve intentional spaced punctuation;CachedEvaluatorbounds its cache growth;SupervisorRegistry::start_allno longer double-spawns on a second call; the test container recovers in place from a poisoned lock. - Supervisor restart backoff resets to the 100 ms floor after a run that stays up at least the 60 s cap, so a daemon that ran healthily for a long stretch and then exits restarts promptly instead of inheriting backoff that climbed during an earlier failure burst. A crash loop whose runs never reach the threshold still ramps to the cap, so the reset never masks a flapping supervisor.
- Corrected stale docs on
filter_op(operators are allowlist-validated), signed URLs (not byte-compatible with Laravel's default absolute signatures),UniqueIdKind::is_valid(a caller helper, not auto-wired intofind), and the identifier length cap (128, not 64).
Documentation
- Documented resource-route authorization (
authorize_resource) in the routing and authorization chapters, and the atomichit_and_checkcounter in the rate-limiting chapter.
0.2.0 - 2026-06-21
Adds role-based access control, a Markdown content / docs-rendering pipeline, and native static-file serving.
Added
- Tier-2 RBAC -
HasRolestrait; roles + permissions with arole_has_permissionsjoin;PermissionMiddleware/RoleMiddleware(both fail-closed / default-deny); theCreateRbacTablesmigration; andcreate_role/create_permission/give_permission_to_rolehelpers. - Content rendering - Markdown rendering and a docs-build pipeline:
MarkdownRenderer,build_docs,DocsCatalog/DocsChapter, heading extraction andslugify_heading. Rendered HTML is sanitized (comrak + syntect + ammonia). - Native static-file serving -
StaticFiles::public()fallback handler for serving apublic/directory at the web root, replacing hand-rolled per-asset whitelist controllers in apps.
Fixed
- Freshly generated apps inherit a framework-level
time = 0.3.47compatibility pin, avoiding Rust 1.96 coherence conflicts fromtime 0.3.48in fresh scaffold dependency resolutions.
Documentation
- Documented the two shipped starter kits - Nebula (Breeze-tier auth) and Pulsar (product site + community) - across the manual, README, and roadmap; restructured the roadmap around the shipped surface; and reconciled version references throughout the docs.
0.1.0 - 2026-06-10
The initial Suprnova release. Suprnova is a Laravel-inspired web framework for Rust, forked from Kit and taken in its own direction. Today's parity target is Laravel 13.x.
This release uses the git distribution model: framework consumers depend
on suprnova = { git = "https://github.com/eas4ai/suprnova.git" },
and the CLI installs with cargo install --git.
Added
HTTP, routing, and middleware
Routerwith route groups, prefixes, parameter constraints, named routes- Compile-time-validated route registration via the
routes!macro - Resource routing (
Router::resource) producing the seven standard routes - Signed URLs (
url::signed_route/url::temporary_signed_routefree functions, plusRedirect::signed_route/Redirect::temporary_signed_route) - Redirect helpers -
Redirect::to,Redirect::back,Redirect::route,Redirect::with_input,Redirect::with_errors,with_flash - Middleware trait with global, group, and per-route layers
- Built-in middleware - CORS, CSRF, session, request timeout, request ID, throttle / login throttle, signed-URL verify, authenticated, email-verified, brute-force
- Abort helpers (
abort,abort_unless,abort_if) suprnova::handle_request(...)- public adapter to serve a single hyper request against a router + middleware chain
Inertia.js frontend bridge
#[derive(InertiaProps)]with TypeScript type emissioninertia_response!macro with compile-time component validation- Three first-class starter frontends - Svelte 5 (runes-on), React 19, Vue 3.5 - all on Inertia 3.1.1 + Vite 8 + Tailwind v4
- Partial reloads (
only/except), deferred props, persistent layout, encrypted history, scroll preservation Inertia::paginate(component, key, paginator)for paginator → Inertia prop wiring
Eloquent-style ORM (over SeaORM)
#[suprnova::model]attribute macro that emits a SeaORM entity and the user-facing Eloquent struct in one shot- Full
Modeltrait -create,find,find_or_fail,find_many,all,query,save,update,delete,force_delete,refresh,fresh,replicate,replicate_into,increment/decrement,destroy,is/is_not,to_array/to_json - Fillable / guarded mass-assignment with
Attrsenvelope - 22 attribute casts - booleans, integers, floats, dates, enums, hashed, encrypted, JSON, collections, money, datetime with timezone
- Accessors / mutators via
#[suprnova::model] - Auto-timestamps (
created_at,updated_at) - Soft deletes (
deleted_at) withforce_delete,restore,trashed,only_trashed,with_trashed - Eleven relation kinds -
HasOne,HasMany,BelongsTo,BelongsToMany,HasOneThrough,HasManyThrough,MorphOne,MorphMany,MorphTo,MorphToMany,MorphedByMany - Per-family morph enums + morph registry with
APP_KEY_PREVIOUSrotation - Eager loading via
.with(...),.with_count(...),.load_missing(...) - Correlated EXISTS engine for
has/where_has - Sixteen lifecycle events (retrieving, retrieved, creating, created, updating, updated, saving, saved, deleting, deleted, restoring, restored, force-deleting, force-deleted, replicating, trashed)
Observer<M>trait with per-method auto-registration via inventory- Local scopes via
#[scopes(M)], global scopes viaGlobalScope Collection<M>Laravel surface -pluck,key_by,group_by,where_in,first_where,contains_where,partition, etc.- Three paginators -
paginate(length-aware),simple_paginate,cursor_paginate- all serializing to Laravel-shape JSON chunk/lazy/cursorfor bulk-row iteration without OOMlock_for_update/shared_lockrow-level lockingDB::table(...)query builder withDynamicRowfor ad-hoc queriesDB::transaction(...)with savepoints, retry-on-deadlock, multi-connection read/write splitDB::listen(...)+QueryExecuted/TransactionBegan/TransactionCommitted/TransactionRolledBackeventsPrunabletrait +model:pruneconsole commanddump/ddquery-helper methods#[model(unique_id="...")]for UUID / ULID primary keys
Auth
Authenticatabletrait +EloquentUserProvider<M>Auth::attempt,Auth::login,Auth::user,Auth::user_or_fail,Auth::user_as<T>,Auth::logout,Auth::check- Multiple named guards (web session, API token)
- Email verification flow -
EmailVerification,EnsureEmailVerifiedMiddleware, signed verification URLs,EmailVerificationMail - Password reset flow -
PasswordReset, throttled tokens,PasswordChangedMail,PasswordResetLinkSentevent - Two-factor TOTP - enroll, verify, recovery codes, replay protection
- Brute-force / login throttle - IP + identifier keyed,
LoginThrottleMiddleware - Remember-me cookies with stable opaque tokens
- Six auth events -
LoginAttempted,LoggedIn,Authenticated,LoggedOut,PasswordResetLinkSent,EmailVerified - Browser sessions backed by the Torii fork at
github.com/eas4ai/suprnova-torii-rs
Authorization
Gatefacade -define,allows,denies,authorize,any,none,check(sync + async variants)#[policy(Model)]macro for policy registration- Resource-route auto-authorization
Payments
- Provider-agnostic five-trait surface -
Checkout,Payment,Subscription,CustomerStore,WebhookHandler PaymentProviderumbrella trait + capability-querying viaas_payment()- DB mirror -
customers,subscriptions,subscription_items,payments,refunds,payment_webhook_events(UNIQUE for idempotency) - Flow-tagged
SessionPayloadenum (one-shot vs subscription) - Two reference adapters as workspace crates -
suprnova-payments-stripe(gateway, fullPaymentimpl),suprnova-payments-paddle(Merchant of Record, noPaymentimpl) - Mock provider for tests
Queue, jobs, batches, chains
Jobtrait -handle,max_tries,backoff,timeout,fail_on_timeoutQueue::push,Queue::push_later,Queue::push_unique,Queue::push_unique_later- Drivers -
sync,null,redis,database JobMiddlewaretrait - six built-in middleware- Batches and chains -
Queue::batch(jobs).dispatch(), fluent chain builder, cancellation, progress tracking - Failed-jobs store with replay
- Worker with graceful shutdown, configurable concurrency, panic
recovery via
catch_unwind, settlement metrics - Twelve queue events covering queueing, processing, failure, release, worker lifecycle
Broadcasting and WebSockets
ws!()macro +Router::wsfor typed WebSocket endpointsWsSocketSink/Stream split- Auto-restart supervisors via
Supervisortrait BroadcastHubwithChannel,Private,Presencechannels- JSON-envelope protocol, presence join/leave/here, configurable presence TTL with crash recovery
Broadcastablebridge toEventDispatcher- Close-on-no-pong heartbeat with configurable WS_TASKS drain
- Per-route WebSocket middleware
- 1 MiB / 64 KiB safer defaults +
WsConfig::generous()factory - Origin policy + 1011 close-on-protocol-violation
Notifications and mail
Notificationtrait +Notify::send(recipient, notification).await- Mailable + Markdown template rendering
- Database / mail / broadcast / web-push channels
- VAPID signing + RFC 8291 ECE payload encryption (via
suprnova-web-push) - VAPID subject validation, retry-after parsing, 8 KiB rejection-body cap
- Notifiable trait for recipient typing
Events
- Typed event dispatcher -
EventFacade::dispatch,EventFacade::listen<E, L>,EventFacade::forget - Cancellable saving/updating events (return
EventResult::cancel) - Queueable listeners
Filesystem
Storage::disk("name")with multi-driver support - local, S3, Azure, GCS via OpenDAL- Move, copy, exists, size, mime, last-modified, prepend/append
- Streaming uploads and downloads
Cache
Cache::store("name")+ driver registration- Drivers - memory, redis (with bounded connect-timeout), database, file
remember,forever,tags, atomic increment/decrement, locks
Vector DB
VectorDrivertrait with four drivers - in-memory, Qdrant (UUID-5 ID mapping), Pinecone (native string IDs), MariaDB nativeVECTOR(N)+ HNSW indexes (11.7+)- Cosine / dot / euclidean distance
Console binary and CLI
- Per-project
consolebinary - Rust analogue ofphp artisan, runs user-defined commands via#[suprnova::console::command] #[derive(Command)]for typed argumentssuprnovaCLI -new,serve,migrate,db:sync,generate-types,key:generate,make:{controller,middleware,action,error,inertia,migration,task,command},db:seed,model:prune--versionflag- Scaffold templates for backend + API starters across three frontends
Feature flags
DatabaseEvaluatorwith snapshot loadingCachedEvaluatorwith TTLFeatureMiddlewareextractor- Admin CRUD surface
FeatureSynctrait for sub-second propagation across processes
Schedule
- Cron expression parser
Schedule::task(...)with composable predicates- Single-server locks, overlap prevention, dispatch tracking
schedule:runconsole command
Validation
validator0.20 integration#[request]+#[derive(FormRequest)]macros#[form_request(max_body_bytes = N)]per-form size cap#[form_request(custom_hooks)]opt-out for user-writtenimpl FormRequest- Lifecycle hooks -
authorize,after_validation,after_validation_async
Database drivers
- SeaORM-backed support for SQLite, Postgres, MySQL, MariaDB
- URL-based driver detection
- Migration system +
migrate,migrate:rollback,migrate:status,migrate:fresh,migrate:refresh
HTTP client
Httpfacade -get/post/put/patch/deletereturning aRequestBuilder;.send().awaitproduces aClientResponse- rustls TLS, 30s default timeout,
suprnova/<version>user-agent json/form/body/header/bearer_token/basic_auth/timeoutchainable methodsRequestBuilder::retry(max_attempts, base_backoff)- exponential backoff for transient failures and 5xx; respectsRetry-AfterHttp::fake(|| async { ... }).awaittest guard withfake_response(method, url_substring, status, body)+assert_sent/assert_not_sent
Encryption
Cryptstatic facade +EncryptionKey(crypto::*); AES-256-GCM with 12-byte random noncesencrypt_string/decrypt_string/encrypt<T>/decrypt<T>CryptPurposeAAD binding preventing cross-protocol replayAPP_KEY_PREVIOUSrotationsuprnova key:generateCLI command for minting fresh keys
Testing
#[suprnova_test]async test macroTestDatabase::fresh::<Migrator>()with parallel-safe instancesTestContainer::bindfor per-test mocks- HTTP test helpers -
Test::get,Test::post, JSON / form / multipart - Queue / Mail / Notification / Event fakes
assert_emitted,assert_dispatched,assert_dispatched_times
Changed
- Auth verification and password-reset flows now operate through the configured user provider instead of Torii internals.
- Generated apps must implement
get_auth_password; scaffolded examples now fail loudly instead of allowing login to always fail silently. - The local release gate is wired into
scripts/release.sh, and the repo includes an enforced pre-push hook for fmt, clippy, tests, docs, and feature builds. - Scaffolded dev-port documentation moved to the current backend/frontend
defaults (
8765/5765), withdev:tlsand--with-portlessdocumented. MAIL_FROMis validated before verification or reset tokens are issued, avoiding orphaned auth-flow rows when mail configuration is invalid.
Fixed
- React scaffold template drift from the released starter.
- Root route groups no longer generate duplicate
//paths. - Literal-path redirects now dispatch through the intended routing path.
- Broadcasting fanout tests now handle
track/untrackresults. - The mail log driver emits the rendered text body, so verification and password-reset links surface in local development logs.
- Password-reset coverage pins session and remember-me revocation behavior.
Notes
- Distribution model: git-based end-to-end.
suprnova = { git = "https://github.com/eas4ai/suprnova.git" }; CLI viacargo install --git. Nothing is published to crates.io.
