JavaGolangJavaScriptSwiftAndroidRustMiddleware
1 days ago
rustfs
rustfs

1.0.0-alpha.72

What's Changed

New Contributors

Full Changelog: https://github.com/rustfs/rustfs/compare/1.0.0-alpha.71...1.0.0-alpha.72

1 days ago
dgraph
dgraph-io

v25.1.0-preview1

What's Changed

Full Changelog: https://github.com/dgraph-io/dgraph/compare/v25.0.0...v25.1.0-preview1 See also: https://github.com/dgraph-io/dgraph/releases

1 days ago
dgraph
hypermodeinc

v25.1.0-preview1

What's Changed

Full Changelog: https://github.com/dgraph-io/dgraph/compare/v25.0.0...v25.1.0-preview1 See also: https://github.com/dgraph-io/dgraph/releases

1 days ago
superset
apache

6.0.0rc4

Hello Superset Community,

This is a call for the vote to release Apache Superset version 6.0.0.

The release candidate: https://dist.apache.org/repos/dist/dev/superset/6.0.0rc4/

The Git tag for the release: https://github.com/apache/superset/tree/6.0.0rc4

The CHANGELOG for the release: https://github.com/apache/superset/blob/6.0.0rc4/CHANGELOG/6.0.0.md

The instructions for updating to the release: https://github.com/apache/superset/blob/6.0.0rc4/UPDATING.md

Public keys are available at: https://www.apache.org/dist/superset/KEYS

The vote will be left open until at least 72 hours have passed and the necessary number of votes (3) have been reached.

Please vote accordingly:

[ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason

Thanks, The Apache Superset Team

1 days ago
valkey
valkey-io

8.1.5

Upgrade urgency MODERATE: Program an upgrade of the server, but it's not urgent.

Bug fixes

  • Fix Lua VM crash after FUNCTION FLUSH ASYNC + FUNCTION LOAD (#1826)
  • Fix invalid memory address caused by hashtable shrinking during safe iteration (#2753)
  • Cluster: Avoid usage of light weight messages to nodes with not ready bidirectional links (#2817)
  • Send duplicate multi meet packet only for node which supports it (#2840)
  • Fix loading AOF files from future Valkey versions (#2899)

Full Changelog: https://github.com/valkey-io/valkey/compare/8.1.4...8.1.5

2 days ago
MeiliSearch
meilisearch

v1.28.2 🐩

This release fixes a bug affecting the Prometheus metrics route in versions 1.28.0 and 1.28.1, specifically when the instance has too many tasks. The issue is visible as high memory usage and could cause the instance to be OOM-killed. If you are using the /metrics route, we recommend deleting all succeeded or failed functions in the index using the dedicated route or upgrading to at least v1.28.2.

🐛 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.28.1...v1.28.2

2 days ago
rustfs
rustfs

1.0.0-alpha.71

What's Changed

New Contributors

Full Changelog: https://github.com/rustfs/rustfs/compare/1.0.0-alpha.70...1.0.0-alpha.71

2 days ago
timescaledb
timescale

2.24.0 (2025-12-03)

This release contains performance improvements and bug fixes since the 2.23.1 release. We recommend that you upgrade at the next available opportunity.

Highlighted features in TimescaleDB v2.24.0

  • Direct Compress just got smarter and faster: it now works seamlessly with hypertables generating continuous aggregates. Invalidation ranges are computed directly in-memory based on the ingested batches and written efficiently at transaction commit. This change reduces the IO footprint drastically by removing the write amplification of the invalidation logs.
  • Continuous aggregates now speak UUIDv7: hypertables partitioned by UUIDv7 are fully supported through an enhanced time_bucket that accepts UUIDv7 values and returns precise, timezone-aware timestamps — unlocking powerful time-series analytics on modern UUID-driven table schemas.
  • Lightning-fast recompression: the new recompress := true option on the compress_chunk API enables pure in-memory recompression, delivering a 4–5× speed boost over the previous disk-based process.

ARM support for bloom filters The sparse bloom filter indexes will stop working after upgrade to 2.24. If you are affected by this problem, the warning "bloom filter sparse indexes require action to re-enable" will appear in the Postgres log during upgrade.

In versions before 2.24, the hashing scheme of the bloom filter sparse indexes used to depend on the build options of the TimescaleDB executables. These options are set by the package publishers and might differ between different package sources or even versions. After upgrading to a version with different options, the queries that use the bloom filter lookups could erroneously stop returning the rows that should in fact match the query conditions. The 2.24 release fixes this by using distinct column names for each hashing scheme.

The bloom filter sparse indexes will be disabled on the compressed chunks created before upgrading to 2.24. To re-enable them, you have to decompress and then compress the affected chunks.

If you were running the official APT package on AMD64 architecture, the hashing scheme did not change, and it is safe to use the existing bloom filter sparse indexes. To enable this, set the GUC timescaledb.read_legacy_bloom1_v1 = on in the server configuration.

The chunks compressed after upgrade to 2.24 will use the new index format, and the bloom filter sparse indexes will continue working as usual for these chunks without any intervention.

For more details, refer to the pull request #8761.

Deprecations

Backward-Incompatible Changes

  • #8761 Fix matching rows in queries using the bloom filter sparse indexes potentially not returned after extension upgrade. The version of the bloom filter sparse indexes is changed. The existing indexes will stop working and will require action to re-enable. See the section above for details.

Features

  • #8465 Speed up the filters like x = any(array[...]) using bloom filter sparse indexes.
  • #8569 In-memory recompression
  • #8754 Add concurrent mode for merging chunks
  • #8786 Display chunks view range as timestamps for UUIDv7
  • #8819 Refactor chunk compression logic
  • #8840 Allow ALTER COLUMN TYPE when compression is enabled but no compressed chunks exist
  • #8908 Add time bucketing support for UUIDv7
  • #8909 Support direct compress on hypertables with continuous aggregates
  • #8939 Support continuous aggregates on UUIDv7-partitioned hypertables
  • #8959 Cap continuous aggregate invalidation interval range at chunk boundary
  • #8975 Exclude date/time columns from default segmentby
  • #8993 Add GUC for in-memory recompression

Bugfixes

  • #8839 Improve _timescaledb_functions.cagg_watermark error handling
  • #8853 Change log level of continuous aggregate refresh messages to DEBUG1
  • #8933 Potential crash or seemingly random errors when querying the compressed chunks created on releases before 2.15 and using the minmax sparse indexes.
  • #8942 Fix lateral join handling for compressed chunks
  • #8958 Fix if_not_exists behaviour when adding refresh policy
  • #8969 Gracefully handle missing job stat in background worker
  • #8988 Don't ignore additional filters on same column when building scankeys

GUCs

  • direct_compress_copy_tuple_sort_limit: Number of tuples that can be sorted at once in a COPY operation.
  • direct_compress_insert_tuple_sort_limit: Number of tuples that can be sorted at once in an INSERT operation.
  • read_legacy_bloom1_v1: Enable reading the legacy bloom1 version 1 sparse indexes for SELECT queries.
  • enable_in_memory_recompression: Enable in-memory recompression functionality.

Thanks

  • @bezpechno for implementing ALTER COLUMN TYPE for hypertable with columnstore when no compressed chunks exist
3 days ago
milvus
milvus-io

milvus-2.6.7

v2.6.7

Release date: December 4, 2025

Milvus Version Python SDK Version Node.js SDK Version Java SDK Version Go SDK Version
2.6.7 2.6.4 2.6.5 2.6.10 2.6.1

Milvus 2.6.7 is a critical stabilization update for the 2.6.x series. This release focuses on hardening the system against distributed failures and optimizing resource utilization under high load. With significant improvements in I/O handling, memory management, and Kubernetes integration, we strongly recommend all production users upgrade to this version to ensure greater reliability and smoother operation at scale.

Features

  • Added /livez endpoint to support Kubernetes native liveness probes, improving container orchestration stability (#45481).
  • Added support for GroupBy operations on TIMESTAMPZ fields, enhancing time-series analytics capabilities (#45763)
  • Supported mmap for JSON shredding's shared key indices to reduce RAM footprint (#45861)

Improvements

  • Supported DML request forwarding in the Proxy to improve write availability and routing resilience (#45922).
  • Upgrade etcd to v3.5.23 to address consensus stability and performance regressions (#45953).
  • Added robust error handling for Etcd server crashes to prevent cascading component failures (#45633).
  • Reduced Etcd load by removing expensive watchers for simple session liveness checks (#45974).
  • Enhanced the WAL retention strategy to better balance disk usage with data recovery safety (#45784).
  • Supported asynchronous write syncing for logs to prevent disk I/O blocking from affecting the main execution path (#45806).
  • Enforced Buffered I/O usage for high-priority load tasks to optimize OS page cache utilization and throughput (#45958).
  • Optimized mmap strategy to map group chunks in a single system call, reducing kernel overhead during segment loading (#45893).
  • Improved the accuracy of memory estimation for JSON shredding to prevent OOM kills or under-utilization (#45876).
  • Refined segment load estimation to account for both eviction and warmup states (#45891).
  • Added granular cancellation checks in query operators to allow faster termination of aborted or timed-out queries (#45894).
  • Removed redundant resource type checks in file resource configuration (#45727).

Bug fixes

  • Interleaved Go and C++ logs into a unified stream to provide a correct chronological view for debugging (#46005).
  • Resolved a race condition where LastConfirmedMessageID could be incorrect under high concurrency writes (#45874).
  • Fixed a calculation error in aggregating allsearchcount from multiple search results (#45904).
  • Fixed Term expressions to correctly handle string containment logic within JSON arrays (#45956).
  • Replaced json.doc() with json.dom_doc() in JSONContainsExpr to fix parsing behaviors and improve performance (#45786).
  • Fixed a panic in Standby MixCoord components during the shutdown sequence (#45898).
  • Fixed the leader checker to ensure segment distribution is correctly synchronized to Read-Only nodes (#45991).
  • Ensured HandleNodeUp is triggered during node re-watching to maintain correct load balancing topology (#45963).
  • Implemented fallback to remote WAL storage if local WAL storage becomes unavailable (#45754).
  • Added EmptySessionWatcher to prevent panics when running in IndexNode binding mode (#45912).
  • Ensured memory state consistency when recovering broadcast tasks from protocol buffers (#45788).
  • Addressed thread-safety issues in SegCore collection schema updates (#45618).
  • Enforced Access Control (RBAC) checks for ListImport and GetImportProgress APIs (#45862).
  • Fixed a bug where BulkImport would fail if the input contained an empty struct list (#45692).
3 days ago
ClickHouse
ClickHouse

Release v25.11.2.24-stable