fuz_repos

tooling · ready · TypeScript, Rust · repos.fuz.dev

fuz_repos as this site sees it: what its repo's own files declare, and every record on the coherence and values pages that names it or links it. This page is computed and adds nothing of its own. For what the project is, see the Fuz stack page.

What uses it

The stack repos that declare a dependency on it. A breaking change has to be carried through each of them, and through any consumer that no manifest declares. Only the stack's own projects are listed, so a consumer outside the stack is not here.

Used byKindDeclared inThrough
zzz runtimeCargo.toml(path)fuz_git, fuz_repos

What it uses

UsesKindDeclared inThrough
fuz_css peerpackage.json@fuzdev/fuz_css
fuz_schema peerpackage.json@fuzdev/fuz_schema
fuz_ui peerpackage.json@fuzdev/fuz_ui
fuz_util peerpackage.json@fuzdev/fuz_util
gro peerpackage.json@fuzdev/gro
blake3 devpackage.json@fuzdev/blake3-wasm
fuz_code devpackage.json@fuzdev/fuz_code
mdz devpackage.json@fuzdev/mdz
svelte-docinfo devpackage.jsonsvelte-docinfo

Read from the repos' manifests on . Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev. See every dependency in the stack.

What it declares from outside the stack

runtime
Cargo.toml: argh, serde, serde_json, thiserror, toml
peer
package.json: @sveltejs/kit, svelte

Read from the repo on . What a repo's manifests declare from outside the stack, by name and without versions. The dev tables are left out, so what an app bundles from its dev table is not here. For a Cargo workspace the list is every crate's together, and it is what is declared, not what a release build links. A crate is left out as tooling only when it is named xtask or testing_*, or the release audit marks it dev-only, so what a bench, debug or test-support crate under another name uses is listed with the rest. See everything the stack declares.

Its check script and CI

The check script of its package.json:

gro check

Its CLAUDE.md has no line in a code block that gives gro check or npm run check with a # comment, and none whose comment says to run it before committing. It may describe its checks another way.

It is among the repos whose check script runs gro check; with a CI step, on a push or a pull request, that runs gro check with --workspace; with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace; with a CI step, on a push or a pull request, that runs gro check with --build; with a Cargo workspace at the root.

.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch

build on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Use Node.js ${{ matrix.node-version }}
    uses actions/setup-node, pinned to a commit
  3. npm ci
  4. npx @fuzdev/gro check --workspace --build

rust on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Install Rust
    rustup toolchain install --no-self-update
    rustup show active-toolchain
    cargo --version
  3. Check git version
    git --version
    version=$(git --version | awk '{print $3}')
    if ! printf '%s\n%s\n' 2.44.0 "$version" | sort -V -C; then
      echo "::error::the fuz_repos tests need git 2.44 or newer, found $version"
      exit 1
    fi
  4. Format
    cargo fmt --check
  5. Clippy
    cargo clippy --workspace --all-targets --locked -- -D warnings
  6. Rustdoc
    cargo doc --workspace --no-deps --all-features --document-private-items --locked
  7. Test
    cargo test --workspace --locked --no-fail-fast

Read from the repo on . A workflow's jobs and steps are as the file writes them: a step's command, or the action it uses without its version. An action's inputs, a matrix's values, permissions, environment and working directories are left out, and nothing here says which command is the gate. A line is quoted when it sits in a code block of the repo's CLAUDE.md, has a # comment after the command, and either is the command gro check or npm run check, or has a comment that says to run it before committing. A repo that describes its check command in a sentence or a list, or in another file, has no line here. Every file is read at the repo's main branch as the checkout last fetched it, so nothing uncommitted or unpushed is here. See every repo's checks.

Holds that name it

Gates

  • Types, tests, lints and format (every change): Type errors, regressions, lint errors and style drift. fuz_repos is among the repos whose check script runs gro check.
  • Drift in generated files (every change): A generated file that no longer matches its source. fuz_repos is among the repos whose check script runs gro check.
  • Drift in the package exports map (ci): An exports map that no longer matches the source, which the local gate rewrites instead of failing on. fuz_repos is among the repos with an exports map in package.json, and a CI step, on a push or a pull request, that runs gro check with --workspace.
  • Build (ci): A broken build. fuz_repos is among the repos with a CI step, on a push or a pull request, that runs gro check with --build.
  • A clean tree after the run, and no TODO docs at the root (ci): Uncommitted output and a TODO Markdown file at the repo root. fuz_repos is among the repos with a CI step, on a push or a pull request, that runs gro check with --workspace.

From Gates. A gate is listed here when its row names the project or links its repo, or speaks of a class of repos that the snapshot puts this one in.

Actions kept with a person

  • Force-push or rewrite the main branch (tool refuses, permission rule): The push tool only fast-forwards, and raw pushes are denied.
  • Push a tag, which starts a release in CI for tsv and gro (tool refuses, permission rule, dry run by default): The push tool never sends a tag, and raw pushes are denied. The release script of tsv pushes its own tag, and changes nothing without an explicit flag.
  • Create a remote branch (tool refuses, permission rule): The push tool refuses to create one from an agent's shell, and raw pushes are denied.

From Actions kept with a person.