Automic VaultAutomic Vault

brew

Install github-release with Homebrew, Nix

Create and edit releases on Github (and upload artifacts). Version 0.11.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install github-release

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#github-release

nixpkgs package indexes · pkgs/by-name/gi/github-release/package.nix · source: api.github.com

overview

Package summary

Create and edit releases on Github (and upload artifacts)

Commands and aliases

  • github-release

history

Project history and usage

github-release is a Go command-line utility for creating, editing, deleting, inspecting, and uploading files to GitHub Releases. It belongs to the early generation of single-purpose release automation tools that wrapped GitHub's Releases API before GitHub's own CLI became the default tool for many workflows.

Project history

The project repository was created in January 2014, soon after GitHub exposed Releases as an API-backed feature. Its README framed the tool as a friendlier alternative to doing release and artifact work with raw HTTP requests, especially because uploads require resolving release identifiers before attaching files.

The project retained a narrow scope: tags and releases stay in GitHub, while the CLI handles the API calls needed to create release records, edit metadata, upload artifacts, and delete releases. Copyright notices in the README identify Nicolas Hillegeer for the original 2014-2017 period and Meter, Inc. for later maintenance.

Adoption history

github-release became useful in build scripts that produced binaries before GitHub Actions and the GitHub CLI were widely adopted. Its packaging in Homebrew and Nix reflects the role it played for developers who wanted a small standalone executable rather than a larger platform CLI.

The tool's continued packaging gives older CI and release scripts a stable command name. That matters for projects that still publish GitHub Release assets from Makefiles, shell scripts, or external CI systems.

How it is used

Practitioners use github-release by exporting a GitHub token, tagging and pushing a repository, then running subcommands such as `release`, `edit`, `upload`, `delete`, and `info`. The README also documents `GITHUB_API`, which lets the same workflow target a GitHub Enterprise API endpoint.

Why package nerds care

For package maintainers, github-release is notable because it automates the exact step that many package recipes depend on: publishing versioned binary artifacts on GitHub Releases. It is a compact example of a tool whose job is not building software, but making the release surface predictable enough for downstream package managers.

Timeline

  • 2014: Repository created for a Go CLI around GitHub Releases.
  • 2014: README examples show release creation, editing, artifact upload, deletion, and release inspection.
  • 2020: Maintenance copyright notice added for Meter, Inc.
  • 2025: v0.11.0 release published on GitHub.

Related projects

  • Related tools include GitHub's Releases API, GitHub Enterprise, GitHub CLI, and CI systems that publish build artifacts to GitHub Releases.

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:upload

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 8 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
github-releasecliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.11.0
manager updated
local dataok
upstreamcurrent
latest detectedv0.11.0

https://github.com/github-release/github-release

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:github-release
Version0.11.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/github-release
Homepagehttps://github.com/github-release/github-release
Repositoryhttps://github.com/github-release/github-release
Upstream docshttps://github.com/github-release/github-release#readme
LicenseMIT
Source archivehttps://github.com/github-release/github-release/archive/refs/tags/v0.11.0.tar.gz
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegithub-release
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

github-release

nix profile install nixpkgs#github-release
  • normalized package name match
  • Matched by: Github Release
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gi/github-release/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment