Execute Semantic Release without a package.json file #115
Comments
|
+1 |
|
+1 |
|
having the same issue, seem this happens regardless the repo is a node project. Was having the same thought if we are missing some config in the workflow? |
|
Also running into this, has anyone sorted it out? |
I've simply added a {
"branches": [
"+([0-9])?(.{+([0-9]),x}).x",
"main",
{
"name": "beta",
"prerelease": true
}
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/github"
]
}I then invoke the action as usual in a github workflow: - name: Execute Semantic Release
id: semantic
uses: cycjimmy/semantic-release-action@v2
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
@maxiride thanks a ton for sharing, that helped get it working for a dotnet project I was trying to get configured 🎉 |
|
Similar issue for me : the How can I add this dependance without a |
|
Using the .releaserc file is a good temporary for some cases, but evidently it doesn't solve all cases, and I just found that for some reason you must provide a value for "plugins", and worse still that semantic-release's behaviour is that providing a "plugins" value will override the defaults. So I agree with the original poster that, given the wide array of inputs this action accepts, providing a superfluous package.json or .releaserc shouldn't be necessary - I'd love to see it dropped as an implicit requirement! But in case it helps anyone, this is the pre-step I'm doing in GitHub Actions (branches are configured in the action itself) |
It is my understanding that the action can feed the underlying semantic release with options by using the
withfieldsbranches,extra_pluginsetc. Hence, executing semantic release without a package.json and without a.releasercfile for non-javascript projects.Describe the bug
The action extis with the following error:
Workflow
CI Log
Expected behavior
I expect the semantic release to run.
Additional context
The action docs states
branches will override the branches attribute in your configuration file., so I've also tried to execute the action with an empty .releaserc file guessing it would have been populated by the action. Same error result.Am I misunderstanding the action use or is there an error in my configuration? Even though I did not specify the
@semantic-release/npmit's like the action pulled and executed it anyway.The text was updated successfully, but these errors were encountered: