@anolilab/semantic-release-preset 1.2.1 → 2.0.0

package/CHANGELOG.md

@@ -1,3 +1,21 @@
+## @anolilab/semantic-release-preset [2.0.0](https://github.com/anolilab/javascript-style-guide/compare/@anolilab/semantic-release-preset@1.2.1...@anolilab/semantic-release-preset@2.0.0) (2022-02-15)
+
+
+### ⚠ BREAKING CHANGES
+
+* remove old node version from our supported versions
+
+Signed-off-by: prisis <d.bannert@anolilab.de>
+
+### Bug Fixes
+
+* markdown lint ([24059d4](https://github.com/anolilab/javascript-style-guide/commit/24059d41ca682ca21b39ad7f6dff594be734329d))
+
+
+### Performance Improvements
+
+* support for v12, v14 was removed from our supported versions of node ([83d6a80](https://github.com/anolilab/javascript-style-guide/commit/83d6a8058ed7791135aff03d4cd734327bb1b694))
+
 ### @anolilab/semantic-release-preset [1.2.1](https://github.com/anolilab/javascript-style-guide/compare/@anolilab/semantic-release-preset@1.2.0...@anolilab/semantic-release-preset@1.2.1) (2022-01-11)
 
 

package/README.md

@@ -128,8 +128,8 @@ Add `cz` to your `package.json scripts`
 
 Ensure that your CI configuration has the following environment variables set:
 
-- GITHUB_TOKEN: [A GitHub personal access token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)
-- NPM_TOKEN: [A npm personal access token](https://www.npmjs.com/settings)
+- GITHUB_TOKEN: [A GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
+- NPM_TOKEN: [A npm personal access token](https://www.npmjs.com/package/settings)
 
 You can test your config with a dry run:
 
@@ -252,7 +252,7 @@ jobs:
 
 ## Note on GitHub protected branches
 
-If you’re releasing a [GitHub protected branch](https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) you need to change the git committer to an owner/admin and allow repo admins to bypass the branch protection (make sure "include administrators" is disabled in the branch protection rules.)
+If you’re releasing a [GitHub protected branch](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches) you need to change the git committer to an owner/admin and allow repo admins to bypass the branch protection (make sure "include administrators" is disabled in the branch protection rules.)
 
 If your repo is under an organisation, you can create a bot account and give it admin rights on the repo. If your repo is under a personal account, you have no choice to make the repo owner the commiter for the release.
 
@@ -263,7 +263,7 @@ Either way, you have to create a GitHub personal access token for the committer
 ## Supported Node.js Versions
 
 Libraries in this ecosystem make the best effort to track
-[Node.js' release schedule](https://nodejs.org/en/about/releases/). Here's [a
+[Node.js’ release schedule](https://nodejs.org/en/about/releases/). Here’s [a
 post on why we think this is important](https://medium.com/the-node-js-collection/maintainers-should-consider-following-node-js-release-schedule-ab08ed4de71a).
 
 Contributing

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@anolilab/semantic-release-preset",
-    "version": "1.2.1",
+    "version": "2.0.0",
     "description": "Anolilab Coding Standard for semantic-release.",
     "keywords": [
         "anolilab",
@@ -70,7 +70,7 @@
         "semantic-release": "^18.0.1"
     },
     "engines": {
-        "node": ">=12"
+        "node": ">=16"
     },
     "publishConfig": {
         "access": "public"