Repository navigation
Only include app changes in release notes - #50
Merged
Merged
Conversation
siewers
added
the
maintenance
siewers
changed the title
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.
Release notes should only describe changes to the app.
Excluded from generated release notes:
documentation: README and other docsmaintenance: build, CI, release toolingdependencies: every Dependabot pull request (NuGet packages, GitHub Actions, .NET SDK)The Maintenance and Dependency updates sections are removed. To mention a dependency update that matters to users, such as a framework upgrade, open it as a separate pull request labeled
enhancementorbug(like the Avalonia 12 update, #36). AGENTS.md describes the rule.Preview against v1.0.0-beta.1 with this config: New features (#36) and Bug fixes (#47) only.