changelog
A project's releases, mirrored into the venture's own database and served over an API.
What it is
changelog.
Releases are fetched from the upstream project and stored in the venture's own database, so the endpoint keeps answering when the upstream is rate limited, slow or down, and a reader is never sent to a third party. A refresh is an admin action rather than a cron nobody watches.
Ports
Database · HttpClient · Clock · KeyValue optional
Routes
/v1/changelog
- GET
/v1/changelog/ - GET
/v1/changelog/{version} - POST
/v1/changelog/admin/ refresh
Note
Rewriting and translating release notes are named in the crate as later work, behind a TextModel port that does not exist yet.
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 5 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core
Other
- updated the following local packages: cratefield-core
3 earlier versions 0.2.1 to 0.3.1
Fixed
- thirteen error-handling defects, plus make the guard-script tests survive a non-executable checkout (#828)
Changed
- Breaking: requires
cratefield-core0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).
Other
- updated the following local packages: cratefield-core
- Breaking: requires
Other
- updated the following local packages: cratefield-core
Mirrored locally, so the page does not depend on someone else's uptime.