Skip to main content

Trigger a Release

You can trigger a release build from the Library Detail page. A release build compiles the library source code and publishes a versioned artifact (e.g. JAR, NuGet package, or npm module) that other components can consume as a dependency.

How to Trigger a Release​

Click + New Release in the Build History section, or select Release from the Choose Action dropdown.

Library release

  1. Branch — select the branch to build the release from (e.g. main)
  2. Version — CodeNOW tracks all previously released versions of the library, so you don't need to remember the current version. Simply click Major, Minor, or Patch to bump the appropriate part of the version number according to semantic versioning — CodeNOW computes the next version automatically. You can also enter a custom version manually.
tip

If you use the branch naming pattern release/<major>.<minor> (e.g. release/1.2), CodeNOW automatically calculates the next patch version for that branch.

Click Confirm to start the release build. The build progress and result are visible in the Build History section on the library detail page.

Incomplete Build​

A library release build is marked as Incomplete when the CI pipeline does not produce all required results. For libraries, the required results are git-tag and the corresponding package registry result — maven for Java, npm for JavaScript, or nuget for .NET libraries. See Incomplete Build for details on how to resolve this.