Inertia.js 3.9 fixes cached protected pages resurfacing after logout
Inertia.js 3.9 flushes prefetch entries when history is cleared, preventing a previously visited protected page from reappearing from client cache after logout.
Find published research by company, product, platform or technology.
Showing 261–280 of 597 dossiers
Inertia.js 3.9 flushes prefetch entries when history is cleared, preventing a previously visited protected page from reappearing from client cache after logout.
A six-month real-world comparison shows AI code-review agents and specialised fuzzers find substantially different V8 vulnerabilities. Replacing fuzzing with agents would leave gaps, and cost per bug remains unknown.
A new buyer survey connects the shift from SaaS seats to agent usage with real budget anxiety: 46% report higher-than-expected agent costs and 45% say oversight eats more than a quarter of expected productivity gains. Preferences are not purchasing outcomes.
Ahrefs tracked roughly 37,500 cited websites for 20 days and found high daily citation churn, frequent recoveries and major differences between AI tools.
New SaaS cohort data challenges the habit of waiting six months to pitch an upgrade. The strongest seat and plan expansion window is the first month, while year-one renewal creates a second chance; AI-native customers are more likely to reactivate after churn.
Builders can automate Stripe revenue and reconciliation analysis, but must plan for API permissions, asynchronous jobs, result retention and a February 2027 query-billing transition.
The previously pre-announced Next.js security release is now available. Teams on affected versions should upgrade to 16.3.3 or 15.5.24; the disclosed flaws can lead to unauthenticated remote code execution under specific image-optimization or Windows-hosting conditions.
The sharpest operational trap is CVE-2026-91768: PHP-FPM’s listen.allowed_clients can treat an allowed IPv6 address as an entire /96 prefix. Teams relying on that ACL should patch rather than assuming the configured address restriction is exact.
Google Analytics hostname allowlists reduce some ghost-traffic cleanup, but server-side Measurement Protocol events bypass the filter. Teams must distinguish browser collection from Measurement Protocol and test empty-hostname events.
The useful part is not the 800,000-line headline. GitHub has published unusually detailed receipts for a production-scale agent-assisted migration: roughly $120,000 of token spend, 14.5 weeks of incremental releases, dozens of regressions, extensive compatibility tests and a workload-specific jump from 7.55 to 120 session lifecycles per second.
Sentry has completed a breaking alerting migration. Legacy alert APIs are gone; metric detection now lives in Monitors while notification routing lives in Alerts, and old direct integrations must use the replacement endpoints.
GitHub AI Scan can now be managed at scale through REST settings for organizations and repositories, building on September's removal of its CodeQL default-setup dependency.
llama.cpp 1.0 removes 35 deprecated functions, adds FP8 KV caching and MoE expert caching, and restricts unauthenticated tools and private-address access. The new versioning promise helps downstream builders, but upgrading is not drop-in.
The first app is now a distribution prerequisite for the second: Shopify adds an adoption threshold and tighter App Store submission rules that especially affect small app portfolios.
Air in IDEs brings local and ACP-compatible agents, parallel sessions, presets and diff review into JetBrains 2026.3, with important provider and governance limits.
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 CVEs; operators must check indexes, backups and PostgreSQL 14 end of support.
Cloudflare Spend Management beta adds hard usage-blocking limits and alerts for Workers and Durable Objects; caps can interrupt apps and still allow overages.
WooCommerce is removing unnecessary block bootstrap work from non-rendering requests. The performance gain is concrete, but extension authors need to understand the new registration boundary rather than assuming Woo blocks are always initialized.
Render is reshaping Workflows economics as it reaches GA: most small and I/O-heavy tasks should get cheaper under Flex, while task-state retention becomes a new line item and fixed-size Pro tiers remain for heavier compute.
R2’s new `us` jurisdiction gives object-storage users an explicit US data-residency guarantee, with jurisdiction-specific S3 endpoints and Workers bindings. Existing unrestricted buckets cannot simply be flipped into the new jurisdiction because jurisdiction is immutable after creation.