-
Notifications
You must be signed in to change notification settings - Fork 44
Open
Description
Hi :)
My config looks like this:
// .release-it.cjs
const version = '${version}'
const packageName = process.env.npm_package_name
let scope = ''
if (packageName) {
scope = packageName.split('/')[1]
}
module.exports = {
plugins: {
'@release-it/conventional-changelog': {
path: '.',
infile: 'CHANGELOG.md',
header: '#📋 CHANGELOG',
preset: {
name: 'conventionalcommits',
types: [
{ type: 'feat', section: '✨ Features' },
{ type: 'fix', section: '🐛 Bug Fixes' },
{ type: 'perf', section: '⚡ Performance Improvements' },
{ type: 'revert', section: '⏪ Reverts' },
{ type: 'chore', section: '📦 Chores' },
{ type: 'docs', section: '📝 Documentation' },
{ type: 'style', section: '💄 Styles', hidden: true },
{ type: 'refactor', section: '♻ Code Refactoring' },
{ type: 'test', section: '✅ Tests' },
{ type: 'build', section: '👷 Build System' },
{ type: 'ci', section: '🔧 Continuous Integration' },
],
},
gitRawCommitsOpts: {
path: '.',
},
},
},
git: {
push: true,
tagName: `${packageName}-v${version}`,
pushRepo:
'ssh://git@...repo.git',
commitsPath: '.',
commitMessage: `feat(${scope}): released version v${version} [no ci]`,
requireCommits: true,
requireCommitsFail: false,
},
npm: {
publish: false,
versionArgs: ['--workspaces false'],
},
}
When i run release-it always suggests an "major" release instead o a minor or patch based on the commits and i don't know why.
Here a simple output of the release-it script:
command: yarn release
yarn run v1.22.22
$ release-it
🚀 Let's release @mycomp/mypackage (13.5.2...14.0.0)
Changelog:
## 14.0.0 (2025-07-28)
* feat(DropzoneUploader): optimize Mobile UI ([e0d0b65](url))
Changeset:
M CHANGELOG.md
M package.json
I would expect here a "minor" bump from 13.5.2 to 13.6.0 and not 14.0.0
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels