Skip to content

docs(migration): Add the v1.57.0 migration page - #779

Merged
annvelents merged 1 commit into
mainfrom
docs/payment-terms-migration
Nov 5, 2026
Merged

annvelents merged 1 commit into
mainfrom
docs/payment-terms-migration

Conversation

@annvelents

Copy link
Copy Markdown
Contributor

Context

Flexible payment terms store the term in a new payment_term field. getlago/lago-api#6142 copies the existing net_payment_term into it:

  • billing entities, through a database migration that runs when the API starts;
  • customers, through the migrations:backfill_customers_payment_term rake task, which enqueues a batched background job.

The customers task must be finished before the release that reads customers.payment_term (lago-api#6195).

Description

  • New guide/migration/migration-to-v1.57.0.mdx: what changes, why, and the self-hosted steps (install, run the task, check it finished, then upgrade).
  • Adds the page at the top of the Migrations group in docs.json.

To check before merging

  • The version: v1.57.0 is assumed to be the first release containing lago-api#6142 (the latest tag is v1.56.0).
  • Step 4 does not name the release that ships flexible payment terms yet.

Self-hosted users must run migrations:backfill_customers_payment_term after installing v1.57.0, and wait for it to finish before upgrading to the release that introduces flexible payment terms.
@mintlify

mintlify Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
lago-docs 🟢 Ready View Preview Nov 5, 2026, 2:19 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@annvelents
annvelents merged commit 681a738 into main Nov 5, 2026
2 checks passed
@annvelents
annvelents deleted the docs/payment-terms-migration branch November 5, 2026 14:37

This branch was successfully deployed

1 active deployment
staging — 5c96b59e Deployed Nov 5, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants