We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
And all standard configs for semantic release for that matter!
It seems to me that this action doesn't support (in my case) .releaserc.json at root of project which is pretty standard for example.
releaserc.json
Even if I add it as a custom config file the action fails with an error of {}
{}
Sure I can go and convert to a yaml and so on - but should all standard configs be supported? :)
From their docs:
A .releaserc file, written in YAML or JSON, with optional extensions: .yaml/.yml/.json/.js
Our .releaserc.json looks like:
.releaserc.json
{ "plugins": [ "@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/changelog", "@semantic-release/npm", "@semantic-release/github", ["@semantic-release/git", { "message": "chore(release): ${nextRelease.version}\n\n${nextRelease.notes}" }] ], "branches": [ "master" ] }
If I omit the custom config file I seem to get a standard config skipping release-notes-generator and performed in a different order
The text was updated successfully, but these errors were encountered:
No branches or pull requests
And all standard configs for semantic release for that matter!
It seems to me that this action doesn't support (in my case) .
releaserc.json
at root of project which is pretty standard for example.Even if I add it as a custom config file the action fails with an error of
{}
Sure I can go and convert to a yaml and so on - but should all standard configs be supported? :)
From their docs:
Our
.releaserc.json
looks like:If I omit the custom config file I seem to get a standard config skipping release-notes-generator and performed in a different order
The text was updated successfully, but these errors were encountered: