You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to define configurations in a .releaserc or package.json file in the module path that would override the config defined at the root level for that specific package?
This way, we could define different rules per package. We mostly want to configure different presetConfig and releaseRules for the commit-analyzer and release-notes-generator plugin. This could also allow to specific plugin to be added to some packages independently.
The question seems related to #95, but I think it lacks context and it should be documented as a feature of semantic-release-monorepo if it is possible to do in a non hack-ish way!
Looking at the code, that would require this module to check if there are config in the current packagePath, load them, and merge them with the pluginConfig received in the different method wrapped such as
Is there a way to define configurations in a
.releaserc
orpackage.json
file in the module path that would override the config defined at the root level for that specific package?This way, we could define different rules per package. We mostly want to configure different
presetConfig
andreleaseRules
for the commit-analyzer and release-notes-generator plugin. This could also allow to specific plugin to be added to some packages independently.The question seems related to #95, but I think it lacks context and it should be documented as a feature of semantic-release-monorepo if it is possible to do in a non hack-ish way!
Looking at the code, that would require this module to check if there are config in the current packagePath, load them, and merge them with the pluginConfig received in the different method wrapped such as
semantic-release-monorepo/src/only-package-commits.js
Line 80 in 089e88a
The text was updated successfully, but these errors were encountered: