faker
faker copied to clipboard
infra: changelog generation
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:
- switch up project locally (if you haven't already)
- switch to this branch
- run
npm run release -- --dry-run
I will provide a sample below.
Fixes #1244
Current Dry Run Sample (will be updated regularly)
Changelog
8.0.0 (2023-01-21)
Features
- company: add realistic Hungarian company names (#1758) (2e6b136)
- helpers: add new faker.helpers.weightedArrayElement (#1654) (59824e6)
- helpers: allow empty string in fake (#1679) (f0d2ffb)
- locales: add mergeLocales utility (#1707) (788fce0)
- number: add binary and octal random number generation (#1708) (d3229fc)
- person: add short bio (#1696) (2a2e054)
- person: split prefix into gendered versions (#1665) (27dff93)
- string: add binary and octal random string generation (#1710) (80e0a96)
- string: generate string from characters (#1717) (47b2cfc)
- string: nanoid (#1716) (099e76c)
Bug Fixes
- internet: fix invalid emails in some locales (#1746) (1e4e869)
- locale: filter inappropriate words in the en locale (#1745) (dfa647d)
New Locales
Codecov Report
Merging #1304 (27216e1) into next (54cc87d) will not change coverage. The diff coverage is
n/a.
:exclamation: Current head 27216e1 differs from pull request most recent head 2b2b42e. Consider uploading reports for the commit 2b2b42e to get more accurate results
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?
- #1096
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 changesets or an alternative like described in the issue itself
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
But should we put "effort" into configuring it when we actually want to move away from that dependency? [...] 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. So if we change our release package, it should also be able to be customizable as well.
But should we put "effort" into configuring it when we actually want to move away from that dependency? [...] 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. So if we change our release package, it should also be able to be customizable as well.
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 So there is not so much randomness in the titles anymore But this PR is not only good for showing up locales, but actually separating them from the features-segment, and that could be a good thing :thinking:
We wait with merging till v8, to start with a "fresh" new changelog style.