nginx-1.28.3
stable and
nginx-1.29.7
mainline versions have been released,
with fixes for
buffer overflow
vulnerability in the ngx_http_dav_module (CVE-2026-27654),
buffer overflow
vulnerabilities in the ngx_http_mp4_module (CVE-2026-27784, CVE-2026-32647),
mail session authentication
vulnerabilities (CVE-2026-27651, CVE-2026-28753) and
OCSP result bypass
vulnerability in stream (CVE-2026-28755)
26.1, the release of Tiny Takeover, is a game drop for Java Edition released on March 24, 2026, which adds new textures and models for every baby mob that did not already have a unique model, adds the golden dandelion, makes name tags craftable, and fixes bugs.
Full changelog: https://minecraft.wiki/Java_Edition_26.1
We are pleased to announce the availability of a preview of the MariaDB 13.0 series. MariaDB 13.0 is a preview rolling release, published on 23 March 2026, and it continues the work started in 12.3 while adding a solid set of entirely new features. …
feat(database): add official postgres 18 and pgvector 18 support -> You could always change the database image and volume mount path manually and achieve unofficial support that is why this was not added faster
feat(ui): add postgres 16 to the UI
feat(ui): improve global search with uuid and pr support
feat(installer): add tencentos as a supported os
feat(service): upgrade checkmate to v3 with all the necessary changes
feat(service): upgrade listmonk to v6 with all the necessary changes
feat(service): upgrade formbricks to v4 with all the necessary changes
feat(service): add service database restore/import support
feat(api): add url update support to services api
feat(api): add more allowed fields to application api endpoints
added dockerfile_location as it is needed for Dockerfile deployments to work properly
added is_spa which can be used together with is_static
added is_auto_deploy_enabled and is_force_https_enabled
feat(api): allow to escape special characters in labels
feat(api): add tag filtering on the applications list endpoint
feat(api): improve docker_compose_domains with conflict checking and force_domain_override support
feat(notifications): add mattermost notifications (an open source slack alternative)
feat: add application logs link to preview deployments PR comment
feat(magic): add LOWERCASEUSER as magic variable which are sometimes required e.g. as docker registry username
feat(ui): show server name on resource card
feat(ui): improve sidebar menu items styling
feat(install): add postmarketos to the supported distributions
feat(ui): make git repository dropdown searchable
feat(service): upgrade n8n template to v2 with all the necessary changes
feat(service): upgrade trigger.dev template to v4 with all the necessary changes
feat(service): upgrade uptime kuma to version 2 with all the necessary changes
feat(service): upgrade docker registry template to v3 with all the necessary changes
feat(service): upgrade postgresus to databasus
feat(service): improve matrix templates by adding postgres and improving naming
feat(service): add healthchecks to evolution-api service
feat(services): update authentik
feat: allow more characters specifically Unicode alpha-numeric characters contained in \p{L}, \p{M}, \p{N} when validating while still not allowing any unsafe characters
feat(lang): add missing chinese translation keys
feat(lang): update portuguese language keys
feat(ui): add port mapping format to helper and fix typo
perf: optimize destinationsByServer query
fix(env): environment variable sorting not working
fix(git): trigger deployments when watch paths is empty and not just when they are null
fix(backup): database restores with custom db name with backup all databases not working
fix(logdrain): use deployment server and not build server settings
fix(service): twenty template and enable it again
fix(docker): use dynamic OS ID for ubuntu based OSs to use the correct Docker repository URL
fix: instance public ips initialization validation
fix: cast docker version to int for proper comparison
fix: making the db public does not instant save the port
fix(log): preserve leading whitespace in logs
fix(logs): remove hardcoded 2000 line limit
fix(api): remove incorrect uuid format from cuid2 parameters in openapi spec
fix(api): applications post and patch endpoints
remove docker_compose_raw from post and patch endpoints, as the compose file is sourced from git and should not be manually settable via the api
improve the documentation for docker_compose_domains (URLs)
enhanced array validation for docker_compose_domains by validating each array field and verifying which fields are allowed
set a custom array validation error message, as the default message is not really clear
show an error if the user attempts to set domains when the build pack is dockercompose
validate that the domains in docker_compose_domains are proper URLs and include a valid scheme (http or https)
fix(api): include docker_compose_domains in domain conflict check via Application::ownedByCurrentTeamAPI
fix(api): is_static and connect_to_docker_network fields where not updating on some endpoints
fix(api): if domains field is empty clear the fqdn column which allows to remove all URLs from the domains field
fix(api): check for domain conflicts within the current request
fix(api): deprecate application create compose endpoint as it is an unstable duplicate of the services endpoint
fix(api): one click service name and description cannot be set during creation
fix(api): create service endpoint validation and docs
if service type and docker_compose_raw is filled show an error
if service type is not valid show an error with all valid service types
remove enum from service type docs as it always gets outdated
fix(api): encoding checks for compose files, nginx configurations, dockerfiles, database configs and labels
switch from ASCII to UTF-8 to allow special characters, emojis and more
fix(api): remove environments from projects API endpoint docs
fix(api): docs for bulk env update response
fix: APP_NAME env in development
using a different APP_NAME for development might seem like a good idea but it is annoying and causes issues when debugging, especially with Redis as it is used as the key prefix
fix(preview): docker compose preview URLs
fix: 404 on /settings for root user on cloud instance
fix(ui): empty network destinations when cloning a resource
fix(ui): instance public ips ui validation
fix(ui): images inside coolify changelog
fix(ui): domain input whitespace trimming in instance settings
fix(ui): change password visibility eye icon based on state
fix(ui): hide Already registered? button from the /register page when there are 0 users as clicking on it would just redirect you back to /register
fix(ui): improve volume mount warning for compose applications
fix(service): remove start command from unleash template
fix(service): add instagram envs to postiz template
fix(service): budibase worker envs
fix(service): correct POSTGRES_HOST in freshrss
fix(service): use fqdn for server host in sequin template
fix(service): wireguard easy host to use fqdn
fix(service): signoz metrics env
chore(deps): update composer and node dependencies
chore(docker): add healthchecks to dev services
chore(service): update weblate service
chore(service): update rybbit service
chore(service): improve mosquitto template
refactor(service): remove unused envs from hoppscotch
refactor(api): remove old stale domains update code from services endpoints
refactor(api): update application create endpoints docs to specify that Dockerfile and Docker Image deployment type are without git
26.1 Release Candidate 3 (known as 26.1-rc-3 in the launcher) is the third and final release candidate for Java Edition 26.1, released on March 23, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-rc-3
New uNmINeD development snapshot is available for download!
Changes:
(Minecraft) Reworked datapack and mod handling
(Minecraft) Textures now can be used with Bedrock worlds (experimental)
(Minecraft) Colors for custom/modded blocks now can be calculated automatically from textures
(CLI) Textures now can be used with the CLI
Automatic colors for custom blocks
uNmINeD now can read biome and block metadata from datapacks/mods and behavior/resource packs, and it calculates map colors for custom blocks automatically by averaging their textures instead of displaying them as pink.
Textured rendering
By default, uNmINeD displays each block as a square filled with a single color. When textured rendering is enabled, it still does not render blocks in 3D, instead it fills the squares with an image (the in-game texture of a block) rather than a solid color.
Textured rendering can be enabled on the render settings side panel (the tab with a cog wheel icon). It works for zoom-in levels 4:1 or higher. It works well with cube-like blocks, but fences, walls and other blocks with a complex 3D model look off. Upcoming releases will be able to render fences and walls correctly, and images to be used for complex blocks will be customizable.
Usage with Java Edition
Using textures or datapacks/mods with Java Edition worlds requires a Minecraft client JAR file. If you have Minecraft installed, uNmINeD will automatically find your client JAR file, otherwise you have to copy it from another machine, and select it in uNmINeD’s app settings.
Usage with Bedrock Edition
Using textures or behavior packs with Bedrock Edition worlds requires a vanilla resource pack. You can download it from Mojang: https://github.com/Mojang/bedrock-samples/releases. Find your version (or use the latest), click on Assets, and download the full package named bedrock-samples-xxxxx-full.zip (or the source code zip package, either one is good), then select the downloaded file in uNmINeD’s app settings.
CLI usage
Use --java-client-jar=/path/to/1.21.11.jar to select your Minecraft client JAR.
Use --bedrock-vanilla-pack=/path/to/bedrock-samples-v1.26.0.2-full.zip to select your vanilla resource pack.
Use --textures=true for textured rendering (effective at zoom-in levels 4:1 or higher).
Selecting a client JAR or a vanilla resource pack is required for all datapack related functions, including automatic color calculation for custom blocks and textured rendering.
26.1 Release Candidate 1 (known as 26.1-rc-1 in the launcher) is the first release candidate for Java Edition 26.1, released on March 19, 2026. This is the first release candidate released in 2026 and the first release candidate to be released with only an unobfuscated build.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-rc-1
26.1 Pre-Release 3 (known as 26.1-pre-3 in the launcher) is the third and final pre-release for Java Edition 26.1, released on March 17, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-pre-3
26.1 Pre-Release 2 (known as 26.1-pre-2 in the launcher) is the second pre-release for Java Edition 26.1, released on March 13, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-pre-2
The PGCA Board would not be able to protect the PostgreSQL trademarks and brand assets without the generous financial support we receive from corporations, small businesses, and individual donors. We are deeply grateful for that support.
After reviewing sponsorship models used by other open source foundations, and in light of the increasing costs required to protect the PostgreSQL brand assets, we have increased the top two sponsorship levels: Benefactor and Patron, effective February 1, 2026. All other sponsorship levels remain unchanged. As always, we welcome and value donations at all levels, in any amount.
Significant update to the PGCA non-profit website
We’ve also made a significant update to the PGCA website, to modernize it and bring it forward to the present. We hope the new site makes it easier to understand the PGCA’s non-profit mission, learn how to use PostgreSQL trademarks appropriately, and donate, whether as a one-time or monthly contribution.
The updated PGCA website is at the same URL as before: www.postgres.ca.
Updated sponsorship levels and the sponsorship prospectus can be found on the Sponsors page at www.postgres.ca/sponsors/.
Bugfix (defect introduced: Postfix 3.0): buffer over-read when Postfix is configured with an enhanced status code not followed by other text. For example, "5.7.2" without text after the three-number code, in an access(5) table, header or body checks, or with "$rbl_code $rbl_text" in rbl_reply_maps or default_rbl_reply. These are all uncommon configurations. Problem reported by Kamil Frankowicz.
Bugfix (defect introduced: Postfix 3.3): null pointer in nbdb_reindexd(8) because the "service_name" value was not propagated. Report by Michael Tokarev.
26.1 Pre-Release 1 (known as 26.1-pre-1 in the launcher) is the first pre-release for Java Edition 26.1, released on March 10, 2026, which updates the panorama and makes technical changes. This is the first pre-release released in 2026, and the first pre-release to be released with only an unobfuscated build.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-pre-1
26.1 Snapshot 11 (known as 26.1-snapshot-11 in the launcher) is the eleventh and final snapshot for Java Edition 26.1, released on March 3, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-snapshot-11
Postfix stable release 3.11.0 is available. Postfix 3.7 - 3.10 were updated a few weeks ago; after that, Postfix 3.7 will no longer be updated.
The main changes are below. See the RELEASE_NOTES file for further details.
Berkeley DB migration:
Some (Linux) distributions are removing support for BerkeleyDB databases (In Postfix, this means we lose support for the hash: and btree: lookup tables). See NON_BERKELEYDB_README for manual and partially automatic migration from btree: to lmdb:, and from hash: to lmdb: or cdb:.
The loss of BerkeleyDB affects Mailman versions that want to execute commands like "postmap hash:/path/to/file" when a mailing list is added or removed. Postfix provides a way to redirect such commands to a supported database type.
You don't have to wait until BerkeleyDB support is removed. It can make sense to migrate while BerkeleyDB support is still available (mainly, less downtime).
Changes in TLS support:
Default TLS security. The Postfix SMTP client smtp_tls_security_level default value is "may" if Postfix was built with TLS support, and the compatibility_level is 3.11 or higher.
Support for the RFC 8689 "REQUIRETLS" verb in ESMTP. This requires that every SMTP (and LMTP) server in the forward path is strongly authenticated with DANE, STS, or equivalent, and that every server announces REQUIRETLS support.
See REQUIRETLS_README for suggestions to carefully enforce REQUIRETLS without causing massive mail delivery problems.
Logging the TLS security level. This shows the desired and actual TLS security level enforcement status and, if a message requests REQUIRETLS, the REQUIRETLS policy enforcement status. For a list of examples see smtp_log_tls_feature_status
Workaround for an interface mismatch between the Postfix SMTP client and MTA-STS policy plugins. This introduces a new parameter smtp_tls_enforce_sts_mx_patterns (default: "yes"). The MTA-STS plugin configuration needs to enable TLSRPT support, so that it forwards STS policy attributes to Postfix. Both postfix-tlspol and postfix-mta-sts-resolver have been updated accordingly.
With this, the Postfix SMTP client will connect to an MX host only if its name matches any STS policy MX host pattern, and will match a server certificate against the MX hostname. Otherwise, the old behavior stays in effect: connect to any MX host listed in DNS, and match a server certificate against any STS policy MX host pattern.
Post-quantum cryptography support. With OpenSSL 3.5 and later, change the tls_eecdh_auto_curves default value to avoid problems with network infrastructure that mishandles TLS hello messages larger than one (Ethernet) TCP segment. This problem is more generally known as "protocol ossification".
Miscellaneous changes:
Deprecation of obsolete parameters. Postfix programs log a warning that these parameters will be removed. See DEPRECATION_README for a list of deprecated parameters.
JSON output support with "postconf -j|-jM|-jF|-jP", "postalias -jq|-js", "postmap -jq|-js", and "postmulti -jl". No support is planned for JSON input support.
Milter support: improved Milter error handling for messages that arrive over a long-lived SMTP connection, by changing the default milter_default_action from "tempfail" to the new "shutdown" action (i.e. disconnect the remote SMTP client). This was already back-ported to earlier stable releases.
There are more changes; see RELEASE_NOTES for those.
Log in
