Markdown for LLMs

Check and release a package

The source Markdown for this article. Copy it into your assistant or download it as a text file.

# Check and release a package

Follow an existing model through checks, review, acceptance and publication. This is a route to the canonical instructions; each stage keeps its own tool versions, evidence and limits.

## Choose your workspace

**External package author:** work in your own package with the public CLI and the documented review artifacts. Start with the [CLI working session](/cli/packages-cases/) and the [Handbook workflow](/handbook/workflow/).

**Core repository contributor:** the [team workflow](/corpus/team-workflow/) also describes repository CI profiles. Those scripts belong to that workspace; they are not prerequisites for publishing a package from an external project.

## Prepare the candidate

1. [Define scope](/handbook/scope/) and [pin the source edition](/handbook/pin-editions/). Name excluded material and source standing.
2. Record the [modeling decisions](/handbook/decisions/) and the [dependencies you reuse](/handbook/reuse-dependencies/). For several packages, use [Corpus boundaries](/corpus/package-boundaries/) and [shared vocabulary](/corpus/vocabulary/local-and-shared/).
3. Prepare [scenarios](/handbook/scenarios/) and [properties and mutations](/handbook/properties-mutations/), then inspect [coverage and quality](/handbook/coverage-quality/).

## Review and accept

Run the [semantic review](/handbook/semantic-review/) and [technical review](/handbook/technical-review/). Keep their findings and opinions distinct. Follow [candidate acceptance](/handbook/accept-release/) to record the verdict, tool version and honest limits. An agent review does not imply independent human approval.

The Handbook's worked candidate has specific recorded limits. Do not treat its verdict as acceptance of a different package or tool version.

## Publish the appropriate artifact

Read [Publishing a release](/corpus/releases/publishing/) for pack, publish and pin, including the distinction between artifact formats. Check [versions and language lines](/corpus/releases/compatibility/) before selecting a release. Preserve the candidate's accepted scope and limits with its artifacts.

## Change and replay

When the source, model or dependency changes, start with [Revisit after change](/handbook/revisit-after-change/), inspect [consumer impact](/corpus/changes/impact/) and follow [Upgrades and replay](/corpus/releases/replay-and-upgrades/).

For an application consuming that package, continue with [application versioning](/build/application/versioning/). For your own Arxo service, use [Operate upgrades](/operate/upgrades-compatibility/) and its deployment verification record.

## Continue by task

- Ready to distribute the accepted artifact? Follow [Publishing a release](/corpus/releases/publishing/).
- A source or dependency changed? Start with [Revisit after change](/handbook/revisit-after-change/).
- Updating a consuming application? Use [Application versioning](/build/application/versioning/).