Skip to content

itos 8.3.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 18:42
v8.3.2
e284f2f

itos 8.3.2

Cut by CI from the 50 commits since v8.3.1: 0 feats, 1 fix and 0 breaking changes, where a breaking change makes a major release, a feat a minor one and a fix a patch. Every change: v8.3.1...v8.3.2

What changed

Fixes

  • Name the line the footer-leading-blank warning reads as the footer (ccb5d89)

Tests

  • Cover a breaking-change note that runs on in the footer warning (e284f2f)

Build

  • Run the doc budget in pre-commit when a capped file is staged (d100b77)

CI

  • Ask the Go module proxy for each new release (75fb980)
  • Lower ARCHITECTURE.md's doc budget to 12000 bytes (0f3f2ac)
  • Hold the pre-commit doc budget to the gates self-test (b8fe627)

Documentation

Upgrading

Commit these changes as your project's rules ask (the install script and the pin are build
commits, or whatever type your rules give itos.yaml and tools/bin/).

  1. What the commits ask. No commit since v8.3.1 is a breaking change. Every feat and fix since v8.3.1 says Upgrading: none.

  2. What it changes on purpose. The old scenarios and conformance cases the range's Changes: footers name,
    which a fix changes because they held the bug (T-071):

    • ccb5d89 fix: name the line the footer-leading-blank warning reads as the footer: messages.yaml: the built-in lint's warnings are printed and do not reject the message

  3. The config. No key, type, value or default changed since v8.3.1: a config it accepts, this release
    accepts and reads the same (tools/bin/schema-contract, T-070).

  4. Move the install script to 8.3.2. A project on the install script
    (tools/bin/install-itos, v2.0.0's Upgrading, step 1) changes its version= line and each
    platform's hash, from this release's checksums.txt; the whole script, for a project that has
    none yet:

    #!/bin/sh
# tools/bin/install-itos: the pinned itos, into .tools/bin/
set -eu
version=8.3.2
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=8ffc99533a39038fed52fdea9cd591e4632b0688ca07b3291380ae7b1f3f983f ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=762414f923007226e7c0a8923d7d8c0f8ab803dc43c10ee73e15339e6ad47a23 ;;
Darwin-x86_64) platform=darwin-amd64 sum=aabd1fcb4f6f835f1807cc9b0ca5a1edee35af401f9da5d8cf53f46588a44f1d ;;
Darwin-arm64) platform=darwin-arm64 sum=4e61f4f4252076a01c322835170509be4ffeed234e86425c7f2e2cd7f45a6aa0 ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=858ee5460025bc95cbe3cd5320722c49285d9b3d4d67f888cceb887d3e99bf1d ;;
*) echo "install-itos: no itos archive for $(uname -s)-$(uname -m)" >&2 && exit 1 ;;
esac
case "$platform" in
windows-*) archive="itos-$version-$platform.zip" bin=.tools/bin/itos.exe ;;
*) archive="itos-$version-$platform.tar.gz" bin=.tools/bin/itos ;;
esac
# What was installed, so a call with nothing to do runs nothing.
pin=".tools/bin/itos.pin"
if [ -x "$bin" ] && [ "$(cat "$pin" 2>/dev/null)" = "$version $sum" ]; then exit 0; fi
tmp=$(mktemp -d)
trap 'rm -rf "$tmp"' EXIT
curl -fsSL -o "$tmp/$archive" "https://github.com/donvargax/itos/releases/download/v$version/$archive"
if command -v sha256sum >/dev/null; then check="sha256sum -c -"; else check="shasum -a 256 -c -"; fi
(cd "$tmp" && echo "$sum  $archive" | $check)
mkdir -p .tools/bin
case "$archive" in
*.zip) unzip -o -q "$tmp/$archive" itos.exe -d .tools/bin ;;
*) tar -xzf "$tmp/$archive" -C .tools/bin itos ;;
esac
echo "$version $sum" > "$pin"
echo "install-itos: itos $version in $bin"

  5. Or move the pin to 8.3.2. A repository that pins a release in itos.yaml
    (v2.1.0's Upgrading, step 2) changes its two lines; pin.checksums is the SHA-256 of this
    release's checksums.txt itself, one hash for every platform:

    pin:
  version: 8.3.2
  checksums: 9e290fbe9b5d631ae007d16be0aa934ae5dcbb44a96ca1a0ea5ba57296ca627f

    A CI step that installs itos by go install moves to
    go install github.com/donvargax/itos/v8/cmd/itos@v8.3.2.

  6. Point the schema line at v8.3.2's. If itos.yaml's first line names a release's
    itos.schema.json, make it
    # yaml-language-server: $schema=https://github.com/donvargax/itos/releases/download/v8.3.2/itos.schema.json.

  7. Check: tools/bin/itos version (or itos version in the repository, with a pin)
    prints itos 8.3.2, tools/bin/itos version --check exits 0 (widen a cap in
    requires that 8.3.2 is past), and tools/bin/itos config check passes. To report a
    problem itos causes, open an issue on donvargax/itos with the label consumer-report
    (https://github.com/donvargax/itos/issues/new?template=consumer-report.yml).

The archives are attested by the workflow that built them:
gh attestation verify <archive> -R donvargax/itos checks one, and
sha256sum --ignore-missing -c checksums.txt checks the ones downloaded beside it.

Assets 10
Loading