-
We want to create new ZITADEL releases manually via the GitHub UI.
This removes complexity, makes us faster in releasing and independent from the semantic-release features.
With manual releases vi…
-
## Issue type
* [ ] bug report
* [ ] idea
* [x] question
* [ ] other
## Background
The https://github.com/IBM/openapi-validator project uses semrel-toolkit's multi-semrel command to manage rel…
-
## Description
Enhance the display of commit messages by rendering SemVer tags as colored badges, improving clarity and readability.
## Visual Example
Current commit view:
![Current View](…
-
hi, I tried to use it and it worked out of the box, however I have few questions:
* how t configure it ? I.e. to use given version of goreleaser ? Does it use the version on the path ?
* what respo…
-
## Issue type
* [x] bug report
* [ ] idea
* [ ] question
* [ ] other
## Expected behavior
Not sure if this is a bug or feature request, but the plugin currently doesn't work with a GitHub App …
-
Suppose that some fork of a repo would like to separately version a project. Upstream commits and tags are synced periodically. Suppose the upstream maintainers are using "v-prefixed" semver tags (whi…
-
Git tag is correctly created, but npm publishing is failed due to the wrong version.
msr: v3.0.0
-
the official semantic-release now supporting esm, but it seems that this package doesn't work with esm projects.
I got this error
```
[12:14:08 AM] › 🎉 Started multirelease! Loading 26 packages.…
-
So that it's automated. Should include package.json, package-lock.json, docs, and html files AFAICT
-
I've been browsing the different repository to try finding documentation on how to configure or do some task. And I didn't find much documentation.
For instance I was hoping to upload the generated…