# How do I create a software release in sbomify?

> Step-by-step guide to creating a product release in sbomify by linking existing component SBOMs to a versioned release.

- **Updated:** 2026-08-04

**TL;DR:** Upload your component SBOMs first, then create a product release that points to specific SBOMs. Each SBOM can have its own version and be shared across multiple releases.

## Walkthrough

Video: [How to create a software release in sbomify](https://marketing-assets.sbomify.com/screencasts/release_creation.webm). Step-by-step screencast showing how to create a product release in sbomify by linking component SBOMs.

## Creating a product release

A product release in sbomify ties together one or more component SBOMs (and other artifacts like compliance documents) under a single version. This is how you represent a shipped version of your software.

### Prerequisites

Before creating a release, you need:

- A **product** set up in sbomify (see [How do products work?](https://sbomify.com/faq/how-do-products-work-in-sbomify/))
- One or more **components** with uploaded SBOMs

### The "Latest" release

The first time an SBOM is uploaded against a product, sbomify automatically creates a `Latest` release that always points to the most recent SBOM version of each component. You don't need to manage it - it's there as a stable URL for "whatever is current".

Named releases (e.g. `v2.1.0`) are immutable snapshots and are what you should share with customers and auditors.

### Steps

1. Navigate to your **Product** and scroll to the **Releases** section
2. Click **Create Release** and fill in the modal: **Name** (e.g. `Middle-Out Rewrite`), **Version** (e.g. `v2.1.0`), and an optional **Description**, then click **Create**
3. Click into the new release
4. Click **Add Artifact**, use **Select All Visible** (or pick individual SBOMs and documents) in the artifact picker, then click **Add to Release**

### How versioning works

Component SBOMs and product releases are versioned independently. For example, your product `v2.1.0` might include a backend component at `v1.8.3` and a frontend at `v3.0.1`. The same component SBOM can also be shared across multiple product releases - if two products ship the same library version, there's no need to upload it twice.

---

From sbomify: https://sbomify.com/faq/how-do-i-create-a-software-release/
