Skip to content

Blog: announce 2.5.0 and 2.5.1 - #45

Merged
lambda2 merged 1 commit into
masterfrom
blog/2-5-releases
Sep 10, 2026
Merged

Blog: announce 2.5.0 and 2.5.1#45
lambda2 merged 1 commit into
masterfrom
blog/2-5-releases

Conversation

@lambda2

@lambda2 lambda2 commented Sep 10, 2026

Copy link
Copy Markdown
Member

Two release posts. docs.trefle.io/blog currently stops at 2.3.0 — 2.4.0, 2.5.0 and 2.5.1 are all missing.

2.5.0 (blog/2026-09-09-2-5-0.md) opens by covering 2.4.0, which was never announced, following the precedent of the 2.3.0 post that covered 2.2.0 alongside it. It then covers the substantial part: sources[].licence, the /citation page and CITATION.cff, terms acceptance, the /api/v1/corrections endpoints that returned 500 on every filter and order key, filter_not[image_url]=null on the search paths, the plants N+1, public completion_ratio, the rebuilt website, and the dependency work.

2.5.1 (blog/2026-09-10-2-5-1.md) is short: the terms gate was blocking the terms page itself, and WFO was missing its licence. It also records that WCVP is the authority on accepted names, and the autonym distinction, since both change what readers can expect from the data.

Notes on the writing

  • Written for API consumers, not as a changelog. Each item says what changed in the payload or the behaviour, not which pull request did it.
  • The licence section says explicitly that null means "not verified", not "unencumbered" — the migrator only seeds confirmed licences and never guesses, and readers should not infer permission from a blank field.
  • The 2.5.1 post states the terms defect plainly rather than softening it. It also states that API access was never gated, because that is the first thing a token holder will want to know.

Verification

yarn build succeeds and both pages are generated:

build/blog/2-5-0-released
build/blog/2-5-1-released

Note for anyone building locally: this repo needs yarn 1.x. Yarn 4 (which volta selects by default here) fails to resolve the lockfile — npx -y [email protected] build works.

2.4.0 was never announced, so the 2.5.0 post opens by covering it, the
way the 2.3.0 post covered 2.2.0 alongside it.

Written for people who consume the API rather than as a changelog: what
changed in the payloads, which endpoints stopped returning 500s, and what
the new licence fields do and do not promise. The 2.5.1 post is short and
says plainly that the terms gate was blocking the terms themselves.
@lambda2
lambda2 merged commit a143edb into master Sep 10, 2026
1 check passed
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.

1 participant