Repository navigation
docs(migration): Add the other v1.56.0 upgrade notes - #775
Conversation
Changelog triage — possible changelog entryThis PR documents several real product/behavior changes for self-hosted users upgrading to v1.56.0: expiring document download links (new This is an unattended triage run, so I'm not drafting an entry — just flagging it. If a human wants one written, reply here or invoke the
Two things that would need resolving before a draft is ready:
Generated by Claude Code |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
52ba9ec to
e491d91
Compare
The dedicated webhook alert worker is not ready for self-hosted use yet, so SIDEKIQ_WEBHOOK_ALERT is no longer documented.
|
Thanks @vincent-pochet for the review! |
Context
The v1.56.0 migration page covers the two changes that reject requests (the v1 page size limit and the customer text field limits). The same release has other changes that self-hosted users should check before or after upgrading.
Description
A new "Other changes to check" section was added to the v1.56.0 migration page:
/documents/...path. The section covers the expiry rules, the410response, the old links andLAGO_LEGACY_DOCUMENT_URLS_EXPIRE_AT, and what to check in integrations that storefile_urland in reverse proxies.LAGO_TRUSTED_PROXIESfor proxies with a public address and the optional throttling Redis.LAGO_FRONT_URLto match the front-end URL.LAGO_GRAPHQL_INTROSPECTION_ENABLEDis set.422, and the optional past and future limits.GET /api/v1/organizations/grpc_tokenendpoint.The new optional environment variables are grouped in one table.
The page also covers the new
getlago/frontimage, which runs nginx as a non-root user on port8080(8443for TLS) instead of80: a third change in the introduction, and a fourth step that lists what a custom Compose file, Kubernetes manifest, reverse proxy or nginx config must change (thedocker-compose.ymlof the Lago repository is updated in getlago/lago#836).The environment variables reference of the self-hosted Docker page now lists the variables added in v1.56.0, with
LAGO_REDIS_CABLE_URLandLAGO_REDIS_CABLE_PASSWORD, which were not documented. TheLAGO_FRONT_URLrow also says that it is used to check the origin of WebSocket connections.Part of BIL-813