Skip to content

Zeroshot v10.21.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 01:23
85e68a3

Changes since v10.20.0.

Features

Let callers declare model context and output limits (#1298)

Let an agent runtime binding declare optional contextWindow and
maxTokens, so callers state a model's limits instead of Zeroshot
guessing them or keeping a catalog. Absent values keep each provider's
defaults.

Add the zeroshot-plan planning skill (#1296)

Adds a zeroshot-plan skill that plans work inside your coding agent
before anything is built. It turns a request or issue into a plan file
(.zeroshot/plans/<id>.md, ignored by git) with checkable acceptance
criteria, and asks only questions that change the outcome. Like the
zeroshot skill, it is used only when the user asks for Zeroshot
planning; for vague or large work the zeroshot skill suggests planning
first and lets the user choose, and it uses a plan's sections as the run
task.

Add TypeSafe-compatible decision adapter (#1313)

Add a decision runtime binding so verifier nodes can call Jev or
another model through a TypeSafe-compatible System One endpoint, using a
caller-provided endpoint and API key. A single adapter validates the
complete probability distribution and emits the authored uncertainty
signal for ties or results below the chosen threshold.

Support GitHub Enterprise and GitLab (#1314)

Support pull/merge request creation, merge delivery, and issue/review
comments on publicly reachable GitHub Enterprise and GitLab instances.
Local runs can reuse host-scoped gh/glab logins; hosted runs accept
explicit token connections.

Forge adapters own instance identity, capability admission, API
credentials, and receipt links while Git transport remains shared.
Require GitHub Enterprise Server 3.22.2+ and GitLab 19.5.1+, with errors
for older or unknown versions. Document GitHub.com, Enterprise, and
GitLab together.

Fixes

Back off grammar compilation rate limits (#1283)

Copilot grammar-compilation rate limits now retry up to three times with
exponential backoff and per-session staggering. Each retry requires
confirmed process cleanup and a successful event drain, then resumes the
same session with its current correction prompt and host context.
Cancellation stops the wait; ordinary HTTP 400 errors remain terminal,
and exhausted retries retain the provider error.

Use --sync-session off for current Copilot CLI releases, replacing the
removed --no-remote-export flag.

Fixes #1203

Documentation

Drop the dead stargazers link and "(my fork)" from Mark's quote (#1312)

  • The starred-by badge no longer links to /stargazers, which GitHub
    now returns as 404 for logged-out visitors. The badge stays as an image.
  • Mark Dingwall's quote under "What users say" drops "(my fork)", at his
    request. He now runs main.

Maintenance

Resolve Python fixture interpreters from the test environment (#1311)

Make the shared Python fixture helper resolve the actual interpreter
selected on the test process's PATH before entering a restricted child
environment. Version-manager shims and interpreter paths containing
spaces or apostrophes now work even when the child clears PATH and
HOME.

Add one focused integration regression for fixture execution and
argument preservation with a cleared environment. Existing fixture call
sites remain unchanged.

Related: #1299

The resolved interpreter and quoted launcher replace the suggested
/usr/bin/env python3 approach because tested launches deliberately pin
or clear PATH. The helper also avoids assuming any of three
conventional installation directories. These changes affect test support
only.

Upgrade

npm install -g @the-open-engine-company/zeroshot@10.21.0