-
Hello! We have been using the semantic-release/git + the [changelog](https://github.com/semantic-release/changelog) plugin for a few weeks to automatically generate the `CHANGELOG.md` and we saw this …
Qing8 updated
4 weeks ago
-
**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…
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…
-
Both the git plugin and github plugin have a configuration option named `assets`. When building out a shareable configuration, It is preferable to omit configuration inline with the plugin and define …
-
## Current behavior
Whenever I try to run a release, with my config using the following config:
```json
"release": {
"branches": [
"release/'*'"
],
....
```
This cause…
-
Creating GitHub release is failing when semantic-release is executed on an Openshift behind a corporate proxy.
When working on an Openshift clusters without a proxy the same configuration works fine…
-
Hello
I am trying to implement pre-releases on my _beta/v1_ branch. I was following the README.md, but when I attempted to push to this branch, my pipeline failed with the error message "no pre-r…
-
I recently converted a monorepo from yarn to pnpm, and now publishing won't happen.
```
4:36:23 PM] [semantic-release] [@semantic-release/npm] › ℹ Verify authentication for registry https://regis…
-
### Current behavior
- Committed changes to feature branch that is by mistake behind main branch.
- Commit analyser says that the branch is behind so no new version is released
- Merged from main t…
-
### New feature motivation
Currently, plugins cannot modify the `nextRelease` object due to the deep cloning of `context`.
This prevents customization scenarios like custom version suffixes (https…