Blog: announce 2.5.0 and 2.5.1 - #45
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two release posts.
docs.trefle.io/blogcurrently 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/citationpage andCITATION.cff, terms acceptance, the/api/v1/correctionsendpoints that returned 500 on every filter and order key,filter_not[image_url]=nullon the search paths, the plants N+1, publiccompletion_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
nullmeans "not verified", not "unencumbered" — the migrator only seeds confirmed licences and never guesses, and readers should not infer permission from a blank field.Verification
yarn buildsucceeds and both pages are generated: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] buildworks.