Closed bamdadfr closed 4 years ago
fixed by installing prior version semantic-release-firefox-add-on@0.2.6
Hmm, seems like this was introduced by a hidden major version bump of sign-addon
when bumping web-ext to v5 https://github.com/tophat/semantic-release-firefox-add-on/compare/v0.2.6...v0.2.7 that was not caught by tests...
:tada: This issue has been resolved in version 0.2.8 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
nice catch :+1:
#
Context
Hello guys, it's probably not the best place to paste this issue because related to
github-actions
.Once posted, I'll probably have to migrate this post somewhere more meaningful.
Nevertheless, I'm having a problem with
semantic-release-firefox-add-on@0.2.7
with this pipelineWhat I expect
The addon to be signed.
What is happening
I'm having the following error:
Very similar to this PR 94.
This PR fixed the problem in 0.2.5
Thoughts
This situation is strange...
My local dry-runs are fine and I suspect
github-actions
to be the culprit.EDIT no
Could this be related to the version of
node
?github-actions supports up to v12 AFAIK. I'm running v15 in local dev environment.
EDIT no
I could
cat
the installed source ofsrc/publish.js:5
installed vianpm
within the pipeline, to double-check the code...But why would the
npm i
outputsemantic-release-firefox-add-on@0.2.7
Caching issues from github ?
Please see the logs of the following command:
output