Skip to content

Releases: PeerDB-io/peerdb

v0.36.0

Choose a tag to compare

@Amogh-Bharadwaj Amogh-Bharadwaj released this 03 Dec 09:21
661fc01

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

Important

Please pause all mirrors before upgrading to this version!
This version includes a code migration which can cause your mirrors to go non-deterministic and difficult to recover if they're running during deployment.

What's Changed

  • Reapply "Store and migrate Postgres table OIDs to catalog (#3704)" (… by @jgao54 in #3730
  • track uncompressed bytes for mongodb connector by @jgao54 in #3715
  • support Avro uncompressed - improvements by @jgao54 in #3739
  • better error handling for getPartitions by @jgao54 in #3742
  • notify connectivity error by @jgao54 in #3748
  • Notify on auth failure for mongo connector by @jgao54 in #3747
  • Dark mode and UI fixes by @ilidemi in #3736
  • Don't warn on Mongo variant unsupported by @ilidemi in #3744
  • Display more precise durations in batches table by @ilidemi in #3743
  • make a catch-all for mongo pool cleared errors by @jgao54 in #3745
  • pg qrep: config for avro schema nullable, debug logging by @ilidemi in #3750
  • Add missing fields from table addition by @ilidemi in #3755
  • improve schema validations gaps by @jgao54 in #3752
  • Refactor SchemaTable -> QualifiedTable (and move to pkg) by @jgao54 in #3758

Full Changelog: v0.35.5...v0.36.0

v0.35.5

Choose a tag to compare

@github-actions github-actions released this 21 Nov 21:52
ca56ccc

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What's Changed

New Contributors

Full Changelog: v0.35.4...v0.35.5

v0.35.4

Choose a tag to compare

@github-actions github-actions released this 17 Nov 23:59
d6d2d6d

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What’s Changed

v0.35.3

Choose a tag to compare

@github-actions github-actions released this 17 Nov 19:24
feef191

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What’s Changed

v0.35.2

Choose a tag to compare

@github-actions github-actions released this 11 Nov 11:44
682140c

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What’s Changed

v0.35.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 22:39
5280636

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What's Changed

Full Changelog: v0.35.0...v0.35.1

v0.35.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 01:19
86a027a

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

Breaking changes

  • We removed the PEERDB_CLICKHOUSE_NORMALIZATION_PARTS setting which historically allow us to chunk our normalization query into parts to address OOM issues for tables with very high volume of updates per batch during CDC. This setting is not enabled by default, and was used sparingly by us. We discovered that if used in conjunction with PEERDB_CLICKHOUSE_PARALLEL_NORMALIZE, could trigger a race condition that results in data loss during replication. The setting that is more useful for addressing OOMs is PEERDB_S3_BYTES_PER_AVRO_FILE, which determines the staging Avro file size limit.

New features

  • We added support for Amazon DocumentDB 5.0 by testing its change stream API and removing validation checks that were blocking DocumentDB peer setup.

Changelog

Full Changelog: v0.34.8...v0.35.0

v0.34.8

Choose a tag to compare

@github-actions github-actions released this 30 Oct 17:40
9a2231a

Caution

PeerDB UI on this version is vulnerable to CVE-2025-66478

What’s Changed

v0.34.7

Choose a tag to compare

@github-actions github-actions released this 30 Oct 04:48
3af0833

What’s Changed

v0.34.6

Choose a tag to compare

@github-actions github-actions released this 13 Oct 18:15
c16430d

What’s Changed

Bugfix/breaking change: Mirror names must now be unique across all mirror types (#3493).

  • What changed: Previously, CDC mirrors assumed unique naming without enforcing it. Now it is enforced and QRep mirrors follow the same rule for consistency. This change makes mirror creation more reliable - if your network drops during setup, you can safely retry without creating duplicates.
  • Migration: No action needed! The database migration automatically handles any existing duplicates, keeping only the most recent mirror.