---
title: "Releasing"
description: "Build, test and pack with Task, how the version is stamped, and how a tag publishes the packages."
audience: "Maintainers"
kind: "How-to guide"
status: "Current"
version: "main · 3.3 (unreleased)"
slug: "internals/releasing"
url: "https://docs.allors.com/documents/internals/releasing/"
---

# Releasing

> **Status: Current.** How-to guide for maintainers.

This guide covers building, testing and packing the solution, and how a release reaches nuget.org. `task` wraps the `dotnet` commands; without it, `dotnet build src/Documents.slnx` and `dotnet test src/Allors.Documents.Tests` do the same work.

<a id="build"></a>

## Build

Prerequisites: [.NET SDK 10.0](https://dotnet.microsoft.com/download) and [Task](https://taskfile.dev/).

-   `task` or `task ci` — build, test and pack
-   `task test` — build and run tests
-   `task pack` — create the NuGet packages in `artifacts/nuget`
-   `task clean` — clean build outputs

Versioning is handled by [Nerdbank.GitVersioning](https://github.com/dotnet/Nerdbank.GitVersioning) (`version.json`).

<a id="release"></a>

## Release

Pushing a tag `vX.Y.Z` or `vX.Y.Z-rc.N` runs `release.yml`: it builds, tests and packs, publishes both packages to nuget.org through [trusted publishing](https://learn.microsoft.com/en-us/nuget/nuget-org/trusted-publishing) from the `nuget-release` environment, and creates a GitHub release. The package version comes from `version.json`, so set it to the tag’s version before tagging.