Mark your PRs with the following labels, as appropriate:
breaking-change: if the PR includes a breaking changeenhancement: if the PR enables / completes a new featurebug: if the PR fixes a bug.dependencies: if the PR updates dependenciesdocumentation **: If the PR doc-only changessubtask **: If the PR is only part of a new feature. Ensure final PR is marked withenhancement.chore **: a maintenance / non-feature released task of no interest to users.
Labels marked with ** are excluded from release notes
- Read the contributing guide
- PR should be motivated, i.e. what does it fix, why, and if relevant, how
- Ensure relevant issues are linked (description should include text like "Fixes #")
- Ensure any appropriate documentation has been added or amended