The 2.9 line went out in nine small releases in October, from 2.9.0 to 2.9.8. Most of the work sits behind the data: the October audit that aligned our names with Kew's checklist, the first trait import from TRY, and a back office that can keep up with the corrections both produce.

The API reference has been updated. This release also carries the performance and hardening work from the last two weeks — including one change to pagination that clients paging very deep need to know about.

Two fixes for defects that shipped with 2.5.0, one of which was doing exactly the opposite of what it was for.

The largest release since Trefle came back. The website has been rebuilt, every upstream source now declares its licence in the API, and a family of endpoint bugs that had been returning 500s went out with it.

Two releases since the last post. 2.1.0 introduced provenance — recording which source each value came from. 2.2.0 and 2.3.0 are about making that recording mean something: deciding which source wins when they disagree, and letting you watch the dataset improve day by day.

Version 2.1.0 is in production. It delivers the most requested feature in Trefle's history — CORS — and starts a longer journey: making every value in the database traceable to its source.

Trefle went quiet for a couple of years. It is back: the whole stack has been modernized and redeployed, and version 2.0.2 is now running in production.

This major release of Trefle brings a lot of new exciting features, such as distributions, farming fields and blazing fast search.