changelog

A project's releases, mirrored into the venture's own database and served over an API.

With fz, into the venture manifest

fz add changelog

With cargo

cargo add cratefield-module-changelog

fz runs inside your venture repository, linked against its own harness. About fz

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/

    The releases, newest first

  • GET/v1/changelog/{version}

    One release, or 404

  • POST/v1/changelog/admin/refresh

    admin tokenPull from upstream

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.

  1. 0.3.3

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
  2. 0.3.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
3 earlier versions 0.2.1 to 0.3.1
  1. 0.3.1

    crates.ioReleaseDiff

    Fixed

    • thirteen error-handling defects, plus make the guard-script tests survive a non-executable checkout (#828)
  2. 0.3.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.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
  3. 0.2.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

Mirrored locally, so the page does not depend on someone else's uptime.