From a7caaf7404542bc57c1df908f059de235a7d1ddb Mon Sep 17 00:00:00 2001 From: Ryoya Tamura Date: Tue, 10 Mar 2026 17:09:47 +0900 Subject: [PATCH 1/2] Add release notes configuration and PR label guidelines Add .github/release.yml to categorize auto-generated release notes by PR labels (breaking, enhancement, bug, performance, documentation, dependencies). Document PR labeling conventions in AGENTS.md so agents apply the correct label when creating PRs. Co-Authored-By: Claude Opus 4.6 --- .github/release.yml | 29 +++++++++++++++++++++++++++++ AGENTS.md | 15 +++++++++++++++ 2 files changed, 44 insertions(+) create mode 100644 .github/release.yml diff --git a/.github/release.yml b/.github/release.yml new file mode 100644 index 0000000..fb75917 --- /dev/null +++ b/.github/release.yml @@ -0,0 +1,29 @@ +changelog: + exclude: + labels: + - duplicate + - invalid + - wontfix + - question + categories: + - title: Breaking Changes + labels: + - breaking + - title: New Features + labels: + - enhancement + - title: Bug Fixes + labels: + - bug + - title: Performance + labels: + - performance + - title: Documentation + labels: + - documentation + - title: Dependencies + labels: + - dependencies + - title: Other Changes + labels: + - "*" diff --git a/AGENTS.md b/AGENTS.md index b33b965..22d7b91 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -459,3 +459,18 @@ Plan files (implementation plans, design docs, etc.) go in `.claude/plans/`. - **PR / Issue titles**: Always in English. - **PR / Issue body**: English by default unless otherwise specified. - **PR assignee**: Always use `--assignee @me` to assign the PR to the current user. + +### PR Labels + +PRs must have at least one label for release note categorization (`.github/release.yml`). Apply the most specific label: + +| Label | When to use | +| --------------- | ---------------------------------------------------- | +| `breaking` | Breaking changes (removal, rename, behavioral shift) | +| `enhancement` | New features | +| `bug` | Bug fixes | +| `performance` | Performance improvements | +| `documentation` | Documentation-only changes | +| `dependencies` | Dependency updates (auto-applied by dependabot) | + +PRs without these labels appear under "Other Changes" in release notes. From bcb22b2adeffcda0d15e47b27954f2c19c52214a Mon Sep 17 00:00:00 2001 From: Ryoya Tamura Date: Tue, 10 Mar 2026 17:14:06 +0900 Subject: [PATCH 2/2] Clarify enhancement label scope in PR labeling guidelines Co-Authored-By: Claude Opus 4.6 --- AGENTS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 22d7b91..c0bb018 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -473,4 +473,6 @@ PRs must have at least one label for release note categorization (`.github/relea | `documentation` | Documentation-only changes | | `dependencies` | Dependency updates (auto-applied by dependabot) | +Use `enhancement` only for end-user-facing features — changes that a `bee` CLI user would notice. CI configuration, repo maintenance, developer experience improvements, and internal refactors do not qualify and should be left unlabeled (they appear under "Other Changes"). + PRs without these labels appear under "Other Changes" in release notes.