New uNmINeD development snapshot is available for download!
Changes:
Full Changelog: v4.3.11...v4.3.12
New uNmINeD development snapshot is available for download!
Changes:
Log in
pg_restore (#11481, fixes #11459).Full Changelog: v4.3.10...v4.3.11
MariaDB Server maintenance releases are here!
On August 24, we released updates for our four currently maintained Long Term Support series:
As usual, these maintenance releases include bug fixes, stability improvements, and ongoing work across MariaDB Server. …
MariaDB Server 12.3, 11.8, 11.4 and 10.11 – Q3 2026 Maintenance Releases, and Goodbye 10.6 appeared first on MariaDB.org
New uNmINeD development snapshot is available for download!
Changes:
Minecraft Java Edition from version 26.3-snapshot-7 does not store blockstate properties in the world save files when referencing a default blockstate. This caused these blockstates to render incorrectly.
uNmINeD now uses a configuration file config/vanilla.defaultblockstates.java.txt to resolve default vanilla blockstate properties. If it encounters a blockstate reference without properties, it will use the default properties from the configuration file.
The configuration file only contains default blockstate information for vanilla blocks. A mod will be available later that will allow you to generate a blockstate configuration file for modded worlds.
If you are upgrading from v0.16.x, replace the binary (or run docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
oauthClientId setting in Application, which allows the WebUI to use a different OAuth client than the default.env.spam.score and env.spam.is_spam variables, which expose the spam filter result to system scripts running at the DATA stage.vCardVersion setting in AddressBook, which allows the default vCard version to be specified when the client does not request a specific version.VARBINARY(255) with a full-length primary key instead of TINYBLOB. Note: Existing deployments should run, once per table, for each of the tables a, d, e, f, g, h, j, k, l, m, n, o, p, q, r, s, t, u, w, x and y the command ALTER TABLE a MODIFY k VARBINARY(255) NOT NULL;.mailto: URI percent-encodes a full name-addr are silently dropped from the scheduling snapshot.SCHEDULE-STATUS=3.7.PARTSTAT on the organizer's copy of the event only, leaving a local attendee's own copy at NEEDS-ACTION and sending the organizer no reply.MKCALENDAR, MKCOL and PROPPATCH store the display name, description, time zone and the other per-user properties under the authenticated account rather than the account that owns the collection./api/discover splits the account name on @ without accounting for the % master user separator or the recovery administrator.SETACL and DELETEACL fail to resolve an identifier spelled with uppercase characters.TZID parameter with no matching VTIMEZONE component whenever the event was stored without one.AddressBook/get: A new account's default address book is never recorded.Email/get and Email/parse with fetchAllBodyValues return body values only for the parts listed in textBody or htmlBody, omitting every other text/* part in bodyStructure.Email/set writes display names as an RFC 2047 encoded-word wrapped in a quoted-string, which RFC 2047 forbids.Mailbox/set, AddressBook/set and Calendar/set store isSubscribed and the other per-user properties under the authenticated account rather than the account named in the request.Principal/query returns no results when the name or email filter is spelled with uppercase characters.FileNode/set: File nodes created over JMAP are returned with a <D:href> holding the raw name over WebDAV.maxTotalHits pagination setting is left at the Meilisearch default.failOnTimeout is disabled.--import always aborts with the target database already containing data in the key range being imported.catchAllAddress pointing to a mailing list or a sub-addressed mailbox is accepted at RCPT TO and then rejected at local delivery with 550 5.5.0 Mailbox not found.is_local_address() and is_local_domain() expression functions do not match an address or domain spelled with uppercase characters.host resolves loopback address, which prevents relaying through a local proxy or tunnel.local_port and local_ip report the address Stalwart is bound to rather than the address the client connected to when the connection arrives through a trusted proxy.totalDeadline is not enforced on tasks that fail with a specific retry time.maxAttempts failures, so a search store that is unavailable or overloaded leaves messages permanently missing from the index.spamtest returns only 1 or 10 (and spamtest :percent only 0 or 100), so scripts cannot act on intermediate spam scores.MIME_BAD is tagged whenever the declared Content-Type of an attachment is not byte identical to the type detected from its magic bytes.
From headers (#11400, closes #11380).environment section (#11407, closes #11381).Full Changelog: v4.3.9...v4.3.10
New uNmINeD development snapshot is available for download!
Changes:
webp-format (lossless, lossy), webp-method (0..6) and webp-quality (0..100) command line parameters to web exportThe isometric mode is not yet optimized for speed, and isometric map tiles are not yet cached. Future releases will be faster.
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-23.5.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/23.5.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 23.5.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: George Joseph
Date: 2026-08-13
websocket_handled_pong_or_close() now checks that session->client is valid
before trying to check missed_pong_count.
Resolves: #2085
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-20.21.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/20.21.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 20.21.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: George Joseph
Date: 2026-08-13
websocket_handled_pong_or_close() now checks that session->client is valid
before trying to check missed_pong_count.
Resolves: #2085
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-22.11.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/22.11.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 22.11.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: George Joseph
Date: 2026-08-13
websocket_handled_pong_or_close() now checks that session->client is valid
before trying to check missed_pong_count.
Resolves: #2085
nginx-1.31.4 mainline version has been released.
This is the first release candidate for Coolify v4.4. It is intended for testing and validation before the stable v4.4 release.
Do not use this release candidate in production without appropriate testing. Please report regressions through GitHub Issues.
nextThese notes include only changes currently unique to next compared with main.
Comparison: main...next
Full Changelog: v4.3.8...v4.3.9
General
API
Media-Over-QUIC
RTSP
RTMP
inform about authentication failures (#5657) (#6072) Reply with NetStream.Play.Failed or NetStream.Publish.Unauthorized when a client is not authorized to play or publish. This makes clients like OBS to stop recreating the connection in case of authentication failures.
reader: do not emit empty frames (bluenviron/gortmplib#106)
parse video PTS delta as signed (bluenviron/gortmplib#88)
HLS
prefer hls.js on iOS too (#6090) In the embedded HLS reader, use hls.js on iOS, that was previously disabled due to compatibility issues that should have been solved.
unlock the session-in-query+iOS combination (#6088) this was previously blocked because the session in query was meant to be dynamic, therefore incompatible with static playlists required by iOS. It is not anymore, so we can support that.
stop using cookies with plain HTTP (#6089) in case of plain HTTP, fall back to query parameters, which are safer than HTTP cookies because they are not shared between different pages/domains, although they are visible in the URL.
WebRTC
SRT
RPI Camera
Dependencies
Binaries are compiled from source code by the Release workflow, which is a fully-visible process that prevents any change or external interference in produced artifacts.
Checksums of binaries are also published in a public blockchain by using GitHub Attestations, and they can be verified by running:
ls mediamtx_* | xargs -L1 gh attestation verify --repo bluenviron/mediamtx
You can verify checksums of binaries by downloading checksums.sha256 and running:
cat checksums.sha256 | grep "$(ls mediamtx_*)" | sha256sum --check
Full Changelog: v4.3.7...v4.3.8
If you are upgrading from v0.16.x, replace the binary (or run docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
inboundReportMaxSize setting, which bounds the size of a decompressed inbound DMARC or TLS report (default 25MB).cacheSize setting, which bounds the total memory shared by the block caches of every column family (default 128MB).Identity/get keeps identities in sync with the account's e-mail addresses.uploadTtl to 1ms triggers panic.CalendarEvent/set does not assign organizerCalendarAddress nor send scheduling messages when an event is created with participants.CalendarEvent/get omits isOrigin when it is listed explicitly in properties.CalendarEventNotification/changes and FileNode/changes reject with cannotCalculateChanges the state that /get returned for an account with no change history.CalendarEvent/set and ContactCard/set do not write a vanished tombstone for the previous CalDAV/CardDAV href when calendarIds or addressBookIds moves an item between collections.mailto: URI are queued verbatim.REPORTs and JMAP CalendarEvent/query results a few years after their first occurrence.MOVE on a folder honors a Depth header of 0 or 1 instead of always moving the whole subtree.Message-ID wrapped in doubled angle brackets.source never match at enqueue.testing mode are enforced, turning any TLS error into a permanent failure.mx patterns published as U-labels never authorize the MX host they name.application/octet-stream as Content-Type for encrypted payloads.550 Relay not allowed, unless the domain's primary name happened to be resolved earlier and is still cached.bufferSize setting was applied to the unused default column family and had no effect.include statements fail to find system and user global scripts whose name contains uppercase characters.totalDeadline is measured from the time a task was created instead of its first failed attempt.
coolify.managed=true label (#8831, closes #8822).Full Changelog: v4.3.6...v4.3.7
Full Changelog: v4.3.5...v4.3.6
Full Changelog: v4.3.4...v4.3.5
Full Changelog: v4.3.3...v4.3.4
Full Changelog: v4.3.2...v4.3.3
New uNmINeD development snapshot is available for download!
Changes:
--textures=true) experimental feature is no longer availableuNmINeD now can read and use 3D block models from Java Edition client JARs and datapacks, and render them in 2.5D top-down and isometric views.
Bedrock Edition does not have 3D block models available for external tools, so uNmINeD uses Java block models to render Bedrock blocks. You will need a Java client JAR file to make this work. You can download it even if you do not have Java Edition, the original Mojang download links are available on GitHub, scroll right to see the client JARs.
Assigning Java block models to Bedrock blocks is controlled by config/bedrockmapping.json. The content of this file is largely based on information extracted from the Chunker project.
Bedrock fences, stairs, glass panes and other connecting blocks may render incorrectly if you have a version older than 1.26.40, because the required information is not present in the world save files.
This is a preview of a new feature under development.
uNmINeD now can render 3D block models to draw blocks instead of using single colors.
Use the --blockrender=true command line parameter to enable block model rendering in the CLI.
This is a preview of a new feature under development.
uNmINeD now can render an “isometric” (axonometric) 3D map.
Block model rendering is a new feature under development. There are a lot of bugs, glitches and unfinished stuff. The code is not yet optimized for speed, upcoming releases will be faster.
Some of the most visible known problems:
0 (#11249, closed #10623).www counterpart domains and corrected domain guidance and mobile domain visibility.Full Changelog: v4.3.1...v4.3.2
The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 18.6, 17.11, 16.15, 15.19, and 14.24, as well as the third beta release of PostgreSQL 19. This release fixes 28 security vulnerabilities and over 110 bugs reported over the last several months.
This release skips PostgreSQL 18 versions from PostgreSQL 18.4 to 18.6. 18.5 was not shipped due to a regression.
There are three issues that may require you to take extra steps after updating, which are described in detail below. These issues are related to:
btree_gistltreeFor the full list of changes, please review the release notes.
PostgreSQL 14 will stop receiving fixes on November 12, 2026. If you are running PostgreSQL 14 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.
The following security vulnerabilities are closed across in this update release. You can find more details about the vulnerabilities and their affected versions in the links below:
This update fixes over 110 bugs that were reported in the last several months.
This specific issue only affects PostgreSQL 14, 15, and 16, but we're highlighting it in the release announcement due to its severity:
The remainder of issues listed below affect PostgreSQL 18. Many of these issues also affect other supported versions of PostgreSQL.
reltuples value in pg_class.
Previously, a parallel worker could report an uninitialized row count, leaving
reltuples set to a bogus value (including Infinity or NaN). Such a
value can cause autovacuum and autoanalyze to not process the table, and this
situation will not self-correct. If you have any tables with GIN indexes,
we recommend checking that their reltuples values look reasonable after
updating. See the "Updating" section for how to identify and repair affected
tables.btree_gist,
including for NaN handling for float4/float8 that could give wrong
answers for columns containing NaN and correct sorting of bit/bit varying
values during index building. You may need to reindex btree_gist
indexes on float or bit columns after updating. See the "Updating" section.ltree comparisons.
ltree values containing more than about 14,653 labels could compare
incorrectly, which could present as a corrupt B-tree index. If you use ltree,
you may need to reindex affected indexes after updating. See the "Updating"
section.RANGE-partitioned tables so the DEFAULT partition is no longer skipped in
cases where it should be scanned. Previously this could cause rows to be missing
from query results.RETURNING with
OLD and NEW.NULL values.value IN (array) tests where the array might be empty, and COUNT() window
functions that use an EXCLUDE clause or lack ORDER BY.REINDEX
CONCURRENTLY on an
index backing a deferred uniqueness constraint, which could cause false
constraint-violation reports.LIKE or
regular-expression exact-match pattern into an equality index condition when the
index and expression collations differ.jsonpath,
including that the @? and @@ operators now correctly raise an error for an
undefined variable in the path expression. Previously, because these operators
cannot supply variable values, an undefined variable was treated as a JSON
null rather than an error, which could also lead to unbounded memory
consumption."no empty local buffer available" errors during temporary table access
when a large effective_io_concurrency
setting could allow a single read stream to consume all local buffers.VACUUM's
wraparound failsafe mode to use the full shared buffer pool as intended, which
had slowed down emergency vacuuming.SERIALIZABLE
isolation. A conflict could be missed when examining an initially-empty btree
index, allowing conflicting transactions to commit and breaking serializability.COMMIT PREPARED or ROLLBACK PREPARED to the output plugin with no
preceding PREPARE, which breaks replication for the built-in subscriber.libpq,
including ensuring it drains all pending bytes from the SSL or GSS decryption
buffer when reading data, avoiding cases where a client waits for data that has
already arrived.pg_createsubscriber
to clean up objects left on a publisher after failure, including a replication
slot.pg_restore
with --statistics or --statistics-only so that, when combined with other
selective-restore options such as --schema, it restores the expected items,
matching the behavior of pg_dump.This release also updates time zone data files to tzdata release 2026c, in which Alberta (America/Edmonton) will be on year-round UTC-06 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be CST from that time forward (though this could change). It also reflects that Morocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving transitions, on September 20, 2026.
All PostgreSQL update releases are cumulative. As with other minor releases,
users are not required to dump and reload their database or use pg_upgrade
in order to apply this update release; you may simply stop PostgreSQL and
update its binaries.
If you have any tables with GIN indexes, we recommend checking their reltuples
values after updating. A prior bug in parallel GIN index builds could have left
reltuples set to a bogus value (including Infinity or NaN) that prevents
autovacuum and autoanalyze from ever processing the table. The following query
lists the tables that have a GIN index, along with their current reltuples:
SELECT DISTINCT t.oid::regclass, t.reltuples
FROM pg_class t
JOIN pg_index i ON t.oid = i.indrelid
JOIN pg_class ic ON i.indexrelid = ic.oid
WHERE t.relhasindex AND ic.relam = 2742;
For any table whose reltuples value looks incorrect, run
ANALYZE on it (or
create another index) to reset the value.
If you use btree_gist, you should reindex btree_gist indexes on float4 or
float8 columns that might contain NaN values, as well as btree_gist indexes
on bit or bit varying columns, for example:
REINDEX INDEX your_index_name;
If you use ltree and have btree indexes over ltree values with very many
labels (more than about 14,653), you should
reindex those
indexes, since they may be corrupt, for example:
REINDEX INDEX your_index_name;
Users who have skipped one or more update releases may need to run additional post-update steps; please see the release notes from earlier versions for details.
For more details, please see the release notes.
This release marks the third beta release of PostgreSQL 19.
In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 19 on your systems to help us eliminate bugs and other issues. While we do not advise you to run PostgreSQL 19 Beta 3 in production environments, we encourage you to find ways to run your typical application workloads against this beta release.
Your testing and feedback helps the community ensure that PostgreSQL 19 upholds our standards of delivering a stable, reliable release of the world's most advanced open source relational database. Please read more about our beta testing process and how you can contribute:
https://www.postgresql.org/developer/beta/
To upgrade to PostgreSQL 19 Beta 3 from an earlier version of PostgreSQL,
you will need to use a strategy similar to upgrading between major versions of
PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore). For more
information, please visit the documentation section on
upgrading.
Fixes and changes in PostgreSQL 19 Beta 3 include:
GROUP BY ALL.FOR PORTION OF temporal table syntax.REFRESH SEQUENCES.postgres_fdw when pushing down an array
comparison such as field = ANY($1) that involves an implicit type coercion.UNIQUE constraint.pg_plan_advice parsing of underscores in numeric literals.FORMAT clause when deparsing JSON_ARRAY(query).Please see the release notes for a complete list of new and changed features:
https://www.postgresql.org/docs/19/release-19.html
The stability of each PostgreSQL release greatly depends on you, the community, to test the upcoming version with your workloads and testing tools to find bugs and regressions before the general availability of PostgreSQL 19. As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible. Your feedback and testing will help determine the final tweaks on the new features, so please test in the near future. The quality of user testing helps determine when we can make a final release.
A list of open issues is publicly available in the PostgreSQL wiki. You can report bugs using this form on the PostgreSQL website:
https://www.postgresql.org/account/submitbug/
If you have corrections or suggestions for this release announcement, please send them to the pgsql-www@lists.postgresql.org public mailing list.
Full Changelog: v4.3.0...v4.3.1
24.0.0-pre1
