Closed jriddle-linode closed 7 months ago
What does this PR do and why is this change necessary?
Updates to use githubs built in release notes and using the following labels.
**NOTE**: The labeler job is dry running on the PR to show what it will do, doesn't execute until we merge.
breaking-change: any changes that break end users or downstream workflows
bugfix: changes that fix a existing bug
new-feature: changes that add new features such as endpoints or tools
improvement: changes that improve existing features or reflect small API changes
testing: improvements to the testing workflows
repo-ci-improvement: improvements to the CI workflow, like this PR!
documentation: updates to the package/repo documentation or wiki
dependencies: Used by dependabot mostly
ignore-for-release: for PRs you dont want rendered in the changelog, usually the release merge to main
📝 Description
What does this PR do and why is this change necessary?
Updates to use githubs built in release notes and using the following labels.
**NOTE**: The labeler job is dry running on the PR to show what it will do, doesn't execute until we merge.⚠️ Breaking Change
breaking-change: any changes that break end users or downstream workflows
🐛 Bug Fixes
bugfix: changes that fix a existing bug
🚀 New Features
new-feature: changes that add new features such as endpoints or tools
💡 Improvements
improvement: changes that improve existing features or reflect small API changes
🧪 Testing Improvements
testing: improvements to the testing workflows
⚙️ Repo/CI Improvements
repo-ci-improvement: improvements to the CI workflow, like this PR!
📖 Documentation
documentation: updates to the package/repo documentation or wiki
📦 Dependency Updates
dependencies: Used by dependabot mostly
Ignore For Release
ignore-for-release: for PRs you dont want rendered in the changelog, usually the release merge to main