New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make patch release a default for each commit #143
Comments
I just tested your config and it works as expected, all commits triggers a Can you run semantic-release with the --debug option and provide the logs? |
Thank you for your prompt reply. Here is my current config: # In .releaserc.js
module.exports = {
plugins: [
[
'@semantic-release/commit-analyzer',
{
preset: 'angular',
releaseRules: [
{scope: 'skip release', release: false},
{type: '*', release: 'patch'},
],
},
],
'@semantic-release/release-notes-generator',
[
'@semantic-release/exec',
{
prepareCmd: [
'./api/app/scripts/release-images.sh ${nextRelease.version}',
'./web/scripts/release-images.sh ${nextRelease.version}',
].join(' && '),
},
],
],
} And this is what's written to the CI log. Please note "ci" type commit doesn't trigger patch version bump:
|
What version of semantic-release and of the @semantic-release/commit-analyzer are you running? It's quite weird that the first line of log is |
I am running a fresh fork https://github.com/beocommedia/semantic-release. I created it a couple of hours ago for another issue. The |
In version So in |
Nice! Thank you for clarification on regex. Works perfectly now! |
Hi,
Thank you for such an excellent plugin. We have a dedicated
prod
branch where each commit should trigger a release. Currently, certain commit types (e.g. chore) do not trigger a release. Is it possible to configure commit analyzer to bump patch version by default for any type except "no-release"? I've tried something like this, but it's not working:Another option, is to list each type with
release: "patch"
, but it's not as flexible as having a wildcard. Thank you very much!The text was updated successfully, but these errors were encountered: