v1.10.37 - Backend developer documentation now says where end-to-end tests run #
A maintenance release that corrects Flopay's internal developer documentation about when the backend's end-to-end tests run, with no change to checkout, payments or the public API.
21 Oct 2026
Maintenance
Flopay's internal developer documentation and code comments said that the backend's end-to-end and browser tests ran automatically before a change was merged. In fact developers run them by hand against a local environment. The documentation now says so, so nobody relies on a check that does not run.
What changed
- Developer documentation and code comments now say that the end-to-end and browser tests run only locally, not automatically before a change is merged.
- The checks that run automatically before every merge are unchanged: code checks, every backend unit test, and a build of each backend service.
Why it matters
- The documentation now matches the checks a change actually passes before it reaches merchants.
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.