-
## :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…
-
Install https://www.npmjs.com/package/semantic-release
-
```
app
lib_core
lib_utils
```
auto resolve dependent version, and `semantic-release`
like this libraray https://github.com/changesets/changesets
-
**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…
-
After updating from `13.1.0` to `13.2.0` releases are now failing with `422 (Unprocessable Entity)`:
```
[7:41:59 AM] [semantic-release] › ✔ Created tag v1.1.1
[7:41:59 AM] [semantic-release] › …
-
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…
-
Kpoke updated
8 months ago
-
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…
-
[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) and [Semantic Release](https://github.com/semantic-release/semantic-release) provide a way to objectively assign versions and aut…
reece updated
3 months ago
-
I'm getting this error on the final step of my action, weirdly enough it releases and tags correctly but the error appears nonetheless.
here's the relevant part from my .releaserc
```json
[
…