Triggers
Auto release triggers
Not every team tags. Yanib supports several trigger modes. Pick one per repo from Repos → [repo] → Settings.
Tag (default)
Release is generated when you publish a GitHub/GitLab Release. Best when you already use semantic versioning.
PR merge
Every merged PR becomes its own release. Good for continuous deployment where each PR ships to production. Each release gets an auto generated tag like release-2026-04-20-a3f1.
Scheduled batch
Accumulates merged PRs and bundles them into one release on a daily, weekly, or monthly schedule. The sweet spot for teams that ship frequently but want fewer, bigger story posts.
Auto publish
An opt in toggle on any of the above. Skip the draft review step and publish straight to every channel. Use carefully.
Switching modes is safe. Existing releases stay, and the next trigger picks up from where you left off. Merged PRs that haven't been released yet sit in a running draft list you can see any time under Repos → [repo] → Overview.