Skip to content

Releases: donvargax/itos

Release list

itos 8.4.0

itos 8.4.0 Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 19:46
v8.4.0
7573f74

itos 8.4.0

Cut by CI from the 13 commits since v8.3.3: 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.3.3...v8.4.0

What changed

Features

  • Name the repository's visibility on itos status's main branch line (7573f74)

Tests

  • Give the fake GitHub a repository whose visibility a step sets (1a396ba)

CI

  • Have the corpus's fake GitHub answer a repository's visibility (7767100)

Documentation

  • Close bug-110 (af5f46d)
  • Queue bug-110 (b345852)
  • Add p1-status-repo-visibility (26878bf)
  • Add p1-work-done-absorbed-idea (db2afcc)
  • Add p1-upgrade-names-action-uses (478c476)
  • Promote p1-status-repo-visibility to slice-135 (17fb71d)
  • Specify slice 135, status naming the repository's visibility (f23e550)
  • Queue slice-135 (ecbe1c6)
  • Take slice-135 (2a60248)
  • Add T-169 (fdc999d)

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.3 is a breaking change. Every feat and fix since v8.3.3 says Upgrading: none.

  2. What it changes on purpose. No fix since v8.3.3 names an old scenario or case it changes (Changes:).

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

  4. Move the install script to 8.4.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.4.0
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=181864c5c38f40f0014ae3609174771f17db52bb8e4c067580e1f6aaeccce36a ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=aa5f4f62362f9f9adfd489cdc5a73bfd67124af7c7a384533f461063470c65b9 ;;
Darwin-x86_64) platform=darwin-amd64 sum=c41ef473d8b752069d62107d9d517f1702eb8bce511e7fa3bdfab7f33ecc929d ;;
Darwin-arm64) platform=darwin-arm64 sum=7632ab557cc55b1f41e4935ad45831d80d1fede50b2047a813c670581300a71b ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=58370d4120951cfe340d05664acb467d58b69fe1a9ce2866093327913e48f0d6 ;;
*) 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.4.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.4.0
  checksums: 1a0ca9db1db4279442788fc2c057e6ae19ada391601ae7df1da02da52cd4a2c4

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

  6. Point the schema line at v8.4.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.4.0/itos.schema.json.

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

itos 8.3.3

itos 8.3.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 19:15
v8.3.3
8b47336

itos 8.3.3

Cut by CI from the 9 commits since v8.3.2: 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.2...v8.3.3

What changed

Fixes

  • Read the footers as git reads trailers, the message's last paragraph (8b47336)

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

    • 8b47336 fix: read the footers as git reads trailers, the message's last paragraph:

      footers must be the message's last paragraph, after a blank line, as git reads trailers

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

    • 8b47336 fix: read the footers as git reads trailers, the message's last paragraph: @ID-HEADER-07 @ID-HEADER-08
    • 8b47336 fix: read the footers as git reads trailers, the message's last paragraph: messages.yaml: the built-in lint's warnings are printed and do not reject the message
    • 8b47336 fix: read the footers as git reads trailers, the message's last paragraph: messages.yaml: the footer-leading-blank warning names the line that starts the footer
    • 8b47336 fix: read the footers as git reads trailers, the message's last paragraph: messages.yaml: --json gives the footer-leading-blank warning with the line it names

  3. The config. No key, type, value or default changed since v8.3.2: 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.3. 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.3
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=df3a752de17ea14ba8d78ebc8a843671b03b0f2cfd6105c6a8d30b7e31f3687b ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=5444a776ae420ce71937be9a3fbfa5dd1daaf3e99303397dc41cd481626e3420 ;;
Darwin-x86_64) platform=darwin-amd64 sum=1734ddd56f67368b20bd07e7abe17ba535bb0e47d31738b7dba7185528c5fd50 ;;
Darwin-arm64) platform=darwin-arm64 sum=3a4d030b84c5c155d8daa6746f19e4eaae9f5df53f6b781bd8cd304cc15497f1 ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=6f2d64246ef404b72d6a7b1b3bb24c895bbb799c82b35d2892cd3420b72e0fcd ;;
*) 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.3. 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.3
  checksums: c5138e7d52ec0772112e43bf89faa60ef0ae5515fec5713af8d47a03e2f08e99

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

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

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

Loading

itos 8.3.2

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 i...

Read more
Loading

itos 8.3.1

itos 8.3.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 17:35
v8.3.1
862dc81

itos 8.3.1

Cut by CI from the 11 commits since v8.3.0: 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.0...v8.3.1

What changed

Fixes

  • Refuse a live scenario turned wip outside except_types (862dc81)

Tests

  • Add the steps of a live scenario turned wip (8d27f1f)

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

    • 862dc81 fix: refuse a live scenario turned wip outside except_types:

      outside except_types, turn a live scenario wip in a feat or fix; other types are refused

  2. What it changes on purpose. No fix since v8.3.0 names an old scenario or case it changes (Changes:).

  3. The config. No key, type, value or default changed since v8.3.0: 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.1. 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.1
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=dcb88f7bc0e14726f43a439dfbd1c989690b79c742d83a7e544adef5b3b71017 ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=738a954b23de1bd9460897b0b0f96f99c7e27809e8f6f88a204030d8e206cfa8 ;;
Darwin-x86_64) platform=darwin-amd64 sum=639c49585dedc508225401c7bed8395ff2f37fd5d0ec63031d82e7d9bdc83935 ;;
Darwin-arm64) platform=darwin-arm64 sum=77bc253c0be929234e7a30576181072b59ee9777621e7264004679036ee319fd ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=5c7e25898d9bc25d5120222f1cfd697728ade8855e32dd611fe8fa7cb54af9c6 ;;
*) 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.1. 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.1
  checksums: 8e82e2a3c84306e4cbc13d0cf4d55c60873e5c070d276d4de72035232bed3cd7

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

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

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

Loading

itos 8.3.0

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.

Loading

itos 8.2.0

itos 8.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 15:55
v8.2.0
2e3d4b6

itos 8.2.0

Cut by CI from the 36 commits since v8.1.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.1.0...v8.2.0

What changed

Features

  • Go on past a failing step in the nightly, naming every failure (ecc1ba8)

Tests

  • Add the nightly steps and the nightly run for slice 133's scenarios (06c9828)

CI

  • Run a push's named tests on each platform, every feature nightly (d51c9c9)
  • Hold the nightly to its shape after T-163 in the features-scope self-test (915464f)

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.1.0 is a breaking change. Every feat and fix since v8.1.0 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):

    • ecc1ba8 feat: go on past a failing step in the nightly, naming every failure: ci-run.yaml: with ci.stop_at_first_failure false every step and check runs
    • ecc1ba8 feat: go on past a failing step in the nightly, naming every failure: ci-run.yaml: the same as --json, its verdict the first failure
    • ecc1ba8 feat: go on past a failing step in the nightly, naming every failure: ci-run.yaml: a code proof that finds a survivor fails the run
    • ecc1ba8 feat: go on past a failing step in the nightly, naming every failure: ci-run.yaml: --json keeps stdout for the verdict

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

  4. Move the install script to 8.2.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.2.0
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=534ba5ca053d41e4f47999ace8aa262ef4aaed6a42fa7c0fbc243a0b15c6fa44 ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=a203b5b59cd53e8f2fecc01bf154fb3429dd6a1b3898accd30357de5565eb251 ;;
Darwin-x86_64) platform=darwin-amd64 sum=61eda01fd8f5ab65e8ff8a5ea6211d941e4ac3b0d3ba48883c991175d09f733f ;;
Darwin-arm64) platform=darwin-arm64 sum=fea02116a7a79f1cc2e6df8211fbb2efb02932e9289ce0d85967379e8c078f77 ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=223da897edf3df082b7ae08bb837d7e3bea1c9a2ee9699463b1f87984a6e70ee ;;
*) 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.2.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.2.0
  checksums: 77cc8f76bfaead2f5214b8f842b166233bbcd31d5b50eb9023072c1a0d486747

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

  6. Point the schema line at v8.2.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.2.0/itos.schema.json.

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

Loading

itos 8.1.0

itos 8.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 10:02
v8.1.0
00392ea

itos 8.1.0

Cut by CI from the 51 commits since v8.0.1: 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.0.1...v8.1.0

What changed

Features

  • Run only a range's run of named tests with ci run --tests (00392ea)

Refactoring

  • Name no node_modules in the built-in header lint's comment (28e966e)
  • Leave the id counter no error path a test cannot reach (05fa40a)

Tests

  • Hold init to naming the project's settings only for a project install (0d9e2bd)
  • Run the changed statements no test ran since the 2026-10-08 nightly (d001ba4)
  • Add the step that runs CI's named tests over a range (d7b0543)

Build

  • Delete package.json, its lockfile, tsconfig.json and the changelog script (d253b04)
  • Build the devcontainer without Node, pnpm or npm's registry (5c2e803)
  • Take the deleted parity records out of the gates path set (d1026c3)
  • Stop naming the paths T-149 deleted in the config set (d648987)

CI

  • Set up no Node or vp in CI and the nightly, and run no changelog step (04c6f43)
  • Delete the parity records and tools/bin/parity (0439ca8)
  • Read the nightly's changed-sites base from the last green nightly (3682394)
  • Judge the nightly's changed sites since the last green nightly (27ae132)
  • Judge only the files a Linux build compiles in the nightly's changed sites (6baa977)

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.0.1 is a breaking change. Every feat and fix since v8.0.1 says Upgrading: none.

  2. What it changes on purpose. No fix since v8.0.1 names an old scenario or case it changes (Changes:).

  3. The config. No key, type, value or default changed since v8.0.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.1.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.1.0
cd "$(git rev-parse --show-toplevel)"
case "$(uname -s)-$(uname -m)" in
Linux-x86_64) platform=linux-amd64 sum=a49624ea8759bf40a05be39476c4eefd6bc10e71ce6f3284d97fc7320b96cd2c ;;
Linux-aarch64 | Linux-arm64) platform=linux-arm64 sum=10a68b6d1513d7520f57830aefeab7d3e82f3db708d8106ae298fdf7218cc17b ;;
Darwin-x86_64) platform=darwin-amd64 sum=eb76cf5db8d9f8c32e3a9fc88230d9225fdc78c73561bc3662ac38c90d439fcc ;;
Darwin-arm64) platform=darwin-arm64 sum=9cfc6a34292275f57a1e318b924706137c49f8715f0ada8f3f52f2ee80952da0 ;;
MINGW*-x86_64 | MSYS*-x86_64) platform=windows-amd64 sum=713cd7e005e8091f0bf18a50a618674b71e04acc385ce812aef1863862018d06 ;;
*) 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.1.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 SH...

Read more
Loading

itos 8.0.1

itos 8.0.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 07:29
v8.0.1
1f660a9

itos 8.0.1

Cut by CI from the 94 commits since v8.0.0: 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.0.0...v8.0.1

What changed

Fixes

  • Print a task's why once in work show, and leave it out of task add's item (d8ef470)

Refactoring

  • Clear what staticcheck finds in the Go code (02dda42)
  • Name the Go build-go in internal/version's doc comment (c58b38f)

Tests

  • Read a registry whose items are absent or null as one with none (b0ef685)
  • Quote the question the decision cases pass, so every YAML reader takes it (78504a7)
  • Keep git from maintaining a scenario's repository in the background (cf9d61d)
  • Delete the TypeScript corpus runner, which a Go program replaced (fabb806)
  • Tell apart two whys of one word each in work show's comparison (1f660a9)

Build

  • Format Markdown and YAML with dprint, pinned by checksum (a0439c0)
  • Run the pre-commit hook from the git config, and drop vp (67d5f39)
  • Keep a hook's git environment from the unit tests it runs (7cbab77)
  • Let the devcontainer fetch dprint and its plugins (56d183e)
  • Say the devcontainer's pnpm serves the TypeScript tooling, not a hook (560b747)

CI

  • Seed the push proof's one mutation site by the range's start (f09e0f2)
  • Take .vite-hooks out of the gates, and hold dprint.json as one (a53681a)
  • Run staticcheck in CI's plan in place of fallow's audit (1349cb0)
  • Record what the gates' self-tests say, before Go tests replace them (debd75c)
  • Hold a tool's Go replacement to what the TypeScript said, with parity (b4feaeb)
  • Port the push steps' self-tests to Go tests beside what they test (3ac374f)
  • Port the nightly's self-tests to Go tests (41c85e4)
  • Run the gates' self-tests as Go tests, and delete their TypeScript (503695f)
  • Delete the seven self-tests no step runs, and say what guards each (66b23fe)
  • Keep git from maintaining the self-tests' scratch repositories (d65e5ee)
  • Record what the conformance runner says, before a Go runner replaces it (76a7cd3)
  • Run the conformance corpus with a Go program (bab4ddf)
  • Record what tools/bin's TypeScript programs say, before Go replaces them (0ced4bc)
  • Build a go run record's program, so parity sees its exit code (e4a052b)
  • Run tools/bin's inbox, build-go and itos-cc-tests as Go programs (86bfe11)
  • Delete tools/bin's TypeScript programs, which Go programs replaced (e3a7daf)
  • Write the inbox's JSON keys in the order gh's jq gives them (7f3d7f2)

Documentation

  • Take T-158 (56fcfb3)
  • Close T-158 (fd604e4)
  • Add p1-work-done-takes-unowned (91dc6d5)
  • Promote p1-push-proof-stable-site to T-159 (5d3ad1b)
  • Write T-159's ledger entry (372c816)
  • Take T-159 (29e696e)
  • Seed the local push proof by origin/main, as CI seeds by the range's start (3a40bcc)
  • Close T-159 (a1a4de4)
  • Take T-142 (35aa528)
  • Format the Markdown as dprint does (a100ccf)
  • Describe the pre-commit hook in the git config, and the commands vp ran (e47e0fb)
  • Drop p1-hook-env-unset-tracked (cfd1678)
  • Add p1-pre-commit-windows (eabe831)
  • Add p1-drop-vite-hooks-path (1174844)
  • Close T-142 (db73926)
  • Queue T-142 (f44b684)
  • Retire the vp staged lesson, since no hook runs vp staged (646729e)
  • Record T-148's pick, staticcheck in CI and no deadcode (2b95bd4)
  • Queue T-148 (60303fe)
  • Say what the nightly runs, which is no closed task's checks (b65f5ca)
  • Take T-148 (487db30)
  • Describe the hooks and checks without fallow, and staticcheck as CI's (110d73c)
  • Add p1-js-error-texts (8b0b24d)
  • Edit p1-js-error-texts (283ea6f)
  • Record that the plugin moves to its own repository if it grows (70a1c76)
  • Add p1-shellcheck-scripts (488007d)
  • Add p1-work-show-closing-checks (da7dab0)
  • Add p1-archive-closed (f592934)
  • Close T-148 (ecf9020)
  • Queue T-148 (dfec339)
  • Take T-143 (1085f16)
  • Describe the self-tests as Go tests, and the parity records (9dbb753)
  • Drop p1-drop-vite-hooks-path (2f0f91f)
  • Add p1-message-doc-header-agreement (8018e7c)
  • Add p1-gate-edit-without-task (b6ba80d)
  • Close T-143 (35168d4)
  • Queue T-143 (43a775f)
  • Take T-144 ([5ae91ca](h...
Read more
Loading

itos 8.0.0

itos 8.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Oct 21:58
v8.0.0
da7d98f

itos 8.0.0

Cut by CI from the 240 commits since v7.5.0: 11 feats, 2 fixes and 7 breaking changes, where a breaking change makes a major release, a feat a minor one and a fix a patch. Every change: v7.5.0...v8.0.0

What changed

CI

  • Cut v8.0.0 by removing the pre-release marker (da7d98f)

Documentation

  • Add p1-prepush-new-ref-base (480411e)
  • Add p1-prepush-refuses-tag-moves (af4ee4a)
  • Add p1-shim-push-named-refs (e1d9dc7)
  • Close bug-105 (a02a70c)
  • Move the testing tiers to v8.x, first after v8.0.0 (0177697)
  • Add T-158 (5c5ac6c)
  • Close slice-131 (a1ebcc5)

Features

  • Push named tags and branches with itos push --tag and --ref (e716a0b)

Tests

  • Add the steps of itos push --tag and --ref (f6a7435)
  • Kill the surviving mutants of itos push and its --tag and --ref (01a6028)

Documentation

  • Edit p1-lint-leading-blank-hash-line (19cc075)
  • Edit p1-draft-checks-before-minting (dd22f4c)
  • Close slice-129 (8f285f6)
  • Add p1-github-registry-pilot (a573b56)
  • Edit p1-typed-items (89c175d)
  • Close slice-130 (b36fee3)
  • Add p2-pilot-mise (8afe2b1)
  • Promote p1-push-tag-and-ref to slice-131 (754cd49)
  • Specify slice-131, itos push --tag and --ref (f4a7fdb)
  • Take slice-131 (e66cf90)

Fixes

  • Warn of answered questions naming a missing item, and rename promoted ideas in questions (798276a)

Documentation

  • Edit p1-guard-follows-cd (dbd6cdc)
  • Edit p3-commit-long-text-footer (636512a)
  • Add p1-steps-config-sets-nested (db36b3e)
  • Add bug-105 (928e17f)
  • Drop p1-promote-renames-asks (cd5d8c6)
  • Specify bug-105, stale question links warn and promote renames them (9304f5a)
  • Take bug-105 (c66ca1c)

Features

  • Refuse ledger layouts, questions and config values itos cannot use (8d366ff)

Tests

  • Add the steps slice-130's scenarios set up with (4830dc4)
  • Kill the mutants slice-130's changed functions left alive (3fbcd4e)

Documentation

  • Put the nightly's changed sites and the stable push sample in v8's testing tiers (911322d)
  • Add p2-stateful-pbt-registry (38d0e9e)
  • Add p3-tla-id-counter (5058848)
  • Add p3-evaluate-pstack (705a6a5)
  • Edit p1-testing-tiers-guide (eabd22b)
  • Ask q-61 (0e2373f)
  • Add p2-adopt-go-template-itos (113e7d6)
  • Drop 4 items (26124ab)
  • Edit p1-wip-red-first (1d16a64)
  • Answer q-61 (3ba748f)
  • Record q-61 as decision 50, superseding ADR-0047 (09bcb3a)
  • Edit p3-commit-long-text-footer (e7f90b0)
  • Add p1-work-merge (94438b5)
  • Add p1-typed-items (297a6fd)
  • Edit p1-work-merge (d8507e6)
  • Promote p1-ledger-layout-checks to slice-130 (4c74635)
  • Drop p1-load-refuses-unusable-values, p1-asks-check, p1-ledger-id-default (b8bbd04)
  • Specify slice-130, ledger layouts, questions and config values refused alike (1e1dbed)
  • Take slice-130 (2bd715c)
  • Fix slice-130's Givens to set up what they assert (f30383d)
  • Extend the trace-each-Given lesson with slices 129 and 130 (f6d8ab0)
  • Edit p1-wip-red-first (41a44a8)
  • Point six questions at the items they were promoted to (68a7fcb)
  • Add p1-promote-renames-asks (dec1b9e)

Features

  • Refuse in config check the values no tool can use (b2adb2d)

Tests

  • Add the steps slice 129's scenarios need (7bf024d)

Documentation

  • Add p1-shim-pathspec-sweeps (52b91b7)
  • Add p1-help-cases-regenerate (e08392d)
  • Add p1-corpus-dev-binary-version (450c2e8)
  • Close slice-128 (792e669)
  • Settle the v8 plan's staging line, ledger.id and Changes hook (d7212ef)
  • Keep the local all-sites run in briefs until the nightly judges them (9ff6285)
  • Promote p1-shell-not-empty to slice-129 (c611035)
  • Drop 4 items (1c3cf9c)
  • Specify slice-129, config check refuses values no tool can use (ce312ed)
  • Take slice-129 (bc79197)
  • Add p1-load-refuses-unusable-values (460b4e7)

Features

  • Refuse skipped hooks, sweeping stages and force-pushes (96133c4)

Tests

  • Add the steps of slice 128's shim and pre...
Read more
Loading

itos 8.0.0-rc.9

itos 8.0.0-rc.9 Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Oct 18:36
v8.0.0-rc.9
96133c4

itos 8.0.0-rc.9

A pre-release, a candidate for 8.0.0, cut while this repository's
tools/bin/release-version/prerelease says rc. It is published as a pre-release and never as latest, so
go install …@latest, the launcher's update notice and a bare itos pin still name the newest
stable release; itos pin 8.0.0-rc.9 pins this one. Its notes run from v7.5.0, the last
stable release, as 8.0.0's will.

Cut by CI from the 171 commits since v7.5.0: 8 feats, 1 fix and 4 breaking changes, where a breaking change makes a major release, a feat a minor one and a fix a patch. Every change: v7.5.0...v8.0.0-rc.9

What changed

Features

  • Refuse skipped hooks, sweeping stages and force-pushes (96133c4)

Tests

  • Add the steps of slice 128's shim and pre-push scenarios (c843c55)

Documentation

  • Edit p1-lint-leading-blank-hash-line (cd0b95b)
  • Add p2-user-feedback-targets (ca14ff4)
  • Promote p1-shim-refuses-hook-skipping to slice-128 (9643618)
  • Specify slice-128, the gates refuse what skips them (65d2779)
  • Close T-157 (cc7db66)
  • Close bug-104 (2dc07ba)
  • Answer q-59 (72c61b6)
  • Ask q-60 (1ae8437)
  • Add p1-nightly-judges-changed-sites (38750b5)
  • Edit p1-testing-tiers-guide (f9b6ba0)
  • Close slice-127 (7282dd5)
  • Answer q-60 (2a603cb)
  • Record q-59 and q-60 as decisions 48 and 49 (77556cc)
  • Edit p1-decision-record-hook-lock (b4a97d9)
  • Take slice-128 (f8c2ef7)

Features

  • Judge the item's own commits at work done (f5e578a)

Tests

  • Add the steps of slice 127's work done scenarios (5047e0a)

CI

  • Hold AGENTS.md to 11000 bytes (23098ff)

Documentation

  • Add T-157 (39fb319)
  • Take T-157 (32d5d62)
  • Cut AGENTS.md to what holds only in this repository (9990ef7)
  • Promote p1-work-done-passes-own-closes to slice-127 (1ad8877)
  • Specify slice-127, work done judges the item's own commits (4911b36)
  • Take slice-127 (92c3ef4)

Fixes

  • Run itos init as the version the config pins (7166fa0)

Tests

  • Kill the four upgrade.go mutants that survive slice-126's range (bde8303)
  • Hold binaryCommand to a run with no command and to git-shim's second word (cc784a4)

Documentation

Features

  • Hand itos upgrade to the newer release it moves to (04ba2a9)

Refactoring

  • Give launch.Main's exit code only when it hands the run on (58d462f)

Tests

  • Let the conformance runner take its native git with --git (3537d34)
  • Expect the stealth rules file's OS path in TestRefreshedRules (62965b8)

CI

  • Hand the conformance runner its native git from previous-release (fcec781)

Documentation

  • Close slice-124 (8719140)
  • Queue slice-124 (876b4fc)
  • Close slice-125 (07e85ad)
  • Queue slice-125 (613611d)
  • Add T-153 (f5c5863)
  • Take T-153 (e60e7b4)
  • Promote p1-upgrade-refreshes-agent-block to slice-126 (0aa45ba)
  • Specify slice-126, upgrade handed to the newer release (33b33b4)
  • Take slice-126 (f585700)
  • Add p1-init-agent-rules-runs-pin (e412304)
  • Add p1-draft-checks-before-minting (27e27f0)
  • Add p1-ci-run-help-proof-check (921f97a)
  • Edit p1-ci-watch-failed-step (55fea0c)
  • Put p1-init-agent-rules-runs-pin in the v8 plan ([af586ea](https://git...
Read more
Loading