Kanject.Cli 2.2.0

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global Kanject.Cli --version 2.2.0
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local Kanject.Cli --version 2.2.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Kanject.Cli&version=2.2.0
                    
nuke :add-package Kanject.Cli --version 2.2.0
                    

Kanject.Cli

A single .NET global tool that drives C# AWS services from dotnet new to kanject aws deploy --env prod — wrapping the existing dotnet/AWS toolchain so your inner loop stays vanilla and the Lambda, ECS Fargate, static-site, and coupled full-stack deploy plumbing disappears behind one committed manifest.

Install

dotnet tool install --global Kanject.Cli

Requires the .NET 10 SDK or later (the .NET 11 SDK installs its .NET 11 build). The aws, msbuild, and github providers ship in the box — no extra installs.

Choose a workflow

  • Deploy applications: Lambda, ECS Fargate, or a coupled SPA/backend. Choose independent service roots, a shared multi-Lambda stack, or a coordinated frontend/backend pair.
  • Publish libraries: kanject packages init, then kanject packages plan and kanject packages verify from the package repository root.
  • Distribute desktop apps: initialize the product manifest, register with kanject add distributable, and configure delivery destinations.

Start at Getting started for workflow selection. Service commands run from the directory containing that service's manifest, which can differ from the repository or solution root. The current static-site shape requires a coupled backend.

Discover commands with kanject --help and kanject aws --help.

What it does

  • Bootstrap — kanject new scaffolds a project from a bundled template and initializes it; kanject init adds the manifest, stage files and lock file to an existing project.
  • Deploy — kanject aws deploy --env <stage> resolves cross-repo dependencies and env, builds the provider artifacts, and ships the manifest's target (Lambda, ECS Fargate, static site, or a coupled backend + site), recording every release in an S3 deployment ledger.
  • Rollback — kanject aws rollback --env prod shows the last 10 deployments with dates, statuses, targets, and commit summaries; pick one and Kanject does the target-native promotion with the prior artifact still immutable in S3/ECR.
  • And more — cross-repo dependency sync, a local test runner, env/param/secret management, static-site previews and ephemeral backend previews (kanject aws deploy --preview <NAME>), DynamoDB change feeds, a managed streaming Function URL and CloudFront edge, VPC & custom-domain wiring, multi-function services, AWS-native pipeline scaffolding, NuGet package publishing, desktop distribution, and sign-in for paid Kanject packages (kanject login, kanject add package).

It invokes — never replaces — dotnet new, dotnet build, and dotnet lambda, and drives AWS services through their SDK APIs (including CloudFormation change sets). The dotnet-native experience stays; kanject only owns the AWS plumbing that doesn't have a great answer in the box.

Learn more

License

Commercial — governed by the Kanject Code Libraries License Agreement (KCLLA); see the bundled LICENSE.md. © Kanject Business Solutions.

Product 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.  net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
2.5.0 103 11/16/2026
2.4.0 93 11/16/2026
2.3.0 113 11/15/2026
2.2.0 128 11/14/2026
2.1.0 96 11/13/2026
2.0.2 102 11/13/2026
2.0.1 94 11/13/2026
2.0.0 100 11/12/2026
1.5.1 123 11/11/2026
1.5.0 121 11/10/2026
1.4.0 106 11/4/2026
1.3.0 119 11/2/2026
1.2.0 157 11/1/2026
1.1.0 115 11/1/2026
1.0.79 111 10/30/2026
1.0.78 101 10/30/2026
1.0.77 108 10/29/2026
1.0.76 102 10/29/2026
1.0.75 100 10/29/2026
1.0.74 101 10/28/2026
Loading failed

- A rejected library wave can be seen and its intent restored (proposal 0059 P1).
 A release commit deletes the declarations it resolved before anything is published. When its release execution was then rejected at Approval, the versions were on no feed, the intent was gone from the tree, and the only way to learn why was the AWS console.
 - `kanject packages intent restore --from <release commit>` writes back, byte for byte, the declarations that commit consumed, read from its parent. You commit them and run `packages release` again. It refuses with the new `KANCLI795`, writing nothing, when the commit is not a release commit on the tracked branch, when a version it set is already published, when its execution failed at Publish (retry that stage instead), or when a file of the same name exists with different content.
 - `packages release status` says how an execution ended. A rejection, a stop and a supersession are still `Failed` in `pipeline.state`, and the report adds which (`pipeline.ending`), who and when, the approver's summary, and whether the failed stage can still be retried. The person is shown by session or user name, never the full ARN.
 - `packages release status` works on a pipeline with no rehearsal. With `rehearsal.enabled: false` in `packaging/release.pipeline.json` the stack no longer needs a rehearsal project, and the report goes by the pipeline execution. It failed `KANCLI556` before.
 - A commit pushed underneath a later one is found. Status reports the execution that carried it and names the commit that execution ran, instead of "not started". The search through the pipeline's history now stops at executions older than the commit.
 - `packages release status --pending` lists every version the checkout holds that no feed has and a release commit on the tracked branch set, with that commit and where its execution stands. It reads the full package surface and changes nothing.
 - Release commits carry a `Kanject-Release-Wave: <part>` trailer, which is how a version a release commit set is told from a manual edit. Release commits written before it are recognised by their shape. `packages release` itself accepts and refuses exactly what it did before.

- `packages release` refuses to author on top of an unpublished release commit (proposal 0059 P2).
 A release commit whose execution failed or was rejected stays on the tracked branch with versions no feed has. The next run resolved a different part and stopped with `KANCLI545` ("remove the manual version edit"), though nobody had edited anything. The front door now recognises the state while it plans, and refuses before it branches or commits.
 - `KANCLI793`: the earlier release commit's execution is still running or awaiting approval. Approve it, or reject it and restore. From the tracked branch's own tip the run stops as "already promoted" and names the execution.
 - `KANCLI794`: the execution failed, was rejected or was stopped, and the declarations the commit consumed are not back. The message names who rejected it and when, the remedy (`packages intent restore --from <commit>`), and `git revert <commit>` to drop the change. After a failed Publish only the retry is offered. With the declarations back the run carries on and ships the versions; if it resolves a higher part it names the revert instead.
 - `KANCLI796`: the pipeline cannot be read, no execution carries the commit, or the clone is shallow. `--accept-unknown-standing <commit>` carries on when the execution can never be read again; it must name the printed commit, is recorded in the release commit, and still requires the consumed declarations to be back.
 - The cost is in the rare case only. The check uses the feed listing the plan already makes, and reads the pipeline only when a version is pending. `--no-push` reads the pipeline then too.
 - A rerun keeps its release commit's intent. A rerun of `packages release` on a minor or major release commit that is not on the tracked branch yet resolved `patch`, because the commit had consumed its declarations, and failed `KANCLI545` against its own versions. It now takes the part and notes from that commit's `release.intent.json`, also when a fix was committed on top of it after a failed rehearsal.
 - `packages bump plan` names the release commit. Run directly on a full clone, its `KANCLI545` says which release commit set an unpublished version and how to restore or revert it. With no git history, or a shallow one, the message is unchanged.