From 2e323c4f3ee4a9bf38a0c8a10645dee37b7981fd Mon Sep 17 00:00:00 2001 From: David LJ Date: Thu, 7 Nov 2024 16:56:42 +0100 Subject: [PATCH] docs: replace standard-version by recommended alternatives --- content/about/index.md | 3 ++- content/next/index.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/content/about/index.md b/content/about/index.md index 2d06403..4ed50d9 100644 --- a/content/about/index.md +++ b/content/about/index.md @@ -36,7 +36,8 @@ The first draft of this specification has been written in collaboration with som * [detect-next-version](https://npmjs.com/package/detect-next-version): Parse, detect and get more metadata about given Conventional Commits. * [recommended-bump](https://www.npmjs.com/package/recommended-bump): Calculates the recommended version bump based on given Conventional Commits. * [git-commits-since](https://www.npmjs.com/package/git-commits-since): Get all (raw) commits since period or (by default) from latest git SemVer tag, plus plugins support. -* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow. +* [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version): Fork of the excellent standard-version. Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org +* [release-please](https://github.com/googleapis/release-please): generate release PRs based on the conventionalcommits.org spec * [Conventional Commit](https://github.com/lppedd/idea-conventional-commit): provides extensible context and template-based completion, and inspections, for Conventional Commits inside the VCS Commit dialog. Available for all [JetBrains IDEs](https://www.jetbrains.com/). * [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add Conventional Commits support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...). * [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are Conventional Commits compliant. Comes with Docker image for CI uses. diff --git a/content/next/index.md b/content/next/index.md index 7e0f111..6713d09 100644 --- a/content/next/index.md +++ b/content/next/index.md @@ -244,7 +244,8 @@ The first draft of this specification has been written in collaboration with som Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects. * [php-conventional-changelog](https://github.com/marcocesarato/php-conventional-changelog): a tool built to generate a changelog from a project's committing history messages and metadata and automate versioning with Semver, following Conventional Commits specs. Configurable and usable for PHP projects as a composer dependency or usable globally for non-PHP projects. * [conform](https://github.com/autonomy/conform): a tool that can be used to enforce policies on git repositories, including conventional commits. -* [standard-version](https://github.com/conventional-changelog/standard-version): Automatic versioning and CHANGELOG management, using GitHub's new squash button and the recommended Conventional Commits workflow. +* [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version): Fork of the excellent standard-version. Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org +* [release-please](https://github.com/googleapis/release-please): generate release PRs based on the conventionalcommits.org spec * [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add _Conventional Commits_ support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...). * [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are conventional commit compliant. Comes with Docker image for CI uses. * [semantic-release](https://github.com/semantic-release/semantic-release): A tool that automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package.