@omnitoolkit/releasebot 7.3.1 → 7.4.0

package/README.md

@@ -2,7 +2,7 @@
 
 This program analyzes a git repository and, if necessary, performs a release according to the specifications of  [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) and [semantic versioning](https://semver.org/spec/v2.0.0.html).
 
-It uses [semantic-release](https://github.com/semantic-release/semantic-release) (see [documentation](https://semantic-release.gitbook.io/semantic-release)) inside a Docker image with a custom-made module (see [index.js](src/index.js)). There, several plugins along with their configuration are defined and loaded on execution:
+It uses [semantic-release](https://github.com/semantic-release/semantic-release) (see [documentation](https://semantic-release.gitbook.io/semantic-release)) as an npm CLI package with a custom-made module (see [index.js](src/index.js)). There, several plugins along with their configuration are defined and loaded on execution:
 
 - [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer) reads each git commit added since the last release, determines if a new release is due, the type of release and the new version number. It analyzes the syntax according to the conventionalcommits preset in [parser.js](https://github.com/conventional-changelog/conventional-changelog/blob/conventional-changelog-conventionalcommits-v9.0.0/packages/conventional-changelog-conventionalcommits/src/parser.js) and checks for custom rules combined from the [default rules list](https://github.com/semantic-release/commit-analyzer/blob/v13.0.1/lib/default-release-rules.js) and the [@commitlint/config-conventional type list](https://github.com/conventional-changelog/commitlint/blob/v19.8.1/%40commitlint/config-conventional/README.md#type-enum). A commit should look like this:
   ```
@@ -43,15 +43,15 @@ It uses [semantic-release](https://github.com/semantic-release/semantic-release)
     - deploy
     - release
   ```
-- Then add the following job and replace `main` with the desired version from the [releases](https://gitlab.com/omnitoolkit/omnitoolkit/-/releases) page:
+- Then add the following job and replace the package version with the desired version from the [releases](https://gitlab.com/omnitoolkit/omnitoolkit/-/releases) page:
   ```yaml
   release_version:
-    image: registry.gitlab.com/omnitoolkit/omnitoolkit/releasebot:main
+    image: docker.io/library/node:24.15.0
     stage: release
     rules:
       - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
     script:
-      - releasebot --branches ${CI_DEFAULT_BRANCH}
+      - npx --yes @omnitoolkit/releasebot@7.4.0 --branches ${CI_DEFAULT_BRANCH}
   ```
 - If `CI_DEFAULT_BRANCH` is not your release branch, replace it with the correct one.
 - If you don't want to release on every push to the release branch, add `when: manual` to the job. You can now start the job on demand from the UI.

package/package.json

@@ -33,5 +33,5 @@
   "scripts": {
     "test": "node --test"
   },
-  "version": "7.3.1"
+  "version": "7.4.0"
 }