From 0cc5286cfa3bb0247a077bc605b835ba329fef73 Mon Sep 17 00:00:00 2001
From: Christoph Witzko <github@christophwitzko.com>
Date: Tue, 7 Feb 2023 11:57:13 +0100
Subject: [PATCH] docs: several improvements
---
README.md | 171 +++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 131 insertions(+), 40 deletions(-)
diff --git a/README.md b/README.md
index 0c815f1..7948d21 100644
--- a/README.md
+++ b/README.md
@@ -6,10 +6,20 @@
> fully automated package/module/image publishing
-A more lightweight and standalone version of [semantic-release](https://github.com/semantic-release/semantic-release).
+This project aims to be an alternative to the original [semantic-release](https://github.com/semantic-release/semantic-release) implementation. Using Go, `semantic-release` can be installed by downloading a single binary and is, therefore, easier to install and does not require Node.js and npm. Furthermore, `semantic-release` has a built-in plugin system that allows to extend and customize its functionality.
+
+### Features
+
+- Automated version and release management
+- No external dependencies required
+- Runs on Linux, macOS and Windows
+- Fully extensible via plugins
+- Automated changelog generation
+- Supports GitHub, GitLab and git
+- Support for maintaining multiple major version releases
## How does it work?
-Instead of writing [meaningless commit messages](http://whatthecommit.com/), we can take our time to think about the changes in the codebase and write them down. Following the [AngularJS Commit Message Conventions](https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit) it is then possible to generate a helpful changelog and to derive the next semantic version number from them.
+Instead of writing [meaningless commit messages](http://whatthecommit.com/), we can take our time to think about the changes in the codebase and write them down. Following the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification it is then possible to generate a helpful changelog and to derive the next semantic version number from them.
When `semantic-release` is setup it will do that after every successful continuous integration build of your default branch and publish the new version for you. This way no human is directly involved in the release process and your releases are guaranteed to be [unromantic and unsentimental](http://sentimentalversioning.org/).
@@ -17,30 +27,140 @@ _Source: [semantic-release/semantic-release#how-does-it-work](https://github.com
You can enforce semantic commit messages using [a git hook](https://github.com/hazcod/semantic-commit-hook).
-
## Installation
### Option 1: Use the go-semantic-release GitHub Action ([go-semantic-release/action](https://github.com/go-semantic-release/action))
-### Option 2: Install `semantic-release` manually
+### Option 2: Install manually
```bash
curl -SL https://get-release.xyz/semantic-release/linux/amd64 -o ./semantic-release && chmod +x ./semantic-release
```
+### Option 3: Install via npm
+
+```bash
+npm install -g go-semantic-release
+```
+
+## Examples
+
+### Releasing a Go application with GitHub Actions
+Full example can be found at [go-semantic-release/example-go-application](https://github.com/go-semantic-release/example-go-application).
+
+Example [.github/workflows/ci.yml](https://github.com/go-semantic-release/example-go-application/blob/main/.github/workflows/ci.yml) config:
+```yaml
+name: CI
+on:
+ push:
+ branches:
+ - '**'
+ pull_request:
+ branches:
+ - '**'
+jobs:
+ lint:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions/setup-go@v3
+ with:
+ go-version: 1.19
+ - uses: golangci/golangci-lint-action@v3
+ test:
+ runs-on: ubuntu-latest
+ needs: lint
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions/setup-go@v3
+ with:
+ go-version: 1.19
+ - run: go test -v ./...
+ release:
+ runs-on: ubuntu-latest
+ needs: test
+ permissions:
+ contents: write
+ steps:
+ - uses: actions/checkout@v3
+ - uses: actions/setup-go@v3
+ with:
+ go-version: 1.19
+ - uses: go-semantic-release/action@v1
+ with:
+ hooks: goreleaser
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
+### Example GitLab CI Config
+
+#### GitLab token
+It is necessary to create a new Gitlab personal access token with the `api` scope [here](https://gitlab.com/profile/personal_access_tokens).
+Ensure the CI variable is protected and masked as the `GITLAB_TOKEN` has a lot of rights. There is an open issue for project specific [tokens](https://gitlab.com/gitlab-org/gitlab/issues/756)
+You can set the GitLab token via the `GITLAB_TOKEN` environment variable or the `-token` flag.
+
+.gitlab-ci.yml
+```yml
+ stages:
+ # other stages
+ - release
+
+release:
+ image: registry.gitlab.com/go-semantic-release/semantic-release:latest
+ stage: release
+ # Remove this if you want a release created for each push to master
+ when: manual
+ only:
+ - master
+ script:
+ - release
+```
+
## Plugin System
Since v2, semantic-release is equipped with a plugin system. The plugins are standalone binaries that use [hashicorp/go-plugin](https://github.com/hashicorp/go-plugin) as a plugin library. `semantic-release` automatically downloads the necessary plugins if they don't exist locally. The plugins are stored in the `.semrel` directory of the current working directory in the following format: `.semrel/<os>_<arch>/<plugin name>/<version>/`. The go-semantic-release plugins registry (https://registry.go-semantic-release.xyz/) is used to resolve plugins and to download the correct binary. With the new [plugin-registry](https://github.com/go-semantic-release/plugin-registry) service the API also supports batch requests to resolve multiple plugins at once and caching of the plugins.
-### Plugin Types
+### Running semantic-release in an air-gapped environment
+As plugins are only downloaded if they do not exist in the `.semrel` folder, it is possible to download the plugins and archive the `.semrel` folder. This way it is possible to run `semantic-release` in an air-gapped environment.
-* Commit Analyzer ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/analyzer?tab=doc#CommitAnalyzer), [Example](https://github.com/go-semantic-release/commit-analyzer-cz))
-* CI Condition ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/condition?tab=doc#CICondition), [Example](https://github.com/go-semantic-release/condition-github))
-* Changelog Generator ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/generator?tab=doc#ChangelogGenerator), [Example](https://github.com/go-semantic-release/changelog-generator-default))
-* Provider ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/provider?tab=doc#Provider), [Example](https://github.com/go-semantic-release/provider-github))
-* Files Updater ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/updater?tab=doc#FilesUpdater), [Example](https://github.com/go-semantic-release/files-updater-npm))
-* Hooks ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/hooks?tab=doc#Hooks), [Example](https://github.com/go-semantic-release/hooks-goreleaser))
+```bash
+# specify all required plugins and download them
+./semantic-release --download-plugins --show-progress --provider github --ci-condition github --hooks goreleaser
+# archive the .semrel folder
+tar -czvf ./semrel-plugins.tgz .semrel/
+
+# copy the archive to the air-gapped environment
+
+# extract the archive
+tar -xzvf ./semrel-plugins.tgz
+# run semantic-release
+./semantic-release --provider github --condition github --hooks goreleaser
+```
+
+### Plugins
+
+* Provider ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/provider?tab=doc#Provider))
+ * [GitHub](https://github.com/go-semantic-release/provider-github)
+ * [GitLab](https://github.com/go-semantic-release/provider-gitlab)
+ * [Git](https://github.com/go-semantic-release/provider-git)
+* CI Condition ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/condition?tab=doc#CICondition))
+ * [GitHub Actions](https://github.com/go-semantic-release/condition-github)
+ * [GitLab CI](https://github.com/go-semantic-release/condition-gitlab)
+ * [Bitbucket Pipelines](https://github.com/go-semantic-release/condition-bitbucket)
+ * [Default](https://github.com/go-semantic-release/condition-default)
+* Commit Analyzer ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/analyzer?tab=doc#CommitAnalyzer))
+ * [Conventional Commits](https://github.com/go-semantic-release/commit-analyzer-cz)
+* Changelog Generator ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/generator?tab=doc#ChangelogGenerator))
+ * [Default](https://github.com/go-semantic-release/changelog-generator-default)
+* Hooks ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/hooks?tab=doc#Hooks))
+ * [GoReleaser](https://github.com/go-semantic-release/hooks-goreleaser)
+ * [npm-binary-releaser](https://github.com/go-semantic-release/hooks-npm-binary-releaser)
+ * [plugin-registry-update](https://github.com/go-semantic-release/hooks-plugin-registry-update)
+* Files Updater ([Docs](https://pkg.go.dev/github.com/go-semantic-release/semantic-release/v2/pkg/updater?tab=doc#FilesUpdater))
+ * [npm](https://github.com/go-semantic-release/files-updater-npm)
+ * [helm](https://github.com/go-semantic-release/files-updater-helm)
### Configuration
@@ -74,35 +194,6 @@ Plugins can be configured using CLI flags or the `.semrelrc` config file. By usi
}
```
-## Example GitHub Actions
-
-For examples, look at the [go-semantic-release GitHub Action](https://github.com/go-semantic-release/action).
-
-## Example GitLab CI Config
-
-### GitLab token
-It is necessary to create a new Gitlab personal access token with the `api` scope [here](https://gitlab.com/profile/personal_access_tokens).
-Ensure the CI variable is protected and masked as the `GITLAB_TOKEN` has a lot of rights. There is an open issue for project specific [tokens](https://gitlab.com/gitlab-org/gitlab/issues/756)
-You can set the GitLab token via the `GITLAB_TOKEN` environment variable or the `-token` flag.
-
-.gitlab-ci.yml
-```yml
- stages:
- # other stages
- - release
-
-release:
- image: registry.gitlab.com/go-semantic-release/semantic-release:latest # Replace this with the current release
- stage: release
- # Remove this if you want a release created for each push to master
- when: manual
- only:
- - master
- script:
- - release
-```
-
-
## Beta release support
Beta release support empowers you to release beta, rc, etc. versions with `semantic-release` (e.g. v2.0.0-beta.1). To enable this feature you need to create a new branch (e.g. beta/v2) and check in a `.semrelrc` file with the following content:
```
--
GitLab