Include all commonly used plugins #3313
-
|
By default, semantic release ships with 4 plugins:
Is there any reason other commonly used ones are not included in this list? I find myself adding the following plugins every time I use semantic release:
Looking at package popularity, these appear to have high usage. Initially I found it confusing to understand why some plugins had to be installed manually and others didn't, and what that meant in terms of configuring them and how they're supported. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
the default configuration is our recommended config for publishing to the npm registry from a repo hosted on github, our most common use case. in that scenario, we actively discourage using the git or changelog plugins.
is there any reason you are choosing to include those plugins every time you use semantic-release, despite the default configuration and our recommendation against their use?
our docs can always use improvement. if you have suggestions to make these recommendations more clear, or if you found recommendations elsewhere that contradict our recommendations that we could attempt to influence, we welcome such feedback. |
Beta Was this translation helpful? Give feedback.
-
|
My company use Azure DevOps instead of Github, so the As for the |
Beta Was this translation helpful? Give feedback.
-
|
anyone can choose to use either plugin despite our recommendations. there absolutely are valid reasons to use them. that is why they exist. however, they are not our recommendation when they are not needed. they are simply dependencies, like any other. if you choose to include them, part of that choice is the complexity of getting them downloaded for use. because of that, we purposely do not include them as default dependencies. we will not include default dependencies that are not used in the default config for many reasons, one of which is the weight of unnecessary downloads. if anything, we need to take steps to include fewer plugins by default rather than more. as you mention, you don't use github, so it would be better for you if we did not include that plugin by default. |
Beta Was this translation helpful? Give feedback.
anyone can choose to use either plugin despite our recommendations. there absolutely are valid reasons to use them. that is why they exist. however, they are not our recommendation when they are not needed. they are simply dependencies, like any other. if you choose to include them, part of that choice is the complexity of getting them downloaded for use.
because of that, we purposely do not include them as default dependencies. we will not include default dependencies that are not used in the default config for many reasons, one of which is the weight of unnecessary downloads. if anything, we need to take steps to include fewer plugins by default rather than more. as you mention, you don…