Add Version (/version) Route

[Jaben]

Add Version (/version) Route

[stumpylog]

I do think it could be useful going forward. My own rough plan currently is the next version supports Gotenberg 8 only, and to flag it as a breaking change for users of paperless, since that is about the only way I can really notify folks they will need to update.

But with a version route, it would be possible to (in the future) translate between things a little bit more while the users get updated to the newer versions.

[gulien]

Done in 2267c5b.

The route /version directly returns the version in text/plain. Please note that not all Gotenberg variants have a semver version. For instance, the demo instance will return {gotenberg_version}-live-demo-snapshot.

The gotenberg/gotenberg:edge tag should be available within ~1hour with this new feature.

[gulien]

Looks like it’s a recurring demand from client maintainers (ping @stumpylog) 😅 I still believe it’s better to have a specific client version per Gotenberg version, or, a client configuration that enables compatibility with a particular Gotenberg version.

Anyway, as it seems helpful, I’ll implement it 👍

[Jaben]

Looks like it’s a recurring demand from client maintainers (ping @stumpylog) 😅 I still believe it’s better to have a specific client version per Gotenberg version, or, a client configuration that enables compatibility with a particular Gotenberg version.

Anyway, as it seems helpful, I’ll implement it 👍

Thank you! The version check will help with mismatched API problems that would otherwise be tough to track down.

[Jaben]

Great -- thanks!