---
title: "Create a Release"
slug: "create-a-release"
updated: 2026-10-26T13:20:56Z
published: 2026-10-26T13:20:56Z
canonical: "learn.allspice.io/create-a-release"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.allspice.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Release

This guide explains how to create a hardware Release in Allspice after your design work has been reviewed, approved, and merged.

A Release gives your team a named snapshot of the repository at a specific point in time. It is the right place to attach manufacturing outputs, assembly documentation, and release notes for handoff.

## When to create a Release

Create a Release when:

- a Design Review has been approved and merged
- the repository contains the exact files you want to freeze for manufacturing or handoff
- you want a permanent, shareable checkpoint for a board revision

In most teams, the typical flow is:

1. Finish design changes on a working branch.
2. Open a Design Review and collect feedback.
3. Merge the approved Design Review.
4. Create a Release from the approved repository state.
5. Attach manufacturing and documentation files to the Release.

## What to include in a hardware Release

A Release usually combines a repository snapshot with the files needed by downstream teams.

Common attachments include:

- Gerber files, ODB++, or IPC-2581 exports
- drill files
- pick-and-place or X/Y placement files
- assembly drawings
- fabrication drawings
- test procedures
- bills of materials (BOMs)
- Release notes describing the revision

## Before you publish

Before creating the Release, confirm:

- the Design Review is merged or otherwise approved
- the selected commit or branch reflects the final intended revision
- your Release title is clear and versioned consistently
- your notes explain what changed and what the Release is for
- any manufacturing output files are ready to upload

## Step-by-step guide to create a new Release

[Create a New Release in Your Project Repository](https://demo.arcade.software/DM9dbr36TpAljIKFgH8A?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true)

1. Open your project repository in Allspice.
2. Navigate to the `Releases` tab. ![Image](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(188).png)
3. Click `New Release`. ![Image](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(189).png)
4. Choose the branch, tag, or commit you want the Release to represent.
5. Add a title for the release. This is usually your PCB version/revision number V2, r17, etc.
6. Enter a clear Release title, such as the board name plus revision or version number. ![Image](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(190).png)
7. Add Release notes that summarize the important design changes, status, or manufacturing intent.
8. Upload any supporting files your collaborators, manufacturing partners, or assembly team will need.
9. Review the information to make sure the Release points to the correct repository state.
10. Click `Publish Release`. ![Image](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(192).png)

![Image](https://cdn.document360.io/3d44af5c-3f49-4ca5-b152-10836a885c13/Images/Documentation/image(193).png)

After publishing, the Release becomes a stable reference point your team can return to later.

## Recommended next steps

After the Release is published, share it with the people who need it and confirm they have the correct attached outputs for fabrication, assembly, or test.