Customize generateNotes configuration #83
Labels
Comments
|
FYI, After going through some closed issues I also tried the following without any luck: |
|
Thanks for the report, @elizabethsjudd! Does it work if you move the E.g.: module.exports = {
plugins: [
'@semantic-release/commit-analyzer',
['@semantic-release/release-notes-generator', {
preset: 'angular',
writerOpts: {
transform: (commit, context) => {...},
}
}],
'@semantic-release/npm',
'@semantic-release/github'
],
branches: ['master'],
githubUrl: 'https://github.ibm.com',
githubApiPathPrefix: 'api/v3',
releaseRules: [ ... ],
releaseNotes: {
issueResolution: {
template: '{baseUrl}/{owner}/{repo}/issues/{ref}',
baseUrl: 'https://github.ibm.com',
source: 'github.ibm.com',
},
},
} |
|
@pmowrer That doesn't even create the custom release notes at all. Is this something I should be bring up with |
|
It depends on what version of |
|
@pmowrer these are the versions I'm using. So it looks like I shouldn't be using the I guess my confusion is... is this a bug for:
|
|
It's most likely a bug with this library... I'll dig into it! |
Merged
|
I believe this has been fixed in the latest version ( |
|
🎉 This issue has been resolved in version 7.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@pmowrer, I updated our version of monorepo to 7.0.2 and am still having the same issue where defining a custom Example I'm also now running in to the issue of it not recognizing our custom Here's our release rules: but when I have a merge with only a |
|
@elizabethsjudd Thanks for trying this out and sorry it still isn't working! A few questions as I try to diagnose this further:
|
|
Release config: We do not have any custom plugin setup. Here's the config that's printed out from the The config is in a Using a JavaScript file allows us to break up the config in to multiple objects and share them across the multiple packages in the monorepo. Here's the output of the debug from the packages that had changes in this particular push and Let me know if you need anything else and thank you for looking in to this. |
|
That release config is using the old format See the current top-level config options here: https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration (I'd recommend running the latest version of this plugin with the latest version of Here's roughly what I think your config should look like. Please reference the individual plugin READMEs via https://github.com/semantic-release/commit-analyzer module.exports = {
branches: ...,
plugins: [
['@semantic-release/commit-analyzer', {
"releaseRules": [
{ breaking: true, release: 'major' },
{ revert: true, release: 'patch' },
{ type: 'feat', release: 'minor' },
...
]
}],
['@semantic-release/release-notes-generator', {
preset: 'angular',
writerOpts: {
transform: (commit, context) => {...},
}
}],
'@semantic-release/npm',
['@semantic-release/github', {
githubUrl: 'https://github.ibm.com',
githubApiPathPrefix: 'api/v3',
}]
],
} |
|
That did the trick @pmowrer. Thank you so much for your help! |
panzarino
pushed a commit
to cypress-io/cypress
that referenced
this issue
Sep 23, 2020
|
I have a similar issue with npm options described here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are using
semantic-releaseandsemantic-release-monorepoin our project and want to modify the defaultconventional-changelog-angularwriterOptsconfiguration (specifically thetransformfunction).Following the guidelines for semantic release, I added the function at the root of the config object and my changes were applied to the changelog notes in GH.
However, with this approach we lost the commit package scoping that is provided by
semantic-release-monorepo.In a different project we use
semantic-release-gitmojias our changelog convention and were able to set it up to work withsemantic-release-monorepoby doing the following:I tried to do something similar in my current project:
but did not have any luck as it reverted back to using the default
transformfunctionDebug with
generateNotesinmonorepo:Debug with
generateNotesat root:The text was updated successfully, but these errors were encountered: