-
Notifications
You must be signed in to change notification settings - Fork 80
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
Commit analyzation doesn't pick up any commits to release #131
Comments
Hi, I encoutered the same issue but found out that when using a custom config for semantic-release you should:
Here is a sample of a minimal custom configuration: // release.config.js
module.exports = {
repositoryUrl: '<your_repository_url>',
extends: 'semantic-release-monorepo',
branches: ['master'], // if you want to release on master
plugins: [
// "semantic-release-monorepo" is perfoming the analysis of commits (for the subrepo)
// then update the context passed to `analyzeCommits` and `generateNotes` steps of semantic-release
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator", // not necessary to create a new release but useful for release's notes
],
}; It would be nice to indicate this in the doc of current repository. |
I just ran into the same issue. What was not obvious is that I had to explicitly have As a side note, |
Did you try |
Hi,
I'm using
[email protected]
(tried with version 17 and 16 as well) and[email protected]
with Yarn workspaces.Here is my set up:
Semantic release is configured for each package inside the monorepo. Given the following folder structure
<repo root>/packages/<package-a>
<repo root>/packages/<package-b>
I'm running semantic release inside
<package-a>
and<package-b>
The semantic release command finds the new commits, and even though I have commits with the correct message format and changes in the correct folders (
<package-a>
and<package-b>
), the process doesn't find any relevant changes. Here are the logs from the "commit analyze" step (debug
mode is turned on):Do you see something wrong with this setup?
The text was updated successfully, but these errors were encountered: