Skip to content

v0.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Jul 11:40
Immutable release. Only release title and notes can be modified.
v0.1.0
ab281c2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

AgentAPI Doctor v0.1.0

Summary

v0.1.0 is the first supported AgentAPI Doctor distribution. It publishes six
native Doctor archives for Linux, macOS, and Windows on amd64 and arm64, plus
checksums, an SPDX SBOM, a Sigstore bundle, and GitHub build provenance.

Doctor runs four bounded raw-wire checks against one explicitly authorized
OpenAI Chat, OpenAI Responses, or Anthropic Messages endpoint. It persists
redacted local evidence and renders terminal, JSON, JUnit, SARIF, Markdown, or
offline HTML reports. This stable distribution is not a vendor certification:
the built-in protocol interpretations remain 0.1.0-candidate.3 and pending
independent source review.

Compatibility and breaking changes

The supported 0.1.x command workflow, exit-code meanings, CLI result envelope,
and release archive naming are recorded in cli/spec.yaml, the public schemas,
and schemas/migration-floor.yaml. Terminal reports now say CHECKS PASSED,
CHECKS FAILED, CHECKS PASSED WITH WARNINGS, or CHECKS INCONCLUSIVE instead
of presenting a candidate profile outcome as a broad compatibility claim.
Markdown and HTML use the same phrases in sentence case. All three formats
display report conditions prominently.

Configuration advances from v1beta1 to v1beta2. The release-candidate
defaults fields were validated but never controlled the fixed Quick Check;
they have been removed instead of remaining misleading no-ops. New baselines
carry urn:agentapi-doctor:baseline:v1; the exact unversioned rc baseline shape
remains readable. Report bundles and local run records retain read support for
their v1alpha1 and v1alpha2 forms.

latest run references now require an explicit --allow-latest flag, including
report, compare, and baseline commands. Exact UUIDv7 run IDs remain the durable
and CI-safe default. The stale doctor dev scaffold surface is removed.

Migration

For an rc1-rc3 configuration, delete the top-level defaults block and change
apiVersion from urn:agentapi-doctor:config:v1beta1 to
urn:agentapi-doctor:config:v1beta2, then run doctor self-check. Target
definitions do not otherwise change.

Existing run records, reports, and unversioned baselines can be read in place.
Do not edit immutable digests to force comparison: rc2 and rc3/v0.1.0 Quick
Check baselines have different built-in identities and must be recaptured.
Scripts that intentionally use the local latest pointer must add
--allow-latest; CI should replace it with the exact run ID.

The complete supported-read matrix and configuration steps are in
docs/migration/README.md.

Known issues

  • A normal endpoint result covers four selected raw HTTP checks for one exact
    endpoint, model, plan, and artifact set. It does not prove arbitrary SDK,
    Agent, provider, or deployment compatibility.
  • Structural checks request 64 output tokens. OpenAI Chat and Responses
    terminal-status checks request 512; these provider-side fields are bounded
    diagnostics, not client-enforced billing ceilings. A model may still return
    an honest INCONCLUSIVE result.
  • The pinned OpenAI Python SDK reproducer is one Linux amd64 loopback regression
    case, not an arbitrary-endpoint SDK driver.
  • Candidate catalog, pack/profile, Registry, Matrix, OCI, package-manager, and
    workflow integration files in the source tree are experimental and are not
    supported distribution channels.
  • Redaction is not anonymization. .agentapi/ contains private local run state;
    keep it out of version control and review every exported report.
  • The project has not claimed independent security review, vendor endorsement,
    a hosted service, or a guaranteed response SLA.

Support window

Support begins when the immutable v0.1.0 GitHub Release becomes public and
ends on 2026-10-13 or when a newer 0.1.x release supersedes it, whichever
comes first. Support is best-effort and covers security and critical Doctor
defects; it does not promise backports to release candidates or older patches.

Publication supersedes the rc1, rc2, and rc3 support windows. Their immutable
artifacts remain available only for historical reproduction.

Verification

The exact immutable v0.1.0 tag binds these notes to the source commit on
protected main. Build metadata and provenance bind the assets to that commit;
checksums and the keyless signature bind the exact published bytes. Every
archive must report version 0.1.0, that full commit ID, and Go 1.26.5 build
metadata. The release gate rejects a different Go patch version, requires six
matching standard-library entries in the SPDX SBOM, and runs
govulncheck -mode=binary on the final Linux amd64 binary.

The complete gate runs schema, catalog, support-lock, Go, race, static-analysis,
integration, documentation, license, container, locked real-SDK, release-tool,
and targeted-mutant tests. Representative Linux, macOS, and Windows runners
verify archive identity, version, and the offline demo before and after
publication. Linux also exercises the fixed-tag installer. Checksums, the
keyless Sigstore certificate identity, provenance, and the exact nine-file
allowlist are documented in docs/operations/release-verification.md.

Assets 12
Loading