Agyloop Releasing

---
name: agyloop-releasing
description: gitflow, Conventional Commits, release-please, Trusted Publishing. Consult before branching, committing, or cutting a release.
allowed-tools: Bash(git *) Read
---

# agyloop releasing

> **Superseded — this describes a process that no longer runs.** agyloop was released
> from its own repository under its own name on PyPI. Since vibey ADR-0021 the source
> lives in the vibey monorepo, and since vibey ADR-0037 it is not published separately at
> all: the whole tree ships as the single `vibey-engine` package, released by the monorepo's
> own `release.yml`. `publish-to-pypi.yml` and release-please are inert here, and the
> TestPyPI command below cannot resolve. For the live process read the monorepo's
> `CONTRIBUTING.md` and its `vibey-releasing` skill.


```
main         ← always releasable; release-please target-branch: main
  ▲ merge commit
develop      ← default GitHub branch; feature PRs squash here
  ▲ squash-merge
feature/*    ← branch from develop, never from main
```

Never implement on `main`.

Commit: `<type>[scope]: <description>`. Hook `--strict`. Types: feat, fix,
docs, style, refactor, perf, test, build, ci, chore, revert.

Historically: first public tag **v0.1.0**, then a release-please PR on `main`,
then `publish-to-pypi.yml` (filename load-bearing) with OIDC environments
`testpypi` / `pypi` (manual approve), verified with a TestPyPI install of
`agyloop`. None of that runs now — there is no `agyloop` distribution to install.

Today a change here is released by the monorepo: it reaches an installed user
through the `vibey` wheel, `vibey-gh` derives the version from the range, and
`pip install vibey-engine` puts `agyloop` on PATH.

See `docs/contributing/release-process.md` (also superseded, kept as the record of
why each gate existed) and the monorepo's `vibey-releasing` skill for the live one.