-
-
Notifications
You must be signed in to change notification settings - Fork 919
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
infra: changelog generation #1304
Conversation
Current Dry Run Sample (will be updated regularly)Changelog8.0.0 (2023-01-21)Features
Bug Fixes
New Locales |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## next #1304 +/- ##
=======================================
Coverage 99.64% 99.64%
=======================================
Files 2340 2340
Lines 242612 242612
Branches 1103 1103
=======================================
Hits 241760 241760
Misses 831 831
Partials 21 21 |
That looks somewhat interesting 😲 But should we put "effort" into configuring it when we actually want to move away from that dependency? Please be sure that the title of that linked issue is not really up to date anymore, as I'm not sure if we really want to use But I'm heavily and in conflict with myself what would be best for the project in the long run as I didn't have build up enough knowledge yet |
This didn't took too long to research. So "putting effort" into it would only be if we accept my suggestion. Currently, this PR fixes our problem with locale changes not showing up. This should have priority. |
Yes, but on the other side we documented and changed the way how we name PR titles and so this fixed the problems with locales as well + it provided us a really helpful convention/structure of PR titles |
06aa9c7
to
beefd46
Compare
We wait with merging till v8, to start with a "fresh" new changelog style. |
This PR introduces configuration for our CHANGELOG file according to the
standard-version
package.You can see what commands would be run, without committing to git or updating files by using the dry run mode:
npm run release -- --dry-run
I will provide a sample below.
Fixes #1244