Repository navigation
chore: version packages - #173
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
15 times, most recently
from
November 18, 2026 21:02
998313f to
853e63b
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 18, 2026 22:22
853e63b to
7e2acdb
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@stainless-code/verdict@0.8.0
Minor Changes
ecc6b89:
drainis a hidden CLI verb that refreshes threads, plans the review threads waiting on a verdict reply, and pins the plan with a digest.drain --agent <name>launches one agent through the same launcherrunuses and validates itsdrain.replies.jsonagainst the plan. No host writes or reply posting ship in this slice.6923d0e:
drain --postanswers the waiting review threads from a validateddrain.replies.json. GitHub and GitLab post one marked reply per draft and appendreplies.jsonunder a lock after each write;withdrawalso resolves its thread. Secret-shaped bodies refuse before any write, stale threads are skipped, and a failed write recordsfailed[]and refusesdrain-incompleteso the same command can finish the remaining replies.9c68ea2:
run --agentnow supports fourteen verified official agent CLIs, includingagy,amp,copilot,crush,droid,gemini,goose,kiro,pi, andqwen, with prompt flags placed immediately before the directive for agents that take it as a flag value. Operators can define more agents under the newagentskey of their own settings file; the shape is prefs-only, closed, and refuses name collisions and invalid binaries asbad-settings.bc6f739: A bad
--contextpath now refusescontext-invalidwith a path-specific hint instead offetch-failed.Breaking changes
A bad
--contextinput — missing, symlinked, too deep or too large, or the wrong type — now refusescontext-invalidinstead offetch-failed. Scripts that matchedfetch-failedfor these cases must matchcontext-invalid. Bundle-write failures still refusefetch-failed. The refusal names the path as typed and, for a relative path, its absolute resolution, and its hint tells you to check each--contextpath.98d8bec:
run --agentnow offers 32 more cited headless agents, including Cline and Junie after CLI-reference checks. Rows whose binary shares a name with another tool run a harmless identity probe before launch; a non-zero exit, a five-second timeout, or a missing match refuses the newagent-mismatchcode before any agent starts, andlauncher.jsonrecordsprobe: {args, ok}for a passing check. Operator agents can setprobe_argsandprobe_matchunder settings.jsonagents, withprobe_matchrequired whenprobe_argsis present.770b32f:
drain --post --dry-runruns every post gate and live read, then writesdrain.dryrun.jsonwith the exact marked replies and typed skips a real post would produce. It makes zero host writes and leavesreplies.json,drain.json, andthreads.jsonbyte-identical;--agent --post --dry-runplans, drafts, then previews. The flag requires--postand secret-shaped bodies still refuse.5712cec: Breaking changes
The installed skill is now a small Bootstrap skill: it only says when to use Verdict and how to reach the binary. The binary serves the full Procedure, so the instructions always match the version that checks your work.
Reinstall the skill on every machine. For harness installs, for each installed agent, run
verdict skill status --agent <x>and delete the oldverdictskill directory at the path printed after->; then runverdict skill install --agent <x>.verdict skill install --detectis fine instead of--agent.verdict skill uninstallremoves only the new Bootstrap skill files, so it would leave the old Procedure files beside the stub.For registry installs, delete the old
verdictskill directory, then re-runnpx skills add stainless-code/verdict.Copies went stale between releases: the Procedure lived inside the installed skill, so an older copy could hand an agent instructions that disagreed with the binary grading its work. Keeping it in the binary removes that skew.
66342c5: Every fetched bundle now carries
procedure.md, the review Procedure assembled by the binary from its embedded payload. Drain plans carrydrain.procedure.mdfor reply drafting. Therun, stage, and drain directives name those files as authoritative, so an installed skill that is older can no longer displace them. The fetchnext:hints and--show-promptsoutput point at the bundle Procedure, and provenance receipts record its sha256 as a bundle input.PromptsHashnow reads the embedded payload, so an installed user gets the real prompt-set hash without aprocedure/checkout.85b2e97: MCP hosts can now load the Procedure straight from the binary.
prompts/listandprompts/getserve five task prompts (address-reviews,fix-ci,incremental-review,review,validate), andresources/listandresources/readserve every payload file atverdict://skill/<path>, byte-identical toverdict skill show. Prompts and resources are read-only and available in every server mode, including--read-onlyand--operator.initializeadvertises both capabilities and points hosts at thereviewprompt orverdict://skill/PROCEDURE.md.31efb1b: Breaking changes
Published JSON schemas moved from
skills/verdict/schemas/to/schemas/; every$idchanged accordingly.938bc6d:
review.jsonis now a findings-only handoff: each finding carries a path, strict integer line, severity, claim, quoted code, and finder confidence; optional spec checks and receipts reserve the evidence S4 verifies. Verdict renders the body and derives approval from the stored findings, with a documented default threshold and the existing block-clause policy. The document keeps"schema_version": "1"— this is a breaking change inside that version, shipped with no shim.Breaking changes
review.jsonmust carryfindings[]and may no longer carryapproved,body,comments[],sections[]or a top-levelconfidence; the document is closed, so any of those keys refuses as an unknown field and there is no repair hint for the old shape. To rewrite a stored v1 file, move eachcomments[].bodyintofindings[].claim, addquote,severityandconfidenceto every finding, convertlineto an integer, move the oldbodyprose tosummary(at most 2000 characters), dropapproved,sections[]and top-levelconfidence, and keep the claim arrays (resolved,triage,coverage,chunks,suppressed,risk,security_summary) unchanged.One problem code that policed the old contract is gone:
basis-replaced(the agent writes nobody, so there is no line for the CLI to repair). The closed document refuses the removed keys
as
unknown-field, and the review prompt dropsin-boundswith the rest of the body grammar.The dry run's
data.checknow reportsfindingsandanchors_moved_to_bodyin place of thecommentsandsectionscounters that described the old body grammar.Approval is no longer an agent claim. With no repository policy, any open, visible finding whose quote standing is not
unverifiedatimportantor above withholds approval, as does any violatedspec_checks[]entry;block_clausesandreport --checkrefine that default when configured.recorddecides once and stores the decision inrecord.jsonasapproval, beside thereview_sha256it decided on;postpublishes that stored decision, renders its body from the same decision, and refusesrecord-stalewhen the review, diff, or head moved after the record, rather than deciding again over a review nobody recorded.Do not release between this slice and S4. S1 stores
spec_checks[]andreceipts[]but does not verify quotes or require receipt coverage; S4 adds the insufficient-review refusal and closes the gap where a findings-free review would otherwise derive approval. The release hold is tracked in Linear.1dfcc29:
backtest fixturesgrades converted fixture recordings against hand-known defects in a new fixture corpus. It publishes recall, bonus-union, false-green, hallucination (with explicitunverifiablecounts) andreview-insufficientmetrics, reproduces seven hand scores as calibration, and writes one report under.verdict/backtest/fixtures/report.json. The mode never launches an agent or calls a host.abb3389:
ready --filternow gates the review on the closed trigger predicates in the trusted base configuration: matching PRs run and record the decision, non-matching PRs refusefiltered-outbefore any host call, and unusable policy or facts refusetrigger-failed.Fetch now requests and records PR labels in
PR.jsonfor every host, so thelabelstrigger predicate can read them from the bundle.Patch Changes
--contextspec.