[dependabot]

Bumps WireCatLabs/cli-base/.github/workflows/release-checks.yml from 0.31.0 to 0.47.2.

Release notes

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

0.35.0

Added

• Bounded batches share parsing, correlation and sequential execution. prepareBatch, readBatchInput and runBatch accept explicit registered handlers, cap input/count/read reservations and retained output, and keep a result for every input on budget refusal. Failed reads never refund their reserved ceiling; it is not a byte consumption measurement. Hosts retain account authorization, cancellation, final rendering and resource cleanup. projectBatchAnswers selects nested answer fields while retaining ids, errors and completeness.

Full changelog

0.31.1

Fixed

• Nested field selection traverses arrays and retains report coverage. Item/list envelopes, continuation, missing data and operation identifiers are handled by one shared projector; consumers no longer need to unwrap item answers.

Full changelog

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.49.0 — 21.10.2026

Added

• parseLucene can read a phrase's distance. With { proximity: true }, "a b"~3 parses as a phrase predicate with slop: 3, and queryNodeSchema accepts slop. Meeting search needs it for words spread over neighbouring transcript lines, and a caller that turns it on says what the number counts. Without the option ~ is still query.unsupported-operator, so messages and lists see no change. A distance that is not a whole number is query.invalid-syntax; word~2 (fuzzy) stays unsupported either way.

0.48.0 — 21.10.2026

Changed — may break callers

• The handbook has a Time page, and the shared CI runs tests in Asia/Vladivostok. Every time is stored and exchanged in UTC; a zone is applied only where a time with no zone comes in and where a person reads one (https://github.com/WireCatLabs/cli-base/blob/main/docs/standards/time.md, WC-TIME-1…6). WC-OUT-13 now asks for ISO 8601 ending in Z, not any zone. node-ci.yml sets TZ=Asia/Vladivostok for test:coverage, so a test that passed only because CI ran in UTC fails. What to watch for: a repository that moves its node-ci.yml pin to this release may see tests fail that read or print local dates; those are the bugs the Time page names.

Added

• wallTime(value, zone, span) in @wirecat/cli-base/query reads a time with no zone (2026-10-21T16:03, optional seconds) as the moment it names in an IANA zone, whatever the process zone. A local time that daylight saving skips or repeats is refused with validation_error, never guessed. It is the input edge WC-TIME-3 asks for; cli-core's --since-time and --at-time parsers are to move onto it.
• zonedMoment(value, zone, span, { end? }) in @wirecat/cli-base/query reads a typed date or time the way WC-TIME-3 and WC-TIME-5 ask: a zone the value names wins, a time without one is read in zone, a date alone is local midnight, or with end the last millisecond of that local day.
• meta.timezone and meta.window are allowed in every envelope: the zone a time without one was read or shown in, and the UTC { since?, until? } a date filter used.

Fixed

• fakeClock(startMs).now() starts at startMs. It reported 2 × startMs plus the time slept, so a test that gave a start time saw a different wall time than it set. What to watch for: a test that worked around the doubled value now sees the value it passed.

0.47.5 — 21.10.2026

... (truncated)

Commits

• b8c56ea chore(release): 0.47.2 (#267)
• 7810058 refactor(standards): drop --qr-file from the flag vocabulary (#266)
• f9435c4 docs(standards): WC-REL-9 counts only changes that make a CLI change its code...
• 611505b chore(release): 0.47.1 (#264)
• 265b053 feat(standards): --alias vocabulary flag (#263)
• 3339910 chore(release): 0.47.0 (#262)
• 332b1e1 feat(standards): a command step may carry line, the whole command with the pr...
• 8891d05 docs(standards): WC-PERM-12 says wa has listen on main, not in a release (#260)
• a88520b chore(release): 0.46.0 (#259)
• c39e1f3 feat(vocabulary): guide is a root word (#258)
• 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)

[leemour]

Superseded by the 0.50.1 bump in the TG-11 PR.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.