Skip to content

itos 8.3.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 17:15
v8.3.0
da2f0ea

itos 8.3.0

Cut by CI from the 12 commits since v8.2.0: 1 feat, 0 fixes 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.2.0...v8.3.0

What changed

Features

  • Let a scenario go live outside feat and fix when named and no code changes (cd35ca3)

Tests

  • Add the steps of a scenario going live outside feat and fix (cb3aedb)
  • Cover the reading of a commit for a scenario going live (0387082)

Documentation

  • Add p1-nightly-report-names-steps (a3096ed)
  • Close slice-133 (d5e8ad1)
  • Queue slice-133 (51db4fe)
  • Add p1-commit-msg-checks-the-index (95ccbe3)
  • Promote p1-moves-going-live to slice-134 (78bec54)
  • Specify slice 134, a scenario going live outside feat and fix (c8aa5ab)
  • Queue slice-134 (d149061)
  • Take slice-134 (da163f2)
  • Add p1-moves-file-wip-going-live (da2f0ea)

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.2.0 is a breaking change.
    Each Upgrading: footer since v8.2.0 (itos commit footers Upgrading v8.2.0 v8.3.0):

    • cd35ca3 feat: let a scenario go live outside feat and fix when named and no code changes:

      to let a scenario go live outside feat and fix, set the moves check's code

  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):

    • cd35ca3 feat: let a scenario go live outside feat and fix when named and no code changes: moves.yaml: an added and a lost live scenario
    • cd35ca3 feat: let a scenario go live outside feat and fix when named and no code changes: moves.yaml: a root commit is judged against the empty tree

  3. The config. Since v8.2.0 (tools/bin/schema-contract, T-070):

    • tests.<key>.range_checks[].code: key added

  4. Move the install script to 8.3.0. 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.0
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=459d3c782aa14723f93331c490fb229622cded545b7758c0425f2fa4e70be6d4 ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=4afd76d7b263fde3478023d83c14ec1fb52c79c2ba42c744aeb2bf1420bbf2a2 ;;
Darwin-x86_64) platform=darwin-amd64 sum=229904cbe247333a3de4b183b46ead1575bdf44ac962d48c052b64676ae92bb6 ;;
Darwin-arm64) platform=darwin-arm64 sum=91518990f790503f69c66cbe4cd0e9df0c82a2ff0081598877a80f39decdf536 ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=fc592c94c5dceaa0d0cefe93c5194de055b0a5c8be24f41f4c999adc386760da ;;
*) 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.0. 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.0
  checksums: 58ace1ab9c33e076da61b307b6277a227f44ce5de47550e1a19d97de49c197da

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

  6. Point the schema line at v8.3.0'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.0/itos.schema.json.

  7. Check: tools/bin/itos version (or itos version in the repository, with a pin)
    prints itos 8.3.0, tools/bin/itos version --check exits 0 (widen a cap in
    requires that 8.3.0 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