-
-
**Describe the bug**
The issue I'm getting is that, with the 4.1.0 version I'm getting the above error where it cannot find the modules for conventional-changelog-conventionalcommits, I'm current…
-
We are running into the gitlab API limit on some projects when multiple semantic-releases are running at the same time from share IPs.
```
[8:07:42 AM] [semantic-release] › ℹ Start step "success"…
-
- bump script should update `stapi_fastapi.constants:STAPI_VERSION`. also should either do semantic versioning - but need to decide how to manage that, i.e. conventional commits? - or switch to dateti…
-
I noticed a strange behaviour/bug with the `git` provider when running semantic-release for a git repository that looks the following:
```
* b76a513 - Merge branch 'feature' (HEAD -> main)
|\
…
-
I think it would be good if we automated the release process to reduce the risk and overhead around doing releases - especially since we don't do that man releases which makes it easy to forgot the pr…
-
## Current Behavior
We have a setup of two branches: **main** and **development**. The development branch is used to push latest changes and triggers version updates like so:
```
npx lerna versio…
-
-
I get this error when executing the plugin in a Gitlab CI pipeline. It only happens the first time, because in the second execution it works fine.
I have a GL_TOKEN with the right permissions over …
-
Try out using `cargo-release` or another crate for generating builds.
Cargo.toml's `version` field will be the authoritative ID for development. Change notes will be generated by parsing Git commit…