chore: rename release config and add CI/dependency sections - #17
Merged
Conversation
Match the .yaml extension used by every workflow in .github/workflows. GitHub reads the release notes config from either .github/release.yml or .github/release.yaml, so the rename alone changes no behaviour. Co-Authored-By: Claude <noreply@anthropic.com>
Renovate now opens PRs labelled `renovate`, which previously landed in "Other changes" alongside everything uncategorised. Give them their own section, and add a CI section for workflow and tooling changes. Both categories sit above the catch-all, since GitHub assigns each PR to the first matching category. The `ci` and `renovate` labels were created in the repository to match. Co-Authored-By: Claude <noreply@anthropic.com>
3 tasks
lan496
marked this pull request as ready for review
September 6, 2026 07:56
lan496
enabled auto-merge
September 6, 2026 07:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/release.ymlto.github/release.yamlto match the extension used by every workflow in.github/workflows.CIcategory (labelci) and aDependency updatescategory (labelrenovate) to the generated release notes.Renovate went live on this repository today and labels every PR it opens with
renovate. Without a category those PRs all land in "Other changes" next to everything else uncategorised, which will dominate the notes once the weekly updates start flowing.Both new categories sit above the
*catch-all, because GitHub assigns each PR to the first category it matches.Notes for the reviewer
91dbe60is a pure rename with no content change (git showreports 100% similarity); the behavioural change is isolated in3bf48a5.The rename is safe: the REST API reference for "Generate release notes content for a release" states that when
configuration_file_pathis unspecified, "the configuration file located in the repository at '.github/release.yml' or '.github/release.yaml' will be used". The web UI docs mention only.yml, which is why this is worth calling out.The
ciandrenovatelabels did not both exist; they have been created in the repository so the categories actually match something.Test plan
[Claude Code] Generated with Claude Code