---
title: GitHub Releases
---

# GitHub Releases

## What it is

> **REMOVED from Omniscio core (in-core GitHub detachment).** This built-in gh:\* GitHub
> feature has been removed; install the **github-integration** marketplace plugin for
> it. This page is kept for historical reference.

> **Status: the built-in GitHub feature is FULLY REMOVED (plugin-only).** The in-core code is gone — there is no longer any way to restore it (the old Settings > Lab > "Built-in GitHub (legacy)" toggle and the `AMC_SHOW_INCORE_GITHUB` env var no longer exist). It is superseded by the **GitHub Integration** marketplace plugin, which has full parity plus a codebase browser, a unified siderail, and a repo navigator. Install the plugin for GitHub features.

View a repository's releases and create a release without leaving Omniscio. This is the last common reason to open github.com for day-to-day work.

## Where to find it

### Where

The "GitHub Releases" tab in the left sidebar. It uses the same GitHub CLI connection that GitHub Notifications, Pull Requests, Issues, and Code Search already use. The tab ships behind an in-development flag (`githubReleasesEnabled`, gated through the unreleased-feature registry); flip it to `shipped` to release.

## How it behaves

### How it works

1. Pick a repository in the sidebar (your own repos, or type `owner/repo`). Its releases load newest-first, each with Latest, Pre-release, and Draft badges.
2. Click a release to see its notes (rendered Markdown), its assets (read-only: name, size, download count, each opens on GitHub), and its flags. There is no in-app asset upload or download.
3. Click the "New release" button to create one.

### Creating a release

The New Release dialog defaults to a **draft** because a release is outward-facing (it publishes a git tag and a public release).

- **Tag**: pick an existing tag, or create a new one. A new tag needs a target branch (where the tag will point); GitHub creates the tag server-side.
- **Title**: optional (GitHub defaults it to the tag).
- **Release notes**: write them by hand, and/or tick "Auto-generate notes from commits". They are independent: GitHub appends the generated notes to whatever you write.
- **Publish**: "Save as draft" (private to you and repo collaborators, nothing goes live) or "Publish now" (creates a public release and the git tag immediately). Draft is the default.
- **Mark as pre-release**: flags the release as not production-ready.
- **Set as the latest release**: shown only when publishing a non-prerelease.

The write goes through the GitHub REST API (`gh api repos/{owner}/{repo}/releases`), never `gh release create`, so it never touches your local git checkout and the feature can never push a tag from your machine.

### Good to know

- Creating a release needs the repo permission. The dialog grants it the first time, using the same flow as merging a PR or creating an issue.
- After a successful create, the dialog shows the result and a "View on GitHub" link. The new release may take a moment to appear in the list.
- Errors are shown in plain language (for example "that repository could not be found"); raw GitHub or HTTP text is never surfaced.
- Editing or deleting an existing release is not built in; do that on GitHub.

## Related

GitHub Notifications setup (the shared `gh` connection), Pull Requests, GitHub Issues, Code Search.