# Release candidates and publication

**0.2.0-rc.2 is published on npm, crates.io, Go and
[GitHub](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-rc.2).**
It includes the native Usagestat quota correction and stable 2.0.0 integration.
All three applications pin the exact registry package, passed their Prometheus
checks and reconciled automatically captured real usage. The regular LitAgent
host/metering services and the local desktop were upgraded with existing state
preserved. [Complete receipt](/docs/validation/release-0.2.0-rc.2) · [Adoption](/docs/rc).
Python **0.2.0rc2** is available as a GitHub wheel/sdist while PyPI organization
approval remains pending. Stable `latest` and `alpha` are unchanged.

**0.2.0-rc.1 is published on npm, crates.io, Go and
[GitHub](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-rc.1).**
Fresh public installations, exact artifact hashes and npm's same-source provenance
passed. All three applications pin the RC and completed real workflow acceptance.
The [publication record](/docs/validation/release-0.2.0-rc.1) preserves real retrieval,
Linux account isolation, security, desktop and application evidence with their
limits. [RC adoption](/docs/rc) provides exact coordinates and host upgrade order.
Python **0.2.0rc1** is a GitHub wheel/sdist while the PyPI organization awaits
approval. Stable npm `latest` remains **0.1.0** and `alpha` remains **0.2.0-alpha.6**.

**Version 0.1.0 is published on npm, crates.io and the public Go module proxy**,
with wire protocol 1.0. PyPI publication is waiting for approval of the selected
`agenticdriver` organization. The reviewed Python wheel and sdist remain usable
as archives. See the [release verification record](/docs/validation/release-0.1.0)
for immutable source, digests, installation evidence and outstanding app migrations.
Real-provider certification remains separate from package publication.

**0.2.0-alpha.6** is published on npm, crates.io, Go and GitHub. Python **0.2.0a6**
is available as a reviewed GitHub wheel/sdist. This release removes mock providers, fake connections,
fake embeddings and simulated acceptance harnesses. Real Prometheus checks cover
the selected Codex/Luna and Claude/Haiku accounts across the three application
examples; [the evidence](/docs/validation/real-providers-alpha6-2026-09-28) records
observed quality limits. Package/build checks run separately from real inference.
See [alpha adoption](/docs/alpha), [migration notes](/docs/migrations) and the
[alpha.6 release](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-alpha.6)
for publication availability and checksums. All six SDK checks passed on Prometheus;
[alpha.6 publication evidence](/docs/validation/release-0.2.0-alpha.6) records exact
artifacts, real connections and the delayed npm registry verification. PyPI approval remains pending.

The earlier **0.2.0-alpha.5** (Python **0.2.0a5**) is published on npm, crates.io, Go and GitHub.
It adds desktop-managed outbound SSH routes, native process cleanup and the SDK
repository's shared application evaluation suite. All nine exact-source checks
passed on Prometheus. Fresh registry/archive installations passed over verified
HTTPS; npm trusted publishing also supplies verified same-source provenance.
The Linux desktop and Python wheel/sdist are public downloads. PyPI organization
approval remains pending. See [alpha.5 evidence](/docs/validation/release-0.2.0-alpha.5),
[alpha adoption](/docs/alpha) and the [prerelease](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-alpha.5).
Stable npm `latest` remains `0.1.0`; previously published versions remain unchanged.

The earlier **0.2.0-alpha.4** preview (Python **0.2.0a4**) remains published on npm, GitHub,
crates.io and Go with desktop connection destinations, credential recovery and
shared-panel offline states. All nine exact-source checks passed on Prometheus.
The reviewed JavaScript archive, Python wheel/sdist and Linux desktop are usable
downloads. npm publication is verified through GitHub OIDC without member approval;
PyPI organization approval remains pending. See
[alpha.4 evidence](/docs/validation/release-0.2.0-alpha.4), [alpha adoption](/docs/alpha)
and the [alpha.4 release](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-alpha.4)
for verified hashes, fresh installation checks and channel status. Stable npm
`latest` remains `0.1.0`.

The earlier **0.2.0-alpha.3** preview remains published on npm, crates.io, Go and GitHub.
It adds shared provider icons and optional native connection details across all
four clients and the Linux desktop. Python **0.2.0a3** wheel/sdist downloads are
available on GitHub while PyPI organization approval remains pending. All nine
SDK jobs passed on Prometheus, followed by fresh installed-client quickstarts
over verified HTTPS. See [alpha.3 evidence](/docs/validation/release-0.2.0-alpha.3),
[alpha adoption](/docs/alpha) and the
[alpha.3 release page](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-alpha.3)
for exact artifacts and channel availability. Previously published versions remain unchanged.

The opt-in **0.2.0-alpha.2** preview (Python **0.2.0a2**) is published on npm,
GitHub, crates.io and the Go module proxy, including the Linux desktop companion.
npm registry publication was verified on 2026-09-27. Its exact version remains
installable after the `alpha` tag moved to alpha.3. Python wheel/sdist downloads are available
while PyPI organization approval is pending.
It fixes the TypeScript host-helper declaration issue
found by application acceptance checks after alpha.1 publication. Alpha.1's
GitHub/Rust/Go artifacts remain immutable; its npm upload was held.
See [alpha adoption](/docs/alpha) for exact package pins and archive installation,
[alpha.2 evidence](/docs/validation/release-0.2.0-alpha.2) for verified publication,
[alpha.1 evidence](/docs/validation/release-0.2.0-alpha.1) for the preceding release,
and [the alpha.2 prerelease](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.2.0-alpha.2)
for per-channel publication status. npm uses `alpha`, preserving
stable `latest`. The candidate's channel and npm `publishConfig.tag` are validated
before upload; authorized local publication must also pass `--tag alpha`.

## Distribution inventory

The user selected organization ownership before the first upload. The source
repository is public at `agenticdriver/agenticdriver`; its issues and history
transferred from the personal account. npm uses **`@agenticdriver/sdk`**, while
PyPI and crates.io keep **`agenticdriver`**. `release/config.json` records the
selected owners, package names and bootstrap maintainer.

Publication on 2026-09-21 used reviewed commit
`442ca9c627717f0cdb42ad8260a9692357c79a87` and its successful eight-job SDK CI run.
The npm organization owns `@agenticdriver/sdk`; `agenticdriver:developers` has
write access. crates.io ownership includes `github:agenticdriver:maintainers`
and `hashimkarim` as individual administrator. Both registry publishers are bound
to this organization repository. PyPI organization approval is pending.

| Channel   | Candidate identity                                  | Version source                  | Current state                                        |
| --------- | --------------------------------------------------- | ------------------------------- | ---------------------------------------------------- |
| npm       | `@agenticdriver/sdk`                                | Root `package.json`             | 0.1.0 published; fresh registry installation passed  |
| PyPI      | `agenticdriver`                                     | `clients/python/pyproject.toml` | Organization approval pending; no PyPI upload        |
| crates.io | `agenticdriver`                                     | `clients/rust/Cargo.toml`       | 0.1.0 published; team ownership and install verified |
| Go        | `github.com/agenticdriver/agenticdriver/clients/go` | `release/config.json`           | v0.1.0 tagged; public proxy installation passed      |

These channels match the SDK's language packages. Node also supplies the host
CLI; Python and Rust are libraries, not `pipx`/`cargo install` apps. OS package
managers, desktop stores, a public container registry and the docs domain are
separate distribution choices. This work does not create those destinations.

## Organization ownership

npm's `@agenticdriver` scope belongs to its organization. The publishing human
remains `hashimkarim`, an organization owner; no shared organization password is
needed. Existing development imports from `agenticdriver` must change to
`@agenticdriver/sdk`, including subpaths such as `@agenticdriver/sdk/client`.
The executable remains `agenticdriver`.
[npm organization packages](https://docs.npmjs.com/creating-and-publishing-an-organization-scoped-package/)

PyPI organizations are separate from GitHub organizations. Create/select the
approved `agenticdriver` PyPI organization, create its `agenticdriver` project,
and bind that project's trusted publisher. Do not create a personal pending
publisher as a substitute for the selected organization owner.
[PyPI organization projects](https://docs.pypi.org/organization-accounts/actions/project-actions/)

crates.io uses GitHub teams as organization owners. Its first upload still needs
an individual member's token; immediately add `github:agenticdriver:maintainers`
as a crate owner and verify the team. Retain `hashimkarim` as the individual
administrator: team owners can publish and yank but cannot change owners.
[Cargo owners](https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-owner)

The Go module is `github.com/agenticdriver/agenticdriver/clients/go`. Update
development imports and `go.mod` from the personal path before adopting 0.1.0.
No semantic-version tag was published under the personal path. Historical
pseudoversions remain historical artifacts, not aliases for the new module.

## Build and verify

For the separately runnable JavaScript archive, exports, declaration and scoped
retrieval checks, use `npm run test:package`. Its [package contract](/docs/packages)
records the exact archive digest and verifies an isolated installed consumer.

Use a clean checkout of the intended commit, Node 24/npm, Python 3.12+, Go 1.22+
and Rust 1.89 through rustup. OpenSSL 3 is needed for the installation check:

```sh
npm ci
python3 scripts/release.py build --output /absolute/path/to/new-candidate
python3 scripts/release.py verify /absolute/path/to/new-candidate --require-clean
python3 scripts/test-release.py /absolute/path/to/new-candidate
```

The output directory must not exist. The builder copies only Git-tracked source
into an isolated tree, installs locked npm dependencies and pinned Python build
tools, and builds the npm tarball, Python wheel/sdist, Rust crate and Go module
proxy archive. `manifest.json` records the commit, versions, protocol, toolchains,
file sizes and SHA-256 digests. Preserve it and `SHA256SUMS` with the artifacts.
A checksum verifies integrity; it is not a signature or proof of trusted authorship.

Verification rejects mismatched versions/digests, missing/extra files, private
configuration filenames, links, traversal, duplicate members and oversized
archives. Installation runs three npm recipes plus the four language quickstarts
against the installed npm host through verified HTTPS. Python runs from wheel
and sdist; Go uses the packaged proxy without `replace`; Rust uses the extracted
crate. The checkout's dev dependencies are build tooling only. This gate checks installation and compilation; real model acceptance is separate.

For tooling development, `build --allow-dirty` creates an explicitly dirty
candidate. `verify --require-clean` rejects it. New source inputs must be added
to Git's index to enter that development build. Do not publish a dirty candidate.

Build timestamps derive from the commit, and Python sdist tar/gzip metadata is
normalized. Dependency locks and pinned build tools support repeatable packaging
on the same toolchain. Cross-platform or changed-toolchain output is not assumed
byte-identical. The [candidate workflow](https://github.com/agenticdriver/agenticdriver/blob/27f2bb1aa5170a35ca5592d6db1eec2b73971bc9/.github/workflows/release-candidate.yml)
runs in CI or manually, retains the tested bundle for 14 days, and has read-only
repository permissions with no registry-upload step or publishing secrets.

## Prepare publication

Builds, tests and Python/Rust/Go publication use
[Prometheus](/docs/ci). npm publication uses a dedicated
standard GitHub-hosted Ubuntu runner because npm does not support self-hosted
OIDC. This is a publish-only exception, not a CI fallback. The job is restricted
to the public repository; standard hosted runners for public repositories do not
consume the private-repository minutes allowance.
[GitHub billing](https://docs.github.com/en/billing/concepts/product-billing/github-actions)

The npm job downloads the successful Prometheus run's exact archive, verifies its
manifest and hashes, and uses the existing `publish.yml` / `npm` trusted publisher.
It does not rebuild the SDK, install application dependencies, or use an npm token.
It verifies the registry bytes after upload. OIDC publication is verified for alpha.4 in the
[release evidence](/docs/validation/release-0.2.0-alpha.4). The subsequent verification
run skipped upload after matching the existing bytes. PyPI organization approval
remains pending.

Automatic npm provenance is enabled when the candidate and publishing workflow
use the same source commit. For delayed publication of an older candidate, it is
explicitly disabled: npm's automatic attestation identifies the workflow revision,
which would otherwise misidentify those older bytes. The exact CI source and
archive checks still apply. No workflow SHA or OIDC claim is rewritten.
[npm provenance configuration](https://docs.npmjs.com/trusted-publishers/#disabling-provenance-generation)

AD-042 remains open until registry installation and all three app migrations
are verified. The selected release target is 0.1.0 under `agenticdriver`, with public
source and public packages. Authenticate the selected registry identities and
configure their publishing destinations before uploading the tested candidate.
Public Go installation uses the public module proxy and checksum database.
The initial npm and crates.io uploads authenticated as `hashimkarim` on
2026-09-21. Native credentials remain outside the repository. PyPI has not been
uploaded under a personal account while organization approval is pending.

The current first-publication requirements differ:

- npm supports trusted publishing on GitHub-hosted runners with Node 22.14+
  and npm 11.5.1+. Bind repository, workflow, environment and allowed publishing
  action. A selected owner must bootstrap the first package; do not upload a
  placeholder to create settings. Automatic provenance also requires the public
  source repository and a supported trusted-publishing workflow.
  [npm guidance](https://docs.npmjs.com/trusted-publishers/)
- PyPI supports a pending publisher for a new personal project, but this release
  selects an organization-owned project. Create that project in the organization
  first, then bind its exact repository, workflow and environment. Use PyPA's
  action with job-scoped `id-token: write`.
  [New projects](https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/),
  [publishing](https://docs.pypi.org/trusted-publishers/using-a-publisher/)
- crates.io requires an existing crate before trusted publishing. Its first
  upload needs a selected owner's scoped API token; later releases can exchange
  GitHub OIDC through `rust-lang/crates-io-auth-action`.
  [crates.io guidance](https://crates.io/docs/trusted-publishing)
- The Go package's 0.1.0 tag is `clients/go/v0.1.0`, because it lives below the
  repository root. Tags remain immutable; there is no registry-upload token.
  [Go publication](https://go.dev/doc/modules/publishing)

### Publisher bindings

The manual [publication workflow](https://github.com/agenticdriver/agenticdriver/blob/27f2bb1aa5170a35ca5592d6db1eec2b73971bc9/.github/workflows/publish.yml) accepts one
`registry` (`npm`, `python`, `rust` or `go`) and a `ci_run` ID. Dispatch it from
`sdk-roadmap`. By default it checks out that workflow revision; optional
`candidate_commit` selects a full immutable commit SHA for a delayed channel,
such as Python awaiting organization approval. The checked-out candidate must
be the **same commit** as the successful SDK checks run. It rejects
pull-request runs, unrelated workflows/repositories, failed/incomplete checks,
changed source revisions and mismatched candidate identities. It downloads and
verifies that run's exact candidate bundle; it does not rebuild npm or Python.
CI artifacts expire after 14 days, so a missing CI bundle requires a fresh
SDK checks run at the exact reviewed source. Released archives are also preserved
on the [0.1.0 GitHub release](https://github.com/agenticdriver/agenticdriver/releases/tag/v0.1.0).

Configure the registry-side trusted publishers with these exact values:

| Setting           | npm                              | PyPI                                   | crates.io                                                        |
| ----------------- | -------------------------------- | -------------------------------------- | ---------------------------------------------------------------- |
| Owner             | npm organization `agenticdriver` | PyPI organization `agenticdriver`      | `github:agenticdriver:maintainers` plus individual administrator |
| Package/project   | `@agenticdriver/sdk`             | `agenticdriver`                        | `agenticdriver`                                                  |
| GitHub owner      | `agenticdriver`                  | `agenticdriver`                        | `agenticdriver`                                                  |
| Repository        | `agenticdriver`                  | `agenticdriver`                        | `agenticdriver`                                                  |
| Workflow filename | `publish.yml`                    | `publish.yml`                          | `publish.yml`                                                    |
| Environment       | `npm`                            | `python`                               | `rust`                                                           |
| First upload      | Organization member login        | Organization project trusted publisher | Scoped member token, then team ownership                         |

npm's binding permits `npm publish`. The registry currently reports both
`createPackage` and `createStagedPackage` after the CLI requested only
`--allow-publish`; this workflow only uses direct publication. The Python
upload uses the pinned PyPA action and OIDC. Rust checks Cargo's repackaged files
against the candidate before acquiring its short-lived crates.io identity.
Only the Go job has `contents: write`, to create `clients/go/vX.Y.Z` at the
verified commit. It never updates an existing tag to a different commit, and
tests a fresh installation from the public Go proxy after tagging.

The npm and Rust initial uploads use the same `scripts/publish.py prepare` gate
and inspected CI bundle with the selected owner's native registry login. Never
use a first-upload placeholder. Bind trusted publishing once those packages
exist; the workflow has no fallback to another owner or stored registry token.
Publisher configuration and successful local login are not publication evidence.

Retries query the exact version before upload. A matching existing npm/crate
is verified and skipped. PyPI checks every existing file and uploads only missing
files; a conflicting digest or unexpected file stops the entire attempt. HTTP
401/403/429, redirects and outages are errors, not evidence that a version is
available. Every channel verifies its actual remote metadata after publication.

Use native registry authentication. Keep credentials out of source, artifacts
and command arguments; preserve other package owners/tokens. The publication
commit passed [SDK CI 35612779939](https://github.com/agenticdriver/agenticdriver/actions/runs/35612779939)
after the authorized public-repository transfer. Linux, macOS, Windows,
container/TLS, documentation and exact-artifact installation checks passed.
No billing or spending settings changed. Registry publisher settings were read
back successfully; a later OIDC upload is not claimed by the initial native-login uploads.

## Release and recover

After authorization and destination setup, verify the clean candidate and its
complete SDK CI result. Upload the inspected npm/Python files. Cargo repackages
during publication, so compare its package with the reviewed candidate before
uploading. Publish the reviewed Go subdirectory tag. Give publishing jobs only
their necessary registry identity; candidate builds need no OIDC permission.

Before retrying an upload, look up that exact version and reconcile remote
digests. A timeout, 401 or outage is not evidence of absence. Never overwrite a
tag, unpublish, yank or use `--skip-existing` to conceal a mismatch. Fix defects
in a new version with a changelog entry.

Install each exact registry version in a fresh app and run an explicitly selected real provider workflow,
TLS and cancellation checks. Coordinate the three app agents to pin coordinates
and lockfiles, rerun integrations, then remove development archives/source aliases.
The same installation harness can select published channels after verifying
their remote contents against the reviewed bundle:

```sh
python3 scripts/test-release.py /absolute/path/to/reviewed-bundle \
  --registry npm --registry rust --registry go
```

Omitted channels still use the reviewed local archives. Add `--registry python`
only after the organization's PyPI files exist. This command performs no uploads.
Current artifacts remain valid until migration is verified. [Migration notes](/docs/migrations)
cover protocol, auth and canonical data; language versions may advance independently
while retaining an explicitly compatible wire protocol.