# Release

Cut and maintain Agentic Resource Registry release branches, prepare alpha, beta, RC...

- Repository: https://github.com/AgenticResourceRegistry/AgenticResourceRegistry (4535 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill release -g -a claude-code -y`
Codex: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill release -g -a codex -y`
Cursor: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill release -g -a cursor -y`
Gemini CLI: `npx skills add AgenticResourceRegistry/AgenticResourceRegistry --skill release -g -a gemini-cli -y`

## Description

Cut and maintain Agentic Resource Registry release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Agentic Resource Registry maintainer release tasks and release-process changes, not for installing or upgrading an existing Agentic Resource Registry deployment.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Agentic Resource Registry release operations

This is a repository-local maintainer skill, not a bundled end-user skill or an `observal` CLI command. Read the [release guide](../../../docs/self-hosting/releasing.md) completely before acting. Use the existing [release tool](../../../tools/release.py); do not implement a second release pipeline.

Resolve these links from the skill directory. Run commands from the Agentic Resource Registry checkout root. Examples use `release/1.14` and PR `123`; substitute the explicitly requested line and PR, never treat examples as authorization.

## Safety and authority

- Obtain approval before remote branch creation, pushes, PR creation, merges, workflow retries, or publishing, unless the current request explicitly authorizes that action. Preparing a PR does not authorize merging it or approving a production environment.
- Explain before merging a preparation PR that it triggers publication, subject to the workflow approval gate. The newest verified stable release also triggers hosted deployment.
- Never publish from `main`, merge a release branch back into `main`, rebase a release line onto `main`, force-push published history, or move an existing tag.
- `main` carries the next minor `X.Y.0-dev.0` version, never a published release version. Release versions, changelog, and `.release.toml` live only on release branches.
- Land ordinary fixes on `main` first. Each affected release line gets its own reviewed backport PR with `cherry-pick -x` provenance.
- Never bypass failed checks, reviews, signing, or checksum verification. Never expose tokens, environment files, GitHub App keys, or OIDC material.
- Production rulesets, environment restrictions, trusted publishers, deployment changes, and Terraform apply require separate authorization. This skill does not change infrastructure or provision resources.
- Do not run `uv publish`, `gh release create`, or `git tag` as a substitute for the release workflow.

## Inspect first

The rest: https://github.com/AgenticResourceRegistry/AgenticResourceRegistry/blob/HEAD/.agents/skills/release/SKILL.md