Closed mykola-mokhnach closed 4 months ago
If this was working before and then randomly stopped, then my guess is the environment changed in some way. Maybe the node/npm versions are different?
If this was working before and then randomly stopped, then my guess is the environment changed in some way. Maybe the node/npm versions are different?
Thank you for your response @milesj
Yes, this is also weird to me. We use exactly the same job config for all projects, so the only thing that might change over time is the actual image (ubuntu-latest
). Nothing else has changed. Shall I try to run the pipeline with an older image (e.g. ubuntu-20.04
)?
Or maybe you could suggest the particular node/npm version to set to make the action work properly?
I'm not entirely sure. I did notice that this action is still configured for node16 which was deprecated by Github, so I think my assumption is correct, since they are forced to node20 now.
I'll have to experiment a bit.
This repo is quite old so I'm updating it here: https://github.com/beemojs/conventional-pr-action/pull/39
@mykola-mokhnach Can you try v3, beemojs/conventional-pr-action@v3
?
@mykola-mokhnach Can you try v3,
beemojs/conventional-pr-action@v3
?
Thanks @milesj . I can confirm the issue is fixed in v3: https://github.com/appium/appium-mac2-driver/actions/runs/9013212335/job/24763664339?pr=301
Awesome, will close this.
Hello We use the following config for the action:
Previously it was working without issue, but now the execution always fails with the following error:
See https://github.com/appium/java-client/actions/runs/8965038536/job/24617789030?pr=2167 for more details.
Is this a genuine issue or there's something we have done wrong in the pipeline config?