Release Pipeline

The Release Pipeline automates everything between finishing your code and publishing a new version of your project. CC Gate runs the tests, bumps the version number, builds the project, and creates a GitHub release — all in one click.

This is for your projects, not CC Gate itself. The Release Pipeline is a tool you use to release your own apps and packages — it works on any project CC Gate is tracking.

What it does

When you start a release, CC Gate works through these steps automatically:

1

Runs your tests

Makes sure nothing is broken before the release goes out. If tests fail, the release stops here — your code is unchanged.

2

Bumps the version

Updates the version number in your project automatically. You choose whether it's a patch (1.2.3 → 1.2.4), minor (1.2.3 → 1.3.0), or major (1.2.3 → 2.0.0) bump.

3

Builds the project

Creates the release build. You can watch the output in real time as it runs.

4

Commits the version bump

Creates a clean, separate commit just for the version change — something like chore: release v1.2.4.

5

Tags the release

Creates a git tag like v1.2.4 on the release commit.

6

Pushes to GitHub

Sends the commit and the tag to GitHub so they're visible to everyone.

7

Creates a GitHub Release

Publishes a Release page on GitHub with auto-generated release notes based on your recent commits. You get a link to view it when it's done.

Supported project types

CC Gate detects your project type automatically and picks the right build and test commands.

Swift

Build and test with the standard Swift tools.

JavaScript / Node.js

Build and test via npm scripts.

Python

Runs your test suite with pytest.

C# / .NET

Build and test with the .NET toolchain.

You can also set a custom test or build command if your project uses something different.

How to start a release

  1. Make sure you're on the main branch of your project in CC Gate.
  2. Commit your latest changes first.
  3. Click the Release button that appears after committing.
  4. Choose your version bump type: patch, minor, or major.
  5. Confirm and watch it run.

CI/CD Setup wizard

If your project doesn't have automated tests yet, CC Gate can set them up for you. When you start your first release, it checks whether your project already has a test configuration. If not, it offers to create one — a GitHub Actions workflow that runs your tests automatically whenever you push.

The wizard asks a few simple questions and generates the config file. You don't need to know anything about GitHub Actions to use it.

Stopping a release

You can cancel at any step before the push happens. If tests fail, CC Gate stops automatically and shows you the error. Nothing is committed, tagged, or pushed — your project is exactly as you left it.

Once pushed, a release is public. If you accidentally release a broken version, create a new patch release rather than trying to delete the tag. Deleting published tags can cause problems for anyone who already downloaded or referenced that version.

Troubleshooting

Tests are failing and blocking the release

Fix the failing tests first — that's usually the right answer. If the failures are unrelated to your change and you need to release anyway, you can disable the "Require passing tests" option in the release configuration panel.

Build errors

The build output scrolls in real time. Read through it to find the specific error, fix it in your editor, then start a new release. The version number won't be bumped twice — only successful releases bump the version.

Version file not found

CC Gate looks for common version files automatically. If your project stores the version number in an unusual place, open the release wizard and point it to the right file.