Releases and Tags

A tag marks a commit as significant — typically a version like v1.2.0. A release builds on a tag by adding human-readable notes and optional file attachments so users can browse and download specific versions from the web UI.

Create a Tag

You can create a tag from the UI or from your local clone.

From the UI:

1. Open your repository and select Releases, then Tags.
2. Select Create Tag.
3. Enter a tag name (for example, v1.2.0), choose the target branch or commit, and select Create Tag.

From the command line:

git tag v1.2.0
git push origin v1.2.0

To tag a specific past commit, pass its commit ID instead of relying on HEAD:

git tag v1.2.0 abc1234
git push origin v1.2.0

Publish a Release

1. Open your repository and select Releases.
2. Select New Release.
3. In the Tag Name field, choose an existing tag or type a new name to create one at the current default branch tip.
4. Enter a Release Title and write release notes in the Markdown body — changelogs, upgrade instructions, and known issues all belong here.
5. Select This is a pre-release if the version isn’t ready for general use, or Save Draft to finish it later without publishing.
6. Select Publish Release when it’s ready.

Note

Draft releases are visible only to repository members with write access. A pre-release is visible to everyone with access but is excluded from the “Latest” designation on the repository overview.

Attach Files

Uploaded files appear on the release page as named download links alongside the auto-generated source archive.

1. On the new or edit release form, go to the Attach Files section.
2. Drag files onto the upload area, or select it to browse — built binaries, compressed archives, checksums, and signatures are all common choices.
3. Repeat for each file, then publish or update the release.

Keep individual files reasonable in size so downloads stay fast for your team.

Tip

For installable packages — npm modules, container images, PyPI wheels, and similar — the package registry is a better fit than release attachments. It understands version resolution, dependency metadata, and client tooling (npm, pip, docker pull) in ways a plain file download doesn’t.

View and Download Releases

1. Select Releases to see the full list, newest first.
2. The latest non-prerelease is highlighted with a Latest badge.
3. Each entry shows the tag name, release title, notes, and links to:
   • Source code — auto-generated zip and tar.gz archives of the tagged commit.
   • Assets — any files you attached when publishing the release.
4. Select a file link to download it directly, or copy the URL to share it.

To compare two releases, open their tag names as a compare URL:

https://git.example.plaidcloud.com/you/my-repo/compare/v1.1.0...v1.2.0

Next Steps

• Publish Packages
• Work with Repositories