[dependabot]

Bumps WireCatLabs/cli-base/.github/workflows/release-checks.yml from 0.85.1 to 0.95.0.

Changelog

Sourced from WireCatLabs/cli-base/.github/workflows/release-checks.yml's changelog.

Changelog

Notable changes to @wirecat/cli-base (published as @wirecat/cli-core up to 0.20.0), one section per version, newest first. Versions follow semantic versioning; before 1.0.0 a minor release may change the API. Versions before 0.8.0 are in the git tags.

Every entry says what changed as a caller sees it, why, and what to watch for — the rules are docs/dev/CONVENTIONS.md.

0.98.0 — 12.11.2026

Added

• cli-dev audit --family: one command instead of each CLI's scripts/audit.sh. Given the CLI's own built bin (--cli dist/bin/b24.js), it installs the latest published CLIs of every parity group (mail and gcal included, which the six copies left out), runs each in an empty home with the keyring out of reach, and reads every CLI's commands info --json, so same-error-reason and same-entity-schema are measured at last. It defaults --for, --lint and --groups as the script did. The two newly measured rules print their findings as warnings for now: they are strict, so no baseline can hold them, and the script never measured them. See TOOLING.md.
• cli-dev changelog fragments and cli-dev changelog level. The changes/<branch>.md fragment check and collection, and the version-level check (Added needs a minor, a break a major), which b24 and cli-core each kept as a script of their own, are now shared; --next <x.y.z> prints the version a release needs. Also exported from @wirecat/cli-base/release (readFragments, fragmentProblems, collectFragments, levelledVersion, versionLevelProblem, CHANGELOG_HEADINGS).
• cli-dev adopt <x.y.z>: a shared-package bump done the same way in every CLI. It pins the version (--package, cli-core by default), runs pnpm install, then generate and ci:quick when the CLI has them, and stops at the first failure. It opens no pull request yet.
• Commands cli-core mounts can say so: origin: "cli-core". The commands document accepts the new value, and lint treats such a command like a handwritten one. Once cli-core marks its commands, cli-dev lint fails a word rule's baseline entry on the CLI's own command (it belongs in the overrides) and an override on cli-core's (it belongs in the baseline), as WC-TOOL-16 says; --allow-stale only warns, as for a stale entry. Nothing changes until then. To watch for: a reader of commands --json on an older cli-base refuses a document with the new value, so cli-core marks its commands only once the CLIs and tools that parse it are on this release.
• A parity group's difference can expire. A differences entry takes review_after, with the lint overrides' rule: a warning from 14 days before, a failure 14 days after. An audit without --for also warns when the baseline holds rows no CLI has any more.
• retrying() in @wirecat/cli-base/http: one retry loop for provider CLIs. It wraps a FetchLike (usually hostFetch's) and sends a read again after 408, 429, 5xx or a retryable error, a write only after a 429, waiting the provider's Retry-After or a jittered backoff, within budget, and through a shared pacer when given. b24, zoom, max, mail and beeline each wrote their own loop with different limits; see REFERENCE.md.
• Vocabulary roles for the words cli-core's shared commands use. account remove --keep-data and --delete-data, session start --answer-stdin, --client-id and --client-file, --hide-phone, and the verb call (api call) now have a meaning in the vocabulary. Eight CLIs carried about 35 baseline and override lines for them. To watch for: cli-dev lint reports each of those lines as stale; remove them in the change that takes this release.
• Lint gives an override's review_after two weeks either side. An override warns from 14 days before its date and fails only once it is more than 14 days past it. Until now every CI run of a CLI went red on the morning after

... (truncated)

Commits

• c1f6e98 chore(release): 0.95.0 (#561)
• 0e81747 fix(ci): coverage takes each test shard's latest attempt (#560)
• 5dfb058 chore(release): 0.94.0 (#559)
• 3b669c4 feat(standards): meta.ranking, what a hosted model did to a search's order (#...
• e45d46e chore(deps): Bump github/codeql-action/autobuild from 4.39.1 to 4.39.3 (#476)
• 134fe83 chore(deps): Bump github/codeql-action/upload-sarif from 4.39.1 to 4.39.2 (#477)
• 472392f chore(deps): Bump github/codeql-action/analyze from 4.39.1 to 4.39.2 (#478)
• 07bcc96 chore(deps): Bump github/codeql-action/init from 4.39.1 to 4.39.2 (#480)
• d057281 feat(standards)!: raw-network catches fetch as a value, docs-check an empty U...
• a2140ac fix(standards): --accept-terms is no longer needed (#557)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)