Release notes

The current software release is GetAIP Core 2.0.0. It changes implementation names and software packaging while the Agent Interoperability Protocol remains version 1.0.

Use the annotated tag or full commit, then bind built artifacts by digest. A software version does not replace the AIP protocol version, source tree, build identity, or qualification scope.

GetAIP Core 2.0.0 — 3 August 2026

Release identity.

• Version: 2.0.0.
• Annotated tag: v2.0.0; tag object d254b2dc876f107e8dd96f073fc5c27c7faad818.
• Release commit: d7cce13d1d555644d04a4d73c66c95b113737635.
• Release tree: e3ef5e0c3921641863a1f6e9b4f704b856dc4423.
• Deterministic source digest: 6901ba7a7e525036229bb42669550933577978ddf5f0913efe769c0694dce6a6.
• Production marker: aip-core-production-20260803-181438-gst; tag object 75b917ab8e3f3a9ab2e2a8479024007e5b1504fc.
• Qualified pull request: #12 at beac80b38bb1f3991804a8c445bcdab2abbd6ba3.
• Gitea Actions run: 4242.
• Merge time: 2026-08-03T14:14:10Z.

What changed.

Part 1 of the GetAIP naming migration makes getaip the CLI command and getaip-server the product-neutral server command. Cargo packages, images, configuration names, environment variables, implementation-owned identities, capability prefixes, and error namespaces follow the corresponding GetAIP naming contract.

The release also includes the separately hosted connector-fleet implementation documented by this site. It does not add the future setup, doctor, status, or serve command surface, and it does not establish public npm or native-binary installer artifacts.

Qualification boundary.

All six protected pull-request contexts completed successfully on the exact PR head. The authoritative source gate reported 573 passing tests and 2 intentionally skipped tests. PostgreSQL scale and recovery, the pinned Python sidecar, macOS portability, complete-history secret scanning, migration images, the Docker failure matrix, product images, and the controlled 45-case product fleet gate passed.

The protocol-preservation diff against aip-core-production-20260802-092436-gst was empty for schemas/aip, crates/aip-core, and crates/aip-schema. This supports the narrow statement that the naming release does not change AIP 1.0; it is not a general production-readiness or external-provider qualification claim.

See release artifacts for exact job-log, Docker, tag, and clone-back evidence.

Historical implementation naming: the v1.0.0 record below documents a pre-v2.0.0 implementation. Executable, crate, configuration, image, and identity names in that record are retained as evidence; use the current reference documentation for present names.

AIP Core 1.0.0 — 21 July 2026

Release identity

The repository records the tag and release commit locally. Its source manifest records a private publication target.

What the release contains

The initial source release includes:

• the native AIP 1.0 model, validation, generated schemas, and Rust facade;
• authentication, discovery, runtime, PostgreSQL storage, gateway, and native transport implementations;
• MCP, A2A, and webhook compatibility components;
• the connector SDK and the five then-maintained public connectors: Cal.diy, Hermes Agent, Chatwoot, Dify, and CrewAI;
• aipd, aipctl, conformance tooling, examples, legal notices, and release automation.

The release was a clean-root source snapshot. Its SOURCE_SNAPSHOT.json records the source and transformation:

The source release deliberately excludes the documentation frontend, top-level benchmarks, top-level tests, and qualification-evidence tree. README.md is the only Markdown document inside that publication boundary. These exclusions describe packaging, not AIP wire behavior.

Historical path from 1.0.0 to 2.0.0

The following five commits formed the documented connector-fleet source range before the later v2.0.0 naming release. They remain useful history, but 97be86e9... is no longer the current release identity.

Separate protocol compatibility from deployment compatibility

Follow the bundled connector migration before replacing a v1.0.0 deployment. The migration must preserve tenant, credential, idempotency, approval, transaction, provider-effect, and recovery state; a successful process start is not sufficient.

Choose the correct source identity

Use v2.0.0 for the current GetAIP software release. Use v1.0.0 only when you need the historical private source snapshot and its exact publication boundary.

For either choice:

1. Resolve the annotated tag to its commit and tree.
2. Require a clean source tree and record its deterministic identity.
3. Record every built image or binary digest and generated manifest digest.
4. Match configuration, migration, connector upstream, and qualification identities to that source.
5. Do not combine release notes, binaries, or qualification results from different source states.

Remaining release boundaries

• The private-SDK publication manifest remains disabled pending its registry bootstrap and verification prerequisites.
• The retained evidence proves the named source and controlled qualification gates, not a public npm installer or standalone native binary archive.
• Public registry publication, multi-platform release signatures, SBOMs, attestations, and a durable public evidence catalog are not established by the retained Gitea release record.
• External-provider and target-deployment qualification remain separate from the successful protected CI contexts.

Related documentation

• Release artifacts and verification
• Bundled connector migration
• Implementation status
• Licensing
• Connector documentation