Development Build
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
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
Warning
After upgrade, you need to run php bin/console doctrine:migrations:migrate (or equivalent) as webserver user after upgrade.. If you are running a docker container, use sudo docker exec --user=www-data partdb php bin/console doctrine:migrations:migrate, or sudo -E inside the docker container, to ensure that the migrations are applied to the correct database.
Important
Since this version Part-DB can enable foreign key checks for SQLite: it is recommend to do this, but it requires some manual intervention. See this announcement on how to do it: #1486
Note
If you are using Part-DB it would be helpful if you fill out this short survey on your usage of Part-DB (Google Forms): https://forms.gle/Q15twx3YYq3qCNfe8
Full Changelog: v2.14.1...v2.15.0
Updates:
Changes/additions:
%appdata%\MPC-HC. Also added an advanced option to always use appdata folder.HistoryExcludeFilter to exclude certain content from getting added to recent file history. It is a simple semi-colon separated list of substrings that is matched against the full path or URL.HistoryExcludeFilterPrivate setting with exact same purpose, which is not exposed through the user interface.Show History entry to recent file menu. This opens a dialog for managing history entries. Allows you to search. Manually remove entries. Clean invalid entries. Clean old entries. Reset position, etc.Fixes:
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.
Range and If-Range header support on file downloads (RFC 7233) (#2377).url_original expression variable for Url rules.jemallocator crate with tikv-jemallocator (contributed by @checkraisefold).description as label property.FUTURERELEASE HOLDUNTIL uses Unix timestamps instead of RFC 3339 date-times.EmailSubmission/query filtering on undoStatus contradicts EmailSubmission/get, reporting held FUTURERELEASE submissions as final instead of pending.EmailSubmission/get requests without an ids argument iterates the wrong index.Accept: text/vcard version negotiation is ignored whenever another parameter such as q or charset follows version=.text/calendar part outside the multipart/alternative and disposed as an attachment.impersonate permission never have their ACL grants collected, so shared items are never listed in JMAP sessions, CalDAV/CardDAV discovery or IMAP.COPY/MOVE into a shared folder fails with NO [ALREADYEXISTS] when the destination account already holds the message, leaving the message in the source mailbox and clients in a retry loop.BODYSTRUCTURE and ENVELOPE return MIME parameters, Content-Description, subjects and display names as raw UTF-8 even to sessions that never enabled UTF8=ACCEPT.
[An on-line version of this announcement will be available at https://www.postfix.org/announcements/postfix-3.11.6.html]
This release addresses medium-impact problems that need to be fixed as some enable remote DOS or policy bypass.
The fixes below, and more, are also released in the unstable version postfix-3.12-20260809.
In addition to updated releases for the supported Postfix versions 3.8-3.11, releases will also be available for the out-of-support Postfix versions 3.5-3.7. NOTE: these do not include the patches for out-of-support Postfix versions that have been issued for "large SMTP inputs (June 2026)", "TLSA parsing (June 2026)", and "SMTP smuggling fixes". Those patches still need to be applied.
These defects were found by Qualys assisted by Claude Mythos Preview, and by OpenAI Security; more than half date from 20 or more years ago. When I implemented Postfix, I knew that there were going to be mistakes. That is the reason why Postfix has its architecture and safety nets. The number of defects may seem large, but considering that they were found in a code base of over 150 thousand lines, the error rate is still lower than what I designed for.
Policy bypass:
Bug (introduced: Postfix 2.2, date: 20041102): missing SMTP server resets of MAIL FROM and RCPT TO command state after smtpd_end_of_data_restrictions rejected a message. This resulted in SMTP protocol state desynchronization between the remote SMTP client and the Postfix SMTP server.
A crafted remote SMTP client could then send RCPT TO and DATA without MAIL FROM, and deliver a second message. Then, smtpd_end_of_data_restrictions skipped check_recipient_access constraints, because a recipient counter was > 1. Reported by OpenAI Security. File: smtpd/smtpd.c.
As reported by OpenAI Security, the failure to reset MAIL FROM and RCPT TO state also affected Milter support (added in Postfix 2.3). Here, after a Milter replied with "accept this message" based on the message envelope, and smtpd_end_of_data_restrictions rejected the message, the Postfix SMTP server as before accepted RCPT TO and DATA without MAIL FROM, and smtpd_end_of_data_restrictions as before skipped check_recipient_access constraints for the second message. Under these conditions, the Postfix Milter client remained in the "accept this message" state, skipping Milter policy enforcement for the second message.
Denial of service:
Bug (defect introduced: Postfix 3.4, date: 20180805): SMTP server command history memory exhaustion with a large number of very small BDAT requests. Reported by OpenAI security. File: smtpd.c.
Bug (defect introduced: Postfix 1.1, date: 20021116): address verification cache poisoning. A local user could use the postdrop command to submit an address verification probe with envelope or message content that Postfix rejected later, resulting in a negative address verification cache entry for that address. On systems that enable address verification, the negative address verification cache entry would force the Postfix SMTP server to reject a message that it should accept (denial of service). Problem reported by OpenAI Security. File: postdrop.c.
Server crashes and panic()s:
Bug (defect introduced: Postfix 3.4, date: 20180805): missing SMTP server reset of RCPT TO state, after a BDAT command error. A crafted remote SMTP client could then send a DATA command without MAIL FROM or RCPT TO, and crash a Postfix SMTP daemon process with a null pointer read error. Reported by OpenAI Security. File: smtpd/smtpd.c.
Bug (defect introduced: Postfix 2.4, date: 20051222): null pointer read crash while parsing a malformed Dovecot AUTH server response. Reported by Qualys, assisted by Claude Mythos Preview. File: xsasl_dovecot_server.c.
Read after free, uninitialized read, under/over read:
Bug (defect introduced: Postfix 2.8, date: 20100914): read-after-free in the PSC_CALL_BACK_NOTIFY() macro. This had no effect on program execution, because myfree() wiped memory, and that memory was not yet reused. Problem reported by Qualys, assisted by Claude Mythos Preview. File: postscreen_dnsbl.c.
Read after free (no privilege escalation) in debug logging (defect introduced: Postfix 2.2, date: 20050117). Reported by Qualys, assisted by Claude Mythos Preview. File: util/inet_connect.c.
Bug (defect introduced: Postfix 2.10, date: 20120617): uninitialized memory read in postscreen HaProxy client after remote I/O exception, causing garbage to be logged. Reported by Qualys, assisted by Claude Mythos Preview. File: postscreen_haproxy.c.
Latent bug (defect introduced: Postfix 2.7, date: 20090618): uninitialized memory read after dnsblog(8) returns a string that is not an IPv4 address. Reported by Qualys, assisted by Claude Mythos Preview. File: postscreen_dnsbl.c.
Bug (defect introduced: before Postfix alpha, date 19970424): the DNS client could read up to two bytes past the end of an MX record, before discovering that the record was too short. This behavior was later copied with SRV records, potentially over-reading up to six bytes. Problem reported by Qualys, assisted by Claude Mythos Preview. File: dns_lookup.c.
Bug (defect introduced: Postfix 1,1, date: 20010524): the postsuper command under-read or over-read a very short queue filename. No crash, information leak, or privilege escalation. Reported by Qualys, assisted by Claude Mythos Preview. Files: postsuper.c, mail_queue.h.
Other code hygiene:
Bug (defect introduced: before Postfix alpha, date: 19971106): 'int' over-shift, in the queue file record-length parser. Postfix programs do not generate such records, but an attacker could cause postdrop to reject input or panic(). Reported by Qualys, assisted by Claude Mythos Preview. File: record.c.
Bug (defect introduced: Postfix 2.2, date: 20050117): non-transitive comparison of IPv4 addresses. Reported by Qualys, assisted by Claude Mythos Preview. File: sock_addr.c.
Bug (defect introduced: Postfix 1.0, date: 20000928): the fast flush server, used by the SMTP command "ETRN", and by the commands "postqueue -s site" and "postqueue -i queue_id" (and their sendmail(1) equivalents), used the wrong duplicate suppression API, resulting in unnecessary queue scans by the queue manager. Reported by Qualys, assisted by Claude Mythos Preview. File: flush.c.
Queue hygiene: the postdrop command accepted the null record type which the rest of Postfix ignores. Reported by OpenAI Security. File: postdrop.c.
You can find the updated Postfix source code at the mirrors listed at https://www.postfix.org/.

What's the best way to capture the spirit of Ireland? Hit the road, of course! In June, members of our Euro Truck Simulator 2 map team travelled across the Emerald Isle on a research trip for our upcoming Isle of Ireland DLC. With cameras in hand and thousands of kilometres ahead, they explored everything from lively cities and picturesque villages to rugged coastlines and breathtaking scenery, collecting the references that will help shape this exciting expansion. Here are some of their highlights from their journey.
This past May, we shared our vision for the future of Firefox. Starting today, you can try out the next design evolution of Firefox in Nightly.
It’s still Firefox, now with a more cohesive look and feel across tabs, menus, panels, and other browser surfaces. You’ll notice softer tab shapes, a warmer color palette, updated icons, and – after hearing from many of you – the return of Compact Mode and new theme options to make Firefox your own.
Many of you have already spotted pieces of the new design in Nightly over the past few months. Now they’re coming together into one complete experience.
You’ll continue to see updates over the coming weeks as we polish the new Firefox design before it reaches Firefox users more broadly later this year. As you browse, we’re especially interested in any visual or functional issues you encounter.
Keep an eye out for things like:
If something doesn’t look or behave as expected, please file a bug in Bugzilla.
When possible, include:
If you have broader thoughts or questions about your experience, join the discussion on Mozilla Connect.
Thanks for using Nightly and helping us improve Firefox. Every bug report helps us identify issues and continue refining the new Firefox design before it reaches Firefox users more broadly later this year.
![]()
Script to find new contributors from bug list
![]()
![]()
![]()
Script to find new contributors from bug list
![]()
![]()
Script to find new contributors from bug list
![]()
![]()
Script to find new contributors from bug list