-
I noticed that we have pinned semantic-release to `19` in this repo:
https://github.com/eslint-community/eslint-utils/blob/ede67fea586f4369c47874a9f4cd660028136482/.github/workflows/ci.yml#L117
…
-
## Issue
The currently configured [semantic-release@23.0.8](https://github.com/semantic-release/semantic-release/releases/tag/v23.0.8) displays a deprecation warning when installed:
> npm warn d…
-
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…
-
https://github.com/semantic-release/github/blob/990bd7335df10153c9b87bf2be57db602b08def0/package.json#L33
-
Currently, the semantic-release version is 20.0.1
Is there an issue with upgrading this package to the latest one - 23.0.8?
guymi updated
2 weeks ago
-
It would be beneficial if the project made "dot" releases or tags as bugs are fixed. This helps those of us who are deploying and upgrading specific major versions in automated or containerized enviro…
-
### Current behavior
`semantic-release --branches '{"name":"main"},{"name":"version-test","prerelease":"snap"}' --dry-run --debug`
Splits `{"name":"version-test","prerelease":"snap"}` into two i…
-
## what
The module could follow a semantic versioning scheme major.minor.patch
Using semantic commits, such as
- `feat!` for breaking backwards compatibility would cause a major version bump
…
-
## Question
I need some help troubleshooting an issue I'm having. Versioning is working great up until the point where psr tries to create the version tag.
- The merge request runs the pipeline s…
-
### Current behavior
I am using semantic-release with a custom tag format for the develop branch, and normal on the main branch... however this format breaks the continuity of the release...
usi…