v1.10.35 - Backend releases are checked and delivered from Flopay's own build service #
A maintenance release that moves the automated checks, release and delivery of Flopay's backend to Flopay's own self-hosted build service, with no change to checkout, payments or the public API.
20 Oct 2026
Maintenance
Every change to Flopay's backend is checked before it is merged, released with a version and release notes, and then delivered to production and to the staging environment. That work now runs on Flopay's own self-hosted build service instead of a third-party one.
What changed
- The checks a change must pass before it is merged are the same: code checks, every backend test, and a build of each backend service.
- A release is still versioned and given release notes in the same way, and is delivered to production only after those checks pass on the exact released code.
- Database updates still run before any service of a release starts, and the services that process background work are still updated before the API.
- The staging environment now receives each change straight from the released code, after production.
Why it matters
- Releases and their checks no longer depend on a third-party build service, so fixes reach merchants on infrastructure Flopay runs itself.
Developer notes
- No public API endpoint, request or response field, webhook payload, SDK export, or documented configuration changed.
- No merchant action is required. This release contains no breaking changes.