Skip to content
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

Doesn't work with semantic-release@next? #43

Closed
FezVrasta opened this issue Apr 19, 2018 · 1 comment
Closed

Doesn't work with semantic-release@next? #43

FezVrasta opened this issue Apr 19, 2018 · 1 comment
Labels

Comments

@FezVrasta
Copy link

FezVrasta commented Apr 19, 2018

I installed @semantic-release/git@next and semantic-release@next but I get:

[Semantic release]: EPLUGIN A plugin configured in the step publish is not a valid semantic-release plugin.
A valid publish semantic-release plugin must be a function or an object with a function in the property publish.

The plugin @semantic-release/git doesn't have the property publish and cannot be used for the publish step.

Please refer to the @semantic-release/git and semantic-release plugins configuration (https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/plugins.md) documentation for more details.

I'm also using semantic-release-monorepo (related issue pmowrer/semantic-release-monorepo#32)

What's wrong?

@pvdlg
Copy link
Member

pvdlg commented Apr 19, 2018

semantic-release-monorepo is not our project and we can't help with it.
At that point monorepo are not supported by semantic-release. See semantic-release/semantic-release#193 (comment). As explained over there semantic-release-monorepo doesn't support all monorepo scenario (namely commits triggering a release on one of the repo that is out of range for another repo) and therefore is not a solution we intend to support.

Regarding the issue you reported, @semantic-release/git@next and @semantic-release/git@latest are the same version. Same for semantic-release@next and semantic-release@latest. So installing the @next version doesn't change anything.

As mentioned in the error message, you are using the @semantic-release/git for the publish step but it doesn't have one. Please refer to the documentation of the plugin. It mentions it has to be used in the prepare step.

@pvdlg pvdlg closed this as completed Apr 19, 2018
@pvdlg pvdlg added the support label Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants