Skip to content

snouty changelog

com.antithesis/snouty

3 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • AGENTS.md +24 −8

    https://raw.githubusercontent.com/antithesishq/snouty/HEAD/AGENTS.md

    − 3. Run `mise run test` before you finish. Before a `git push`, also run the−    checks that the Stop hooks run (see "Checks and lints") and `mise run lint`:−    a hook does not run until you stop.− errors, warnings, hints, status lines and the README.− upgrade exists, with a reason and a link. A pull request fails on licenses,− bans and sources; only the nightly and manual runs fail on advisories. Do not fix a− zizmor finding in a generated workflow by hand; change its generator, as− `.github/zizmor.yml` describes.+ 3. While you work, run only the tests that your change touches:+    `cargo nextest run <name>`, or `SNOUTY_SPEC=<file> cargo nextest run+    spec_tests` for a spec. To run all tests but the slow container tests, use+    `cargo nextest run --filterset 'not group(container)'`.+ 4. Run `mise run test` one time, before the first `git push`. After that, run+    it again only when a later change touches the container code or+    `specs_engine/`. CI runs all tests on each push.+ 5. Before a `git push`, also run the checks that the Stop hooks run (see+    "Checks and lints") and `mise run lint`: a hook does not run until you+    stop.+ - snouty is a CLI, not a library. The crate is published only so that+   `cargo install snouty` works, so its Rust API has no users: rename, hide or+   remove a public item freely, and do not call that a breaking change.+ errors, warnings, hints, status lines, the README and CI.md.+ - A test does not wait out a fixed time. Pause the tokio clock+   (`start_paused`) in a unit test. For a wait inside the binary, set+   `SNOUTY_TEST_SECOND_MS`, which shortens the retry backoff, the docs connect+   timeout and the MCP progress interval. Do not add a second variable of this+   type.+ upgrade exists, with a reason and a link. An ignore that matches no crate+ fails the check, so delete it when an upgrade drops the crate. A pull request+ fails on licenses, bans and sources; only the nightly and manual runs fail on+ advisories. Do not fix a zizmor finding in a generated workflow by hand; change+ its generator, as `.github/zizmor.yml` describes.
  • server.json 2 fields changed
    env_vars
    SNOUTY_UNSTABLE_FEATURES none
    version
    0.9.1 0.10.0

  • server.json 1 field changed
    version
    0.9.0 0.9.1