Shipped · Databases

What get-convex/convex-backend shipped

The public repository of Convex · github.com/get-convex/convex-backend

Written by FoxPlug from the repository's own releases; not affiliated with Convex. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/get-convex/convex-backend; Convex did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for convex-backend, free

Week of November 2, 2026

What shipped

Why it matters

S3 exports stop accumulating every snapshot since the export began, so export metadata stays bounded instead of growing and being rewritten on each commit. Persistence index scan attribution and safer index cache registration give clearer measurements and fewer concurrency problems. The billing and usage pages gain clearer figures for included usage and estimated monthly spend.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: S3 export tables keep only their last 10 snapshots, persistence index scans are attributed to caller and index kind, index cache intervals register before insert, gzip ConfigDecoder added, and the usage page shows included usage from the ledger plus estimated monthly s

Post for LinkedIn

This week's changes: S3 export tables now keep their last 10 snapshots, so metadata.json no longer lists every snapshot since the export started and each commit reads and rewrites less. Persistence index scans are attributed to their caller and index kind. Index cache intervals are registered before inserting the entry, with the registration undone when an entry already exists, and a concurrent population test checks every registered interval. A gzip ConfigDecoder was added. The usage page now estimates monthly spend for active deployments and shows included usage from the ledger when it is not in the current billing period. MetricPrice generation no longer includes allocations.

Week of October 19, 2026

What shipped

Why it matters

This week's changes affect sync and export behavior on busy deployments and tighten how compromised certificates are handled in Node. The S3 export transaction change and the egress reporting make large exports more predictable to run and measure.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: a flag to distrust compromised eMudhra certificates in Node, a Node.js 22 Brotli mitigation fix, S3 export no longer holding a transaction across a page, Parquet bytes reported as egress, larger data sync batches, and npm 1.48.0.

Post for LinkedIn

This week's changes: a flag to distrust the compromised eMudhra certificates in Node, with the distrust reapplied after its revert; a fix for the Brotli mitigation on Node.js 22 in the node executor. The S3 export worker no longer holds a database transaction open while a page syncs, and S3 export reports Parquet bytes as egress. Data sync uses a larger batch size, AWS credentials are cached process-wide, and npm release 1.48.0 is out.

Week of October 12, 2026

What shipped

Why it matters

This week tightened deployment token security with a shorter JWT lifetime and a reserved claim, and fixed pagination so it can be repeated in mutations. CLI output is safer because env var values are redacted in verbose push output, and ai-files install and update now fail with a nonzero exit code. The bundle analyzer also gained explore, insights, and package and file details views.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New release 2026-10-10-72ce13c. Deployment JWT lifetime is now capped at 1 hour, jti is reserved in deployment JWTs, and database bandwidth usage can be aggregated. Pagination can repeat in mutations, verbose push output redacts env var values, and the bundle analyzer has explore

Post for LinkedIn

A new precompiled release, 2026-10-10-72ce13c, is out. Deployment JWT lifetime is now capped at 1 hour and the jti claim is reserved in deployment JWTs. Pagination can be repeated inside mutations, and the ai-files install and update commands now exit 1 on failure. Verbose push output redacts environment variable values. Usage tracking can aggregate database bandwidth events without a request id. The bundle analyzer adds explore, insights, and package and file details. IO errors from mysql are now classified.

Week of October 5, 2026

What shipped

Why it matters

This week's changes touch core data paths and the deploy experience. Aggregate database bandwidth events can now omit the request id, and S3 exports no longer fail when a sync page meets a Glue table that does not exist yet. The dashboard health page also shows schema validation and index backfill progress, so a deploy that is still validating or backfilling is visible. The ai-sdk-provider reached version 0.3.0 for stable voice support and opt-in ZDR routing, and transcription failures now retry on transient HTTP errors.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: aggregate database bandwidth events can omit the request id, missing Glue tables no longer break S3 exports, and the dashboard health page shows schema validation and index backfill progress during deploys. The ai-sdk-provider hit 0.3.0 with stable voice support and op

Post for LinkedIn

Here is what shipped this week. The database bandwidth aggregate now allows events covering multiple requests to omit the request id, while individual execution events keep it. S3 exports no longer fail when a sync page touches a Glue table that is not there yet, because a missing table is treated as missing when loaded lazily. The dashboard health page now shows schema validation and index backfill progress, with a line per job while a deploy is validating a schema or building indexes. The ai-sdk-provider reached 0.3.0 for the stable release of voice support and opt-in ZDR routing, and transcription failures now use APICallError so transient HTTP errors honor maxRetries. The logs page gained a search query argument for linking to filtered views, the S3 integration was renamed to AWS S3 wi

Week of September 28, 2026

What shipped

Why it matters

This week brings expanded regional availability for deployments and improvements to reliability and correctness across WebAssembly execution, database operations, and web standards compliance. Fixes to error labeling and documentation make the platform easier to debug and understand.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New regions live: Sydney (ap-southeast-2) and Montreal (ca-central-1). Plus improvements to WASM error reporting, index backfill reliability, and web spec compliance.

Post for LinkedIn

This week we expanded Convex's regional footprint with Sydney and Montreal now available for deployments. We also shipped reliability improvements to index backfill operations with MySQL deadlock retries, better WebAssembly error labeling to distinguish import vs execution failures, and enhanced Request/Response spec compliance. These changes support better debugging and more robust database operations for production deployments.

Week of September 21, 2026

What shipped

Why it matters

This week focused on stability improvements for v6 persistence migrations and storage operations. Fixes to index scanning recovery and error reporting improve reliability for deployments managing large datasets. New regional options expand deployment choices.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: improved async error reporting, fixed URLSearchParams behavior, added 1.0 storage syscalls, and resolved v6 migration index scanning issues. Canada and Australia region support now available.

Post for LinkedIn

Convex updates this week address database reliability and developer experience. We fixed async stack trace formatting for better error visibility, resolved v6 persistence migration edge cases, and implemented the 1.0/storageStore syscall. The dashboard now supports Canada and Australia regions and improved validation for team operations. These changes strengthen deployment stability and expand regional availability.

More from get-convex/convex-backend on GitHub

Releases

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.