Last week, we showed you the new Atlas gameplay feature coming to American Truck Simulator with the release of Road Trip. And today, we are excited to also showcase a video trailer focused on Atlas!
This upcoming feature is designed around exploration and encourages players to discover, visit, and learn about selected locations across the world of American Truck Simulator via Tourist Boards. These will then uncover Points of Interest, Viewpoints, and Photo Trophies, which highlight significant spots in the region that you'll need to discover to earn a special postcard reward. You can find out more about Atlas in the dedicated blog.
Now, to get you in the mood for the upcoming Road Trip DLCs, we have put together a video trailer where you can see in more detail how Atlas will work in American Truck Simulator. Let's watch it below!
Keep in mind that Atlas will only be unlocked for players owning any Road Trip DLC (Ford Car Pack or RAM & Dodge Car Pack), so make sure to add them to your Steam wishlist. However, this feature is not limited to cars, and you will also be able to enjoy it when driving a truck.
Don't forget to give our X/Twitter, Instagram, Facebook, Bluesky, and TikTok a follow to not miss out on any Road Trip news, or subscribe to our newsletter to stay informed!
Full Changelog: v1.7.0.8...v1.8.0.4
New uNmINeD development snapshot is available for download!
Changes:
Log in--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:
Full Changelog: v1.7.0.8...v1.8.0.3
You’ve been asking all year, and the wait is over… Mark your calendars, because Community Day 2026 will be held on Saturday, November 7! 🎉
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.
The Stable channel has been updated to 152.0.7977.42/.43 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.
You can find more details about early Stable releases here.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Srinivas Sista
Google Chrome
Back in April during State of the Open Home 2026, we gave you a sneak peek of ESPHome’s very first official product… And after months of hard work alongside the community, the ESPHome Starter Kit is here! 🎉
ItemView by @JPKribs in #2077sidebarAdaptable by @LePips in #2107MediaInfoSupplement by @JPKribs in #2139jellyfin-sdk-swift to 3.0.0 (12.0) by @JPKribs in #2172MediaSource / MediaStream by @JPKribs in #2184officialRatings by @JPKribs in #2190Runtimes by @JPKribs in #2170safeAreaBar, liquid glass supported tabs by @LePips in #2096PlatformViewRepresentable by @LePips in #2108ItemView by @LePips in #2112navigationBarTitleDisplayMode to toolbarTitleDisplayMode by @LePips in #2123Full Changelog: 1.5...1.6
We're excited to share that, for the very first time in SCS Software's history, we'll be attending the Tokyo Game Show 2026! We can't wait to meet our community in Japan and be part of one of the world's most iconic gaming events as it celebrates an incredible milestone.
This year's edition of Tokyo Game Show is especially significant, marking the event's 30th anniversary. To celebrate this special occasion, TGS 2026 will take place over five full days, from September 17th to 21st, bringing together leading publishers, exciting upcoming games, and countless attractions for visitors from around the world.
You'll be able to find us in Hall 09, Booth E86, where our colleagues from SCS will be exhibiting in a compact booth made possible with the support of our friends at Neon Noroshi. Whether you're a longtime fan of our games or discovering them for the first time, we'd love for you to stop by, say hello, and experience what we've been working on.
During the first two days, the Tokyo Game Show is dedicated to gaming industry professionals, while the final three days are open to the public. Throughout the event, visitors will have the opportunity to get behind the wheel and try several of our upcoming projects, including the Iceland DLC for Euro Truck Simulator 2, as well as the upcoming British Columbia and South Dakota map expansions for American Truck Simulator.
We're also doing everything we can to bring playable demonstrations of our upcoming Road Trip and Coaches projects to Tokyo Game Show, along with a PlayStation 5 version of Euro Truck Simulator 2. While we're not quite ready to make any promises, our teams are working hard behind the scenes, and we hope to give visitors an early hands-on look at these exciting new experiences.
We're especially happy to share that Japanese-speaking visitors will be able to communicate with our team comfortably, as language interpreters will be available at our booth throughout the event. We hope this will make it even easier for everyone to ask questions, chat with us, and enjoy their time at our exhibit.
If you're planning to attend Tokyo Game Show 2026, we'd love to see you there! Be sure to stop by Hall 09, Booth E86, try out our latest projects, meet the team, and share your passion for trucking with us. We look forward to welcoming you to our very first Tokyo Game Show!
Full Changelog: v4.3.0...v4.3.1
24.0.0-pre1
Let us know what you think about the new UI here: #11195
GET requests now return 405 Method Not Allowed. This affected /enable, /disable, /deploy, server validation, application/database/service lifecycle actions, and service-application lifecycle actions (v4.2.0).www redirects for applications using Traefik.Full Changelog: v4.2.0...v4.3.0
The Extended Stable channel has been updated to 150.0.7871.230 for Windows and Mac which will roll out over the coming days/weeks.
Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Daniel Yip
Google Chrome
Below are development builds for testing purposes.
Latest development build: 2.8.0.49 (August 22nd 2026)
Latest stable release build: 2.8.0
https://github.com/clsid2/mpc-hc/releases/tag/2.8.0
Today, we're excited to share a brand-new gameplay preview from our upcoming South Dakota DLC for American Truck Simulator! Get a closer look at some of the beautiful roads, landmarks, and industries our map team has been recreating.
In the gameplay preview below, you'll follow a journey that begins in the Black Hills before passing by the scenic Pactola Lake and crossing the Spring Creek Memorial Bridge. Along the way, we'll drive through several settlements, including the beautiful city of Hot Springs and part of the historic town of Deadwood, before completing our delivery at a wood processing depot.
This route is just a small preview of what South Dakota has to offer, featuring winding mountain roads, charming communities, and diverse scenery. Whether you're taking in the views or making deliveries across the state, there's plenty to discover behind the wheel.
We hope you enjoy this gameplay preview and the stunning scenery South Dakota has to offer. As always, please keep in mind that everything you see is still a work in progress and subject to change during development.
If you like what you see, be sure to add the South Dakota DLC to your Steam Wishlist. Don't forget to follow us on Twitter, Facebook, Instagram, Bluesky, and YouTube, or sign up for our newsletter. Until next time, happy haulin'!
Fixed Firefox becoming unresponsive when clearing browsing history, which could also result in site data being lost. (Bug 2059647)
Reference link to 153.0.3 release notes.
This new alpha build introduces 8 new effects, fixes some crashes and other glitches, fixes compatibility with some old plugins, and adds some debugging options to assist with the WINE effort.
You can read more about 5.2 and what it includes by reading the release notes for the first alpha.
The new effects will be discussed more in the final release notes for 5.2, when the time comes, but here are some previews for now. Each new effect is also available for plugins to use in their Direct2D effect graphs.
Original Image
Linocut
Mosaic
Pointillism
Stained Glass
Ordered Dither
Spherize
(This isn’t actually a very good image to use for showcasing this effect. I’ll have a better example for the final release notes.)
Waves
Here are several examples for this one, which has many different modes you can experiment with:
Halftone
Change Log
Changes since 5.2 Alpha (build 9688):
Download and Install
This build is available via the built-in updater as long as you have opted-in to pre-release updates. From within Settings -> Updates, enable “Also check for pre-release (beta) versions of paint.net” and then click on the Check Now button. You can also use the links below to download an offline installer or portable ZIP.
You can also 
download the installer here (for any supported CPU and OS), which is also where you can find downloads for offline installers, portable ZIPs, and deployable MSIs.
We are pleased to announce the fifth release candidate preview release of Jellyfin 12.0!
This is a preview release, intended for those interested in testing 12.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Starting with this release, we are dropping the preceding 10. from our versioning. Thus, 10.11.x -> [10.]12.x = 12.x. The reason is simple: at this point in the project, we don't envision a hard break in the API like we planned way back in the early days, and this version scheme was causing a lot of confusion amongst users about what a "major" release was. For more information, please see the RC1 release notes.
The main goal of this release has been performance. 10.11.0 dropped a major backend rewrite, and while it was broadly functional, it had a lot of rough edges. This release seeks to polish out most of those rough edges and bring better performance to all users.
There are many other small fixes, improvements, changes, and translations. See our draft release notes here or below for the full list of pull requests. You can also view the Server side changelog here.
Note: You must be on Jellyfin 10.10.7+ or 10.11.x (ideally, 10.11.11) before upgrading! If you are not, the upgrade will fail. Ensure you upgrade to one of these versions first!
Note: The initial load of Jellyfin 12.x will run a few migrations and will take several minutes. Please be patient and do not interrupt the process. You can leverage the (newly improved!) startup UI on your local network to see specific progress, or off-network to see general progress, by visiting the server URL in your web browser during startup.
Note: If you install the RC, you should disable all external plugins and reinstall using the unstable plugin repository, or plugins may fail to load and cause unintended side effects.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
12.0-rc5 or preview tags.v12.0-rc4)Full Changelog: v12.0-rc4...v12.0-rc5
We are pleased to announce the fifth release candidate preview release of Jellyfin 12.0!
This is a preview release, intended for those interested in testing 12.0 before its final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Starting with this release, we are dropping the preceding 10. from our versioning. Thus, 10.11.x -> [10.]12.x = 12.x. The reason is simple: at this point in the project, we don't envision a hard break in the API like we planned way back in the early days, and this version scheme was causing a lot of confusion amongst users about what a "major" release was. For more information, please see the RC1 release notes.
The main goal of this release has been performance. 10.11.0 dropped a major backend rewrite, and while it was broadly functional, it had a lot of rough edges. This release seeks to polish out most of those rough edges and bring better performance to all users.
There are many other small fixes, improvements, changes, and translations. See our draft release notes here or below for the full list of pull requests. You can also view the Web side changelog here.
Note: You must be on Jellyfin 10.10.7+ or 10.11.x (ideally, 10.11.11) before upgrading! If you are not, the upgrade will fail. Ensure you upgrade to one of these versions first!
Note: The initial load of Jellyfin 12.x will run a few migrations and will take several minutes. Please be patient and do not interrupt the process. You can leverage the (newly improved!) startup UI on your local network to see specific progress, or off-network to see general progress, by visiting the server URL in your web browser during startup.
Note: If you install the RC, you should disable all external plugins and reinstall using the unstable plugin repository, or plugins may fail to load and cause unintended side effects.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
12.0-rc5 or preview tags.v12.0-rc4)Full Changelog: v12.0-rc4...v12.0-rc5
