infra(deps): switch to commit-and-tag-version

[ST-DDT]

Replaces the standard-version dependency with the maintained fork commit-and-tag-version.

• https://github.com/absolute-version/commit-and-tag-version
• standard-version lists this as official fork/replacement

I did some tests locally and release seems to behave the exact same as standard-version, but you might want to try it out yourself.

I also explicitly disabled the tag generation, as we generate the tags via GH releases anyway.

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	79ea746
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/663f755d187acd000878ce01
😎 Deploy Preview	https://deploy-preview-2882.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.96%. Comparing base (042c871) to head (79ea746).

Additional details and impacted files

@@           Coverage Diff            @@
##             next    #2882    +/-   ##
========================================
  Coverage   99.96%   99.96%            
========================================
  Files        2977     2977            
  Lines      215466   215466            
  Branches      950      601   -349     
========================================
+ Hits       215387   215395     +8     
+ Misses         79       71     -8     

see 1 file with indirect coverage changes

[Shinigami92]

nice

[xDivisionByZerox]

We already had a config file for standard version: https://github.com/faker-js/faker/blob/043f68b0691f1cc1c11f2257b9c9e2cfa5047c72/.versionrc.json
If I understand correctly, we can keep using it. The new config should propably go into the config file instead of the package.json.

[ST-DDT]

We already had a config file for standard version: 043f68b/.versionrc.json If I understand correctly, we can keep using it. The new config should propably go into the config file instead of the package.json.

It doesn't show up in the config spec, but seems to work anyway.
https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.2.0/README.md

[xDivisionByZerox]

It doesn't show up in the config spec, but seems to work anyway.

It's not obvious but as they state in their README:

Any of the command line parameters accepted by commit-and-tag-version can instead be provided via configuration.

In combination with the point aboth:

You can configure commit-and-tag-version either by:

1. Placing a commit-and-tag-version stanza in your package.json
2. Creating a .versionrc, .versionrc.json or .versionrc.js.