-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changelog as part of GitHub releases #175
Comments
Agree. |
I'll bring this up with the team, there might be some patterns we can reuse from the main Backstage repo for this. 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
The changelog of
mkdocs-techdocs-core
is now on theREADME.md
On GitHub it's a good practice to create GitHub releases with changelog there.
For example when bots like renovate bump version of a package the release note is included on the PR.
Example here that the release note is missing
If we look at backstage
Because this it creates GitHub release (https://github.com/backstage/backstage/releases)
Please consider also creating GitHub release so that people sticking package version and using tool to renovate those package have also release notes on the PR.
Thanks!
The text was updated successfully, but these errors were encountered: