v4.4.0

Level: minor, 4.4.0.

Waves in this release: Wave 42: the contract with a repository.

Wave 42: the contract with a repository:

• #1464: The wave starts no verify of a pull request whose mergeable is UNKNOWN (#1481).
• #1474: A signed test server ends its sign-ins with it, so an open server on a reused port gets no old sign-in (#1477).
• #1472: The help of riff wave end names [release] in riff.toml, not deploy/release-check.sh (#1476).
• #1453: Each lead of the riff hears each step of a release, and a lead in a critical place can hold the deploy (#1475).
• #1465: riff pr open --help says that the Milestone: trailer and the title rule hold only with the rules of riff (#1473).
• #1448: The daemon checks the network of each session that it takes up: it stops a worker with none and tells the person of a lead (#1471).
• #1466: wave_list has its rustdoc again, and wave_run_in_container has only its own (#1470).
• #1422: A public base image of riff, riff-base, and riff-rust: each project builds its image FROM one and adds its toolchain (#1469).
• #1426: With no CI, the full check is riff/verify, not a check named Gate that never runs (#1468).
• #1441: A verify with no PASS or FAIL leaves an ends record, and riff daemon events works in the lead container (#1463).
• #1423: The env, volumes and caches of a session come from riff.toml, not from Rust settings that riff sets (#1462).
• #1438: The verify checks that a host can pull a new session image, and the daemon shows a pull that failed (#1461).
• #1429: The names riff uses on the forge are in the book, riff init counts the issues with no Done when, and the dead sccache install goes (#1460).
• #1427: A failed check that is not a run of GitHub Actions starts no fix session: the lead gets its link (#1459).
• #1425: The release cycle, riff build and the real-session test are only for a repository with [release] in riff.toml (#1458).
• #1430: riff wave run --host makes the main clone on a host that does not serve the repository (#1457).
• #1428: riff pr open keeps only the rules that riff reads in a repository that is not riff (#1456).
• #1431: riff init in a session container skips the checks of the machine and runs the checks of the repository (#1455).
• #1424: The package sources that auto mode trusts come from riff.toml, not only crates.io (#1454).

What's Changed

Changes

• The package sources that auto mode trusts come from riff.toml, not only crates.io by @n8behavior in #1454
• riff init in a session container skips the checks of the machine and runs the checks of the repository by @n8behavior in #1455
• riff wave run --host makes the main clone on a host that does not serve the repository by @n8behavior in #1457
• A failed check that is not a run of GitHub Actions starts no fix session: the lead gets its link by @n8behavior in #1459
• riff pr open keeps only the rules that riff reads in a repository that is not riff by @n8behavior in #1456
• wave_list has its rustdoc again, and wave_run_in_container has only its own by @n8behavior in #1470
• A verify with no PASS or FAIL leaves an ends record, and riff daemon events works in the lead container by @n8behavior in #1463
• The names riff uses on the forge are in the book, riff init counts the issues with no Done when, and the dead sccache install goes by @n8behavior in #1460
• The env, volumes and caches of a session come from riff.toml, not from Rust settings that riff sets by @n8behavior in #1462
• riff pr open --help says that the Milestone: trailer and the title rule hold only with the rules of riff by @n8behavior in #1473
• The daemon checks the network of each session that it takes up: it stops a worker with none and tells the person of a lead by @n8behavior in #1471
• The release cycle, riff build and the real-session test are only for a repository with [release] in riff.toml by @n8behavior in #1458
• The verify checks that a host can pull a new session image, and the daemon shows a pull that failed by @n8behavior in #1461
• The help of riff wave end names [release] in riff.toml, not deploy/release-check.sh by @n8behavior in #1476
• Each lead of the riff hears each step of a release, and a lead in a critical place can hold the deploy by @n8behavior in #1475
• A signed test server ends its sign-ins with it, so an open server on a reused port gets no old sign-in by @n8behavior in #1477
• With no CI, the full check is riff/verify, not a check named Gate that never runs by @n8behavior in #1468
• A public base image of riff, riff-base, and riff-rust: each project builds its image FROM one and adds its toolchain by @n8behavior in #1469
• The wave starts no verify of a pull request whose mergeable is UNKNOWN by @n8behavior in #1481

Full Changelog: v4.3.0...v4.4.0

Images

• ghcr.io/como-technologies/riff-base@sha256:2799cd2e7c6e23ab4b9b576ad1331e7315044378a490317624c93d3d984ad5b1
• ghcr.io/como-technologies/riff-rust@sha256:eb0c0920825ef44e72e4183bb8a4a93a5add5a09422a4f3e73ec61cde19ccfe1