tobogganSe connecter

packages

The Louise packages, each released on its own

Clone avec HTTPS, un jeton personnel en mot de passe, ou avec SSH, une clé ajoutée dans vos paramètres.

18 lignes · 1286 octetsBrut · Historique

Releasing a package

A release of a package is its [package] version and the annotated tag <package>-v<version> at the commit that has it, whose message is the release notes. Releasing json tags json and nothing else.

  1. In a pull request: bump version in <package>/louise.toml, and add the release's entry at the top of <package>/CHANGELOG.md. If the package now needs a newer release of a sibling, raise that requirement too, and release the sibling first.

  2. Merge it, then tag the merged commit and push the tag:

    git fetch origin && git checkout origin/main
    git tag -a json-v0.21.1 -F notes.md   # "json 0.21.1", then the changelog entry
    git push origin json-v0.21.1
    
  3. The tag's workflow (release.yml, scripts/check-tag.sh) checks that the manifest at the tag says that version, and that every versioned requirement of the package has a release that satisfies it. If it fails, delete the tag, fix, and tag again.

What the version says:

  • A fix or an addition that keeps every program building: the patch (0.21.0 → 0.21.1). Apps take it with louise update <package>.
  • A breaking change: a new line, the minor while in 0.x (0.21 → 0.22). A package or an app on ~> 0.21.x does not take it until it raises its requirement.