Comments (17)
i believe its the git plugin that is causing the issue. The latest version (10.0.0) has a dependency on [email protected] so it you havent fixed the plugin version then it could be throwing an error with this by trying to grab the latest version, yet all other plugins havent been updated to support (they were reporting support <= 18.0.0). I set the @semantic-release/[email protected] to resolve things and work around the conflict here.
from semantic-release-action.
@pegiadise I donβt think itβs the reason.
This worked for me:
- name: π Release
uses: cycjimmy/semantic-release-action@v2
id: semantic
with:
semantic_version: 18
extra_plugins: |
@semantic-release/changelog@6
@semantic-release/git@10
[email protected]
from semantic-release-action.
looks like you need to add
with:
semantic_version: 17
to your action
from semantic-release-action.
Got the same error
Fixed by specifying a setup-node
step and it works now
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: '14'
- name: Semantic Release
uses: cycjimmy/[email protected]
with:
semantic_version: 18.0.0
extra_plugins: |
@semantic-release/[email protected]
@semantic-release/[email protected]
@semantic-release/[email protected]
@semantic-release/[email protected]
@semantic-release/[email protected]
from semantic-release-action.
Yeah that's how I found it. I'm not sure why --silent
is added by default but this should definitely be documented.
from semantic-release-action.
same here, any pointers ?
from semantic-release-action.
Thanks
from semantic-release-action.
@revolunet it's not fix the problem for me :(
with:
branch: staging
extra_plugins: @semantic-release/changelog
@semantic-release/git
@semantic-release/exec
semantic_version: 17
env:
GITHUB_TOKEN: ***
GH_TOKEN: ***
GITHUB_TOKEN_NPM: ***
added 2 packages, and audited 3 packages in 966ms
found 0 vulnerabilities
Error: Error: Command failed: npm install @semantic-release/changelog @semantic-release/git @semantic-release/exec --silent
from semantic-release-action.
@pennywisdom I believe your fix resolves the issue I was having in #80 but for me it didn't resolve this particular issue.
what is a workaround for me was to not use npm@7
, and to downgrade to npm@6
I normally have my github actions config set up like this:
...
- uses: actions/setup-node@v2
with:
node-version: 14
- run: npm install -g npm@7
- uses: cycjimmy/[email protected]
...
the workaround for me was:
...
- uses: actions/setup-node@v2
with:
node-version: 14
# - run: npm install -g npm@7
- uses: cycjimmy/[email protected]
...
which is just a workaround, not a fix...
from semantic-release-action.
Is it actually some Node 16 breaking change that needs to be obliged?
from semantic-release-action.
@pegiadise I donβt think itβs the reason.
This worked for me:
- name: π Release uses: cycjimmy/semantic-release-action@v2 id: semantic with: semantic_version: 18 extra_plugins: | @semantic-release/changelog@6 @semantic-release/git@10 [email protected]
Yup. I also ended up using semantic 18. It seems that the issue is with semantic 17 and Node 16.
from semantic-release-action.
For me this error was happening due to packages
permission missing from the job
from semantic-release-action.
I faced the same issue today. For me, the problem is isolated to one repository. The main difference between my other repos where this action is used is that actions/setup-java
is used since I intent to use gradle-semantic-release-plugin
. I attached my release workflow at the end of this comment. I went through this entire thread and all proposed solutions did not work, I even explicitly set the versions for all packages. Is there anything I am missing?
Another thing to note: When running the seemingly failed command in my local shell, everything works fine and no error is thrown. So I assume it is not a mismatch of some dependencies here.
on:
push:
branches:
- main
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: "lts/*"
- uses: actions/setup-java@v3
with:
java-version: "17"
distribution: "adopt"
- uses: bufbuild/buf-setup-action@v1
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
- uses: arduino/setup-protoc@v1
with:
version: "3.x"
repo-token: ${{ secrets.GITHUB_TOKEN }}
- uses: cycjimmy/semantic-release-action@v3
env:
GITHUB_TOKEN: ${{ github.token }}
GITHUB_ACTOR: ${{ github.actor }}
OSSRH_ACTOR: ${{ secrets.OSSRH_ACTOR }}
OSSRH_TOKEN: ${{ secrets.OSSRH_TOKEN }}
SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
SIGNING_PASSWORD: ${{ secrets.SIGNING_PASSWORD }}
with:
semantic_version: 19
extra_plugins: |
@semantic-release/git@10
@semantic-release/changelog@6
@semantic-release/exec@6
conventional-changelog-conventionalcommits@5
gradle-semantic-release-plugin@1
from semantic-release-action.
There should be a way to disable the "--silent" flag, for example when re-running a failed job with the "debug" mode enabled.
This would allow to get more information about the error. This happened to me today. Had to create a fork and disable the "--silent" flag to understand the issue.
from semantic-release-action.
It's possible to disable the --silent
flag by passing:
env:
RUNNER_DEBUG: 1
from semantic-release-action.
You're right, see : 6d1b158
from semantic-release-action.
Definitely. Also, it should be documented that the RUNNER_DEBUG
environment variable is automatically set by GitHub when re-running a failed job and checking the "Enable debug logs" box.
from semantic-release-action.
Related Issues (20)
- `extends` parameter should allow file paths as well HOT 1
- Allow tag format parameter HOT 3
- Does not support semantic-release version 20 HOT 3
- Release action fails with non-specific error HOT 2
- Error: Error: Command failed: npm install HOT 10
- Is now mandatory NPM_TOKEN to run semantic-release? If yes is possible to run it without publish on NPMJS website?
- Add action typing
- Get version from dry-run mode. HOT 1
- BUG: DRY_RUN still creates release... HOT 1
- Incompatibility with semantic-release >v20 HOT 13
- ESM Error on Semantic Release Version 19.0.5 HOT 2
- `CI = false` & `dryrun = true` does not result in prelease build HOT 2
- override plugin version HOT 2
- Incompatibility with v22 of semantic-release HOT 4
- workflow_run causes semantic-release-action to reference wrong branch HOT 1
- `perf` prefix triggered a patch release. HOT 2
- [semantic-release] βΊ β EGITNOPERMISSION Cannot push to the Git repository
- Add repository_url input
- An error occurred while running semantic-release: Error: Cannot find module 'xxxxx' with 4.1.0 HOT 3
- ESM fail HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from semantic-release-action.