Paperless-ngx 3.5.0 upgrade: async bulk edits, no breaking changes seen

released
lab run
upgraded from
3.4.2
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

Paperless-ngx 3.5.0 adds a manual workflow trigger, renders document notes as markdown, and moves bulk operations to run in the background. It also clears old sessions automatically. The release notes list 32 app changes, most of them fixes.

Breaking changes and deprecations

The release notes have one note at the top: some users may need to adjust their PAPERLESS_ALLOWED_HOSTS setting. A fix to the allowed_hosts default is in the same release (#14735).

Other changes that may affect you (reported in the release notes, not all tested by us):

  • Bulk operations now hand off to async tasks (#14773, #14711).
  • Some OCR user arguments that Paperless uses itself are now blocked (#14734).
  • Tags moved from django-treenode to an adjacency-list model (#14612).

Tested in our lab

We installed 3.4.2 with the official SQLite Docker Compose file, then upgraded to 3.5.0 using the documented steps. We stopped the stack with docker compose down, changed the image tag, pulled and started it again.

  • Before: version 3.4.2, one tag, one document consumed from a text file.
  • After: the stack came up healthy and reported version 3.5.0. The document, its content and the tag were all still there.
  • A new upload after the upgrade was consumed. A bulk “add tag” call returned a task ID. Both documents had the tag afterwards.
  • We found no errors or tracebacks in the container log after the upgrade.
  • A request with a made-up Host header (paperless.example) still returned 200 on the login page. We ran this with the default settings only, with no PAPERLESS_ALLOWED_HOSTS set.

A note on installing: the 3.4.2 compose env file did not set PAPERLESS_SECRET_KEY, and the container kept restarting with an ImproperlyConfigured error until we added one. The sample files may change, so set your own key if you copy them.

We did not test PostgreSQL or MariaDB, the AI chat, mail accounts, the manual workflow trigger, or a large library.

Lab log

$ docker compose down
[...]
 Network pl_default Removed
$ docker compose pull
[...]
 Image ghcr.io/paperless-ngx/paperless-ngx:3.5.0 Pulled
$ docker compose up -d
[...]
 Container pl-webserver-1 Started
$ docker compose ps --format "{{.Service}} {{.Image}} {{.Status}}"
broker docker.io/valkey/valkey:9-alpine Up 40 seconds
webserver ghcr.io/paperless-ngx/paperless-ngx:3.5.0 Up 40 seconds (health: starting)
$ curl -s -u admin:[redacted] http://localhost:8000/api/documents/?fields=id,title,content
{"count":1,"next":null,"previous":null,"results":[{"id":1,"title":"LabDoc","content":"Invoice 42\nLab test document for upgrade\n"}]}
$ curl -s -u admin:[redacted] -H "Content-Type: application/json" -d '{"documents":[1,2],"method":"add_tag","parameters":{"tag":1}}' http://localhost:8000/api/documents/bulk_edit/
{"result":"OK","task_id":"c4c60106-de7e-4d7d-861f-0ce35bce0c8c"}
$ curl -s -u admin:[redacted] http://localhost:8000/api/documents/?fields=id,title,tags
{"count":2,"next":null,"previous":null,"results":[{"id":2,"title":"PostUpgrade","tags":[1]},{"id":1,"title":"LabDoc","tags":[1]}]}

Reported by others

Nothing beyond the release notes. We did not search for user reports.

Verdict

Upgrade now. In our small SQLite Docker test, the upgrade from 3.4.2 was uneventful and kept our data. If you set PAPERLESS_ALLOWED_HOSTS, read the note in the release first. Take a backup before upgrading, as always, especially on a large library or PostgreSQL, which we did not test.

sources

other Paperless-ngx releases