8.0.0 roadmap

[gulien]

Hello folks 👋 ,

I'm planning to release Gotenberg 8.0.0 before the end of the year. It will be a "light" release, i.e., if you're using the latest 7.x version, all you'll have to do is remove the deprecated flags, form fields and so on. Checking your Gotenberg instance(s) logging entries should be enough to know if you're using any deprecated features 👍

7.10.0

• Use Debian 12 (a.k.a. bookworm) and latest LibreOffice version (LibreOffice newer versions stability issues #576 - done in fix: LibreOffice newer versions stability #697).
• "Stateful" Chromium, i.e., only one long-running browser instance in order to prevent too much memory leaks (Memory leak Chrome #642) and ease the scalability strategy (done in fix: chromium memory leaks #705).
• Switch LibreOffice module to same "supervisor" as Chromium (done in chore(libreoffice): switch to supervisor #708).
• Edge release: a push on main branch now triggers the build of gotenberg/gotenberg:edge and gotenberg/gotenberg:edge-cloudrun. Good to know: the live demo is based on this new version.
• Fix armhf build (Chromium not working on armhf after version 116.0.5845.180-1~deb12u1 #709).
• Refactor convert method from PDF engines to be more generic (no more PDF format, but PDF Archive, PDF UA, etc.).
• Refactor godoc and tests.
• (optional) Replace unoconv with a new unoconverter Python project.

8.0.0

• Remove all deprecated features (done in feat: remove deprecated stuff #726).
• Chromium: capture screenshots (done in feat(chromium): capture screenshot #765).
• Chromium: performance mode, e.g.,skipNetworkIdleEvent (done in feat: skip networkIdle event #749).
• Chromium: return error if status code does not match a specified value (Propagating error in chromium module #613 - done in feat(chromium): return 409 Conflict if HTTP status code from main page is not acceptable #755).
• Chromium: flag to clear cache after each request (panic: cannot create context from nil parent #753 - done in feat(chromium): flags for clearing cache/cookies between each conversion #756).
• Set to v8 (done in chore: upgrade to v8 #767).

---

Do you want to help? Consider testing gotenberg/gotenberg:edge, thanks!

[bedla]

Hi, I have a question: do you some plans to take a look into vulnerabilites detected in the image?

docker run aquasec/trivy image gotenberg/gotenberg:latest

Anyways, thx for your project :)
Ivos

[gulien]

Dependencies will be updated so I guess it will take care of « vulnerabilities ».

[stumpylog]

Regarding deprecated flags/options, is there an API to check the version of Gotenberg a client is communicating with? I maintain a little library for talking to Gotenberg, so the version might be basically anything somewhat recent, depending on the user.

[gulien]

Best option is to release a major version of your client. For instance, gotenberg/gotenberg-php 1.x will not be compatible with Gotenberg 8, but 2.x will.

[stamahto]

Can you please consider adding a CORS option env into docker image to make the server callable from a web browser. Now it can only be called by developers making their own backend API that calls Gotenberg. That means a lot of extra work to do and in addition, 2 containers must be running for one purpose.
See #713

[gulien]

Gotenberg should not be exposed to the external world, you'll make your internal network vulnerable. See https://infosecwriteups.com/0-day-bug-breaks-multi-million-dollar-system-38c9e31b27e9.

[maj2c]

Hi,
First of all thank you for the great job and making it available for everybody :)
Is it possible to make a docker release with latest features but based on Debian 11 instead of 12?
The cloud host I am using does not support Debian 12. Thus, I am forced to stay on release 7.9.2-cloudrun.
Thank you in advance.

[gulien]

Hello @maj2c 👋 I don’t want to create additional release with another Debian version, because the Go code and the Dockerfile dependencies are quite interdependent.