Self-hosted Supabase now defaults to Envoy instead of Kong
Supabase’s self-hosted stack now routes through Envoy by default, bringing new API-key support and hardened gateway defaults while breaking some Kong-specific assumptions.
Search
Search results for “PostgreSQL compatibility”
Find published research by company, product, platform or technology.
Showing 81–100 of 188 dossiers
GitHub’s OAuth apps get short-lived tokens, multiple callbacks — and a wildcard setting worth auditing
GitHub OAuth apps can now use eight-hour access tokens with rotating refresh tokens, register up to 10 callback URLs, and explicitly control wildcard callback matching. New apps default to expiring tokens, while existing single-callback apps should review a legacy wildcard setting GitHub has now made visible.
Amazon Aurora Serverless gets faster burst scaling
Aurora Serverless can now add roughly 12 ACUs in the first second of a scale-up event on platform versions 3 and 4. The change is automatic and is most useful for bursty SaaS, API, batch and agent workloads, but it does not remove the separate resume delay when a database has scaled all the way to zero.
Coolify 4.5.3 repairs access controls, deployment healthchecks and retry hazards after 4.5 launch
Coolify 4.5.2/3 add access-control fixes and correct deployment regressions introduced after 4.5.1. Operators should test healthchecks, API permissions and restores.
Web DevelopmentCloud & InfrastructureCloud PlatformsDeployment & DevOpsFrameworksDeveloper ToolsActive dossier
Cloudflare opens Void: a Vite SDK, CLI and self-hosted deployment platform
Void SDK adds server routes and typed data access to Vite, Void CLI provisions Workers resources, and Void Platform provides a controlled multi-user deployment surface. The convenience comes with Cloudflare runtime dependencies and real deployment limits.
Fly.io raises Machines RAM prices while nearly halving Sprites compute costs
Always-on RAM-heavy Fly Machines cost more from October, while bursty Sprites get much cheaper. CPU pricing for Machines and Managed Postgres plans stay unchanged.
Turso concurrent writes move from Cloud preview to a 0.8 engine release with new contention benchmarks
The new Turso 0.8 results add a concrete performance datapoint to the earlier MVCC preview, but benchmark workloads, transaction conflicts and production durability still require independent verification.
SaaSCloud & InfrastructureMarketing & DistributionHostingEmail & LifecycleSaaS OperationsActive dossier
Stalwart 1.0.1 fixes credential exposure and tenant isolation — 1.0 migration still needs care
Stalwart 1.0.1 fixes local credential-file permissions and a tenant isolation bug, but changes Prometheus/OTLP metrics and leaves some migration WebUI cache pitfalls.
Railway warns of possible decrypted customer secrets as builds recover in stages after security incident
Railway has not confirmed every customer was breached. Precautionary all-customer rotation guidance, revoked API tokens and deployment disruption make this actionable for builders.
InfluxDB’s Docker `latest` tag now jumps from v2 to v3 Core
This is not a normal container refresh. InfluxDB 3 is a ground-up architecture change with different query and storage assumptions, and Flux is not supported. Treating `latest` as a harmless moving patch tag can therefore turn an ordinary image pull into an unplanned database migration.
Python 3.15 makes lazy imports and UTF-8 defaults real — with a new profiler and free-threaded ABI
Python 3.15.1 supersedes the 3.15.0 launch with an urgent certificate-trust update. New installers alone do not update existing virtualenvs: update pip, uv and certifi where applicable.
Grafana Marketplace opens a paid plugin channel for specialist observability developers
At ObservabilityCON 2026, Grafana opened paid plugin distribution to verified partners. Cloud customers can trial and subscribe to integrations on their Grafana bill; partner maintenance and security requirements are part of the model.
Forgejo 17.0 expands self-hosted CI — but existing Actions webhooks need manual migration
The October 15 Forgejo 17.0 release strengthens self-hosted Git and CI workflows, but webhook receivers need a migration because the new workflow-run events change headers and payload semantics. The release is non-LTS.
Shopify has cut off legacy Theme CLI authentication for password-protected stores
Theme developers using Shopify CLI 3.83.x and older against password-protected storefronts are now past the documented cutoff. Shopify requires 3.84.0 or later for these flows; the live changelog's September 23 date supersedes the earlier October 1 deadline in this dossier.
Tor Browser 16.0 moves to Firefox ESR 153, adds Linux ARM64 and retires 32-bit x86
Tor Browser 16.0 makes the annual Firefox ESR migration real: Linux ARM64 reaches stable, 32-bit Linux support ends and privacy hardening comes with explicit accessibility trade-offs.
LaunchDarkly AgentControl now versions and deploys agent skills without application releases
Agent skills join prompts and models as managed runtime configurations; approvals and pinned versions make changing agent behaviour auditable rather than an untracked edit to skill files.
EDG opens its industrial C++ compiler front end under Apache 2.0 after three decades
The EDG front end moved from commercial licences to a public repository and C++ Alliance stewardship on September 30. A fresh October 20 statement confirms permissive commercial reuse, experienced maintainers and work still needed on reflection, coroutines and back ends.
Effect 4.0 rebuilds the TypeScript runtime around a zero-dependency core and LTS
Effect 4's performance and LTS claims remain, but 4.0.2 explicitly marks some formerly unlabelled APIs unstable without changing their current behavior, signatures or types.
Shopify Hydrogen 2026-10 goes GA as a framework-neutral commerce library
Hydrogen 2026-10 is generally available as a JavaScript commerce library with React Router and Next.js starters and examples for other frameworks. Existing Hydrogen storefronts still work; migration is optional.
Deno joins Cloudflare — Deno Deploy will shut down and runtime development will end
The Cloudflare move is a hard migration deadline for Deno Deploy users and a major maintenance change for Deno runtime adopters. JSR will continue, and self-hosted distributed Workers are still a future plan.