-
### Current behavior
`semantic-release --branches '{"name":"main"},{"name":"version-test","prerelease":"snap"}' --dry-run --debug`
Splits `{"name":"version-test","prerelease":"snap"}` into two i…
-
Something like [this](https://medium.com/agoda-engineering/automating-versioning-and-releases-using-semantic-release-6ed355ede742) is cool because we can push create semantic tags based on the convent…
-
### Current behavior
We have released version 4.118.0, 4.118.1 4.118.2 4.118.3 .. and went to 4.124.1
and then we discovered that we have a bug in production, so we want to do a hotfix, using the …
-
- https://www.conventionalcommits.org/en/v1.0.0/#summary
- https://github.com/semantic-release/semantic-release
-
reece updated
5 months ago
-
### Start Date
_No response_
### Implementation PR
_No response_
### Reference Issues
_No response_
### Summary
Adding semantic versioning helps determine a version and release that version ove…
-
## Feature Request
### Description
Angular Commit Parser doesn't work with BitBucket multi-line PR commit messages.
BitBucket by default generates commit messages when a pull request merged t…
-
## Describe the bug
Python semantic release introduced recursive parsing of commits for change logs.
At the moment the default behaviour of the team is to use squash merges into develop and pul…
-
I have the following workflow config:
```yaml
name: Semantic Release
on:
push:
branches: [main]
jobs:
release:
name: Release version
permissions:
…
-
## The problem
The `setup_hook` function ins't working properly
## Expected behavior
Call `semantic_release` commands via setup.py
## Additional context
Documentation says that by addin…
-
### Steps to Reproduce
1. Create a breaking commit using exclamation mark, like `feat!: awesome feature`.
2. Try to push
---
```json
// package.json
"devDependencies": {
"@commitlint/…