Skip to content

chore: satisfy Registrator AutoMerge guidelines automatically#20

Merged
sotashimozono merged 1 commit intomainfrom
chore/registry-guideline-automation
Apr 15, 2026
Merged

chore: satisfy Registrator AutoMerge guidelines automatically#20
sotashimozono merged 1 commit intomainfrom
chore/registry-guideline-automation

Conversation

@sotashimozono
Copy link
Copy Markdown
Owner

Summary

Aligns this repo's CI automation with the shared registry-guideline fix
rolled out across the sotashimozono Julia package fleet (sibling PRs
on Lattice2D / QuasiCrystal / ...). Makes every future Project.toml
version bump clear Registrator's AutoMerge guidelines without any
human [merge approved] intervention.

What changes

  • release-drafter.yml
    • The breaking label now triggers the minor version-resolver, so
      any PR ticked as breaking automatically forces a minor bump.
    • Adds a 💥 Breaking changes category (unless the repo already had
      one under a different name / label).
    • Prepends ## Changelog to the rendered template body.
  • PULL_REQUEST_TEMPLATE.md — adds a Breaking change checkbox
    under Type of Change.
  • PRLabeler.yml (if present and using the standard structure) —
    bootstraps the breaking label and auto-applies it when the
    checkbox is ticked.
  • AutoRegister.yml (or AutoRegister.yml.disabled — kept
    disabled) — always wraps the drafted release notes in a literal
    ## Changelog header and a See the full changelog at ... footer
    before posting the @JuliaRegistrator register comment. This
    guarantees Registrator's required "breaking"/"changelog" keyword is
    present, which was the last remaining rejection cause on the fleet.

Why this matters

Registrator's AutoMerge guideline rejects breaking-change registrations
whose release notes lack the literal word "breaking" or "changelog".
With the wrapper in AutoRegister.yml, that keyword is always present,
so no manual re-trigger is ever needed.

Scope

This PR only touches .github/ files and is version-bump-neutral — no
Project.toml change. The next feature/fix PR on this repo will be
the first one to exercise the new flow end-to-end.

Type of Change

  • Feature (enhancement)
  • 🐛 Bug Fix (bug)
  • Performance (performance)
  • 📖 Documentation (documentation)
  • 🧰 Maintenance (chore or refactor)
  • 💥 Breaking change (breaking)

Mirrors sotashimozono/Lattice2D.jl#23: makes release-drafter,
PRLabeler, PR template and AutoRegister wrap every drafted set of
release notes with a '## Changelog' header, so Registrator's
required 'breaking' / 'changelog' keyword is always present on the
'@JuliaRegistrator register' comment. Also adds the 'breaking'
label as a first-class citizen that forces a minor version bump.
@JuliaRegistrator
Copy link
Copy Markdown

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sotashimozono sotashimozono merged commit b6a18e2 into main Apr 15, 2026
3 of 4 checks passed
@sotashimozono sotashimozono deleted the chore/registry-guideline-automation branch April 15, 2026 02:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants