Part-DB now requires PHP 8.2 or higher. It is recommended that you read the upgrade guide from v1 to v2 before upgrading.
Part-DB 2.0.2
This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.
Bug fixes
Properly pass environment variables to Part-DB in jbtronics/partdb1 docker image to prevent startup issues (issue #1006)
Improvements
Updated translations
Do not pollute docker error logs with deprecation notices
UpSnap is, and always will be, free and open source software.
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
Part-DB now requires PHP 8.2 or higher. It is recommended that you read the upgrade guide from v1 to v2 before upgrading.
Part-DB 2.0.1
This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.
Bug fixes (compared to 2.0.0)
Fixed broken english translations
Fixed problem that wrong column was sorted after columns were reordered in a table
Part-DB now requires PHP 8.2 or higher. It is recommended that you read the upgrade guide from v1 to v2 before upgrading.
Part-DB 2.0.0
This upgrade introduces a new web based configuration system. Existing configuration using environment variables will continue to work. If you want to configure these parameters via the WebUI in the future, an additional migration step is required. See the upgrade guide for more information.
Breaking changes
Part-DB now requires at least PHP 8.2 or higher. If you are still using PHP 8.1 you need to upgrade PHP first
Nodejs 20 or higher is now required
The config/banner.md file does not exist anymore. If you wanna customize the banner, either do it via the WebUI or the BANNER env.
The parameters partdb.sidebar.items, partdb.sidebar.root_node_enable and partdb.sidebar.root_expanded in config/parameters.yaml,
were removed. You can configure them now directly in the admin interface.
New features
Introduced capability to configure system settings and info providers via the WebUI. No need to work with environment variables anymore
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
Tip
There is a new experimental docker image, which is much faster. See this post for more info.
Tip
You can help to translate Part-DB to other languages. See this post for more info.
Bug fixes
Pass the proxy related settings to the docker application (issue #1001)
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🧪 new features
new option chdir to change the PWD (process working-directory) before volumes are mapped 14555d5
🩹 bugfixes
fix using empty folders as statefile storage (v1.19.6 made this a bit too strict) 0d96786
holding I/K to scroll through folders quickly now works better 914686e
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
Fixed Content Versioning to correctly merge relational data and support all query parameter functionality (#25437)
The following changes should be kept in mind when updating:
Relational versioned data now requires explicit field expansion to be included in the response.
Invalid data (e.g. Fails validation rules) will error on query
Filter conditions now apply to the versioned data instead of the main record
For more information, please read the breaking change docs for a full list of changes.
Additionally there will be further breaking changes to USER_CREATED, USER_UPDATED, DATE_CREATED, DATE_UPDATED default values in a followup PR to improve this behavior further.
Check in with #25744 to see more info about the breaking changes.
✨ New Features & Improvements
@directus/api
Fixed Content Versioning to correctly merge relational data and support all query parameter functionality (#25437 by @Nitwel)
@directus/app
Fixed links in WYSIWYG missing underline and pointer cursor styling (#25739 by @Abdallah-Awwad)
Added a new field to conditions for clearing hidden fields on save (#25646 by @robluton)
🐛 Bug Fixes & Optimizations
@directus/app
Fixed timestamp fields being incorrectly marked as changed due to timezone mismatch (#25718 by @khanahmad4527)
Fixed code button state not updating when exiting code mode in WYSIWYG (#25741 by @Abdallah-Awwad)
Added currentItem id check to prevent in-flight api call from returning stale data (#25660 by @robluton)
UpSnap is, and always will be, free and open source software.
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
UpSnap is, and always will be, free and open source software.
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
UpSnap is, and always will be, free and open source software.
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
UpSnap is, and always will be, free and open source software.
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
Negative side-effect: users of the option to automatically mark updated articles as unread will once have some articles with enclosures re-appear as unread
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
ℹ️ this upgrade is a one-way ticket
your up2k database (.hist/up2k.db), used by the e2d filesystem indexing feature, will be upgraded to a new format which older copyparty versions cannot read. A backup of each database will be created automatically, named up2k.db.bak.SOMETHING.v5. If you need to downgrade to a previous version: Shutdown copyparty, delete these files: up2k.db up2k.db-shm up2k.db-wal and then copy up2k.db.bak.*.v5 to up2k.db
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🧪 new features
#511 login with username and password (not just password) can now optionally be enabled with --usernames346515c
if you have enabled password hashing (ah-alg: argon2 or similar) then you will need to hash your passwords again after enabling usernames, hashing them as username:password:
introduce copyparty-en.py, english-only edition of copyparty-sfx.py to save space 33497e6
🗿 known issues
the copyparty.pyz in this release is english-only, and does not include the translations -- they got lost in transit while adjusting the buildscripts to make copyparty-en.py
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🩹 bugfixes
#354 fix copyparty-sfx.py failing to start on certain versions of python c17ce48
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🧪 new features
#265 uid/gid for new files can be configured per-volume f195998
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🧪 new features
#201 add support for reflink-based dedup on cow filesystems df9feab
combine --dedup with --reflink to enable, or volflags with same name
a better and safer alternative to the other dedup approaches (symlink/hardlink), but only possible to use in some cases:
needs linux 5.3 or newer, python 3.14 or newer, btrfs/xfs/zfs
not available in the docker images yet; needs a new version of python, so maybe next alpine release (november/december 2025)
ratelimit password changes to impede bruteforcing a2601fd
limit is set by --ban-pwc (default is 5 changes in 60min)
there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-07-28)
⚠️ ATTN: this release fixes an XSS vulnerability
GHSA-9q4r-x2hj-jmvr, exploitable in two different ways, could let an attacker execute arbitrary javascript on other users:
either: tricking someone into clicking a malicious URL to load and execute javascript
or: uploading a malicious audio file to the server, affecting any successive visitors
so, with new and curious eyes on the project, we are starting off with a bang. Huge thanks to @altperfect for finding and reporting this earlier today.
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
🧪 new features
#214 option to stop playback after one song, and/or at end of folder 6bb27e6
v1.14.3 (2024-08-30) fixed a bug that was introduced in v1.13.8 (2024-08-13); this bug could lead to data loss -- see the v1.14.3 release-notes for details
Log in
