ReleaseGen 0.4.0
dotnet tool install --global ReleaseGen --version 0.4.0
dotnet new tool-manifest
dotnet tool install --local ReleaseGen --version 0.4.0
#tool dotnet:?package=ReleaseGen&version=0.4.0
nuke :add-package ReleaseGen --version 0.4.0
ReleaseGen
ReleaseGen is an opinionated .NET CLI for building, packaging, and publishing .NET projects. One strict releasegen.json manifest drives every stage of a release: build, test, package, and publish.
Install
dotnet tool install ReleaseGen -g
Requires the .NET 10 SDK. The tool command is releasegen. Running bare releasegen prints command help; no stage executes without an explicit verb.
Quickstart
# 1. Write a minimal releasegen.json in the current directory
releasegen init
# 2. Edit releasegen.json: name your targets (projects and their artifact kinds),
# declare runtimeIdentifiers, and optionally add test and publish sections
# 3. Run the pipeline the manifest names, in manifest order
releasegen run
Notes:
initis a one-shot command and takes no part in the chained run. It refuses to overwrite an existing manifest unless you pass--overwrite;--preset <name>seeds the manifest'sbuild.presetkey.runis the chained run: it executes the stages the manifest names - build always, test when a test section is declared, package and publish when targets declare package kinds - in manifest order, aborting at the first failed stage and noting each skipped stage. The test outcome is carried to publish, so tests never run twice.- Each stage is also its own command -
releasegen build,releasegen test,releasegen package,releasegen publish- and all of them share the same manifest, discovered by walking up from the current directory.
Build output stays local under a release/ directory; the only network destination is the publish stage's NuGet source. Publishing is gated on your tests: a manifest declaring a test section blocks publish when that stage fails.
Commands
| Command | Purpose |
|---|---|
init |
Write a minimal manifest (one-shot) |
build |
Publish release binaries per target and runtime identifier |
test |
Run the projects the manifest's test section names |
package |
Pack the package kinds each target declares |
publish |
Push packages to NuGet sources (test-gated) |
run |
Chained run of the stages above, in manifest order |
Every command accepts the global --quiet flag; every stage command and run also accept
--dry-run and --verbose (which contradict --quiet); exit code is 0 on success and 1
on any failure. See the command reference for flags and behavior.
Documentation
- Changelog
- Command reference
- Manifest schema
- Build presets
- Single-file rules
- Trusted publishing in CI
- Stage handoff contract
- Glossary
What ReleaseGen isn't
- A changelog or release notes generator/formatter.
- A test coverage checker.
- An artifact uploader: ReleaseGen writes release binaries and archives to a local
release/directory and performs no upload of them. - A token broker: ReleaseGen performs no OIDC token acquisition; see the trusted publishing page for the CI-side procedure.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.4.0 | 94 | 11/9/2026 |
| 0.3.0 | 102 | 11/4/2026 |
| 0.2.0 | 113 | 11/1/2026 |
| 0.1.0-alpha.0 | 75 | 10/25/2026 |
# Changes since 0.3.0
## Added
- **NuGet API key via environment on .NET SDK 10.0.300+** — `publish` now delivers the API key to `dotnet nuget push` through the `NUGET_API_KEY` environment variable on .NET SDK 10.0.300+ (NuGet 7.6), so it never appears on the command line or in the process listing; older .NET SDKs (or an unresponsive probe) fall back to `--api-key`. The .NET SDK probe runs only after every early-exit condition, and printed push lines name the channel, never the key value.
- **`dotnet-releaser` migration skill** — `skills/dotnet-releaser-to-releasegen-migration/` guides migrating a dotnet-releaser (TOML) pipeline to ReleaseGen: TOML config inventory, manifest translation, a coverage report, a dry-run validation gate, and a CI rewrite. It is backed by a mapping table that classifies each surface as Mapped, Manual action required, or No ReleaseGen equivalent.
- **`releasegen build --rids <rids>`** — a comma-separated subset of the manifest's `runtimeIdentifiers` for the current invocation only (same escape posture as `--preset`): it is never written to the manifest and may only narrow the manifest's declared set, never adding a RID the manifest does not specify. Entries match case-insensitively, de-duplicate, and keep the manifest's spelling; an empty/blank/out-of-set value is refused with a named error before any publish is planned.
## Changed
- Pinned `Microsoft.Build` package to 18.9.6 since newer versions don't support .NET 10
- Dependencies: Meziantou.Analyzer to 3.0.322.
- Documentation for commands, stage handoff, and trusted publishing now describes how the API key reaches the spawned push (environment on .NET SDK 10.0.300+, `--api-key` argument otherwise).