tophat / semantic-release-firefox-add-on Goto Github PK
View Code? Open in Web Editor NEW🦊 A Semantic Release plugin to sign Firefox Add Ons using web-ext
License: Apache License 2.0
🦊 A Semantic Release plugin to sign Firefox Add Ons using web-ext
License: Apache License 2.0
See @tophat/eslint-config
npm package
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 [email protected]
with this pipeline
The addon to be signed.
I'm having the following error:
[4:39:10 AM] [semantic-release] › ✖ An error occurred while running semantic-release: TypeError: defaultAddonSigner is not a function
at signAddon (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/src/publish.js:31:30)
at /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/web-ext/dist/web-ext.js:1:70282
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at publish (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/src/publish.js:43:33)
at validator (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/node_modules/p-reduce/index.js:16:18) {
pluginName: 'semantic-release-firefox-add-on'
}
TypeError: defaultAddonSigner is not a function
at signAddon (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/src/publish.js:31:30)
at /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/web-ext/dist/web-ext.js:1:70282
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at publish (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/src/publish.js:43:33)
at validator (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/node_modules/p-reduce/index.js:16:18) {
pluginName: 'semantic-release-firefox-add-on'
}
Very similar to this PR 94.
This PR fixed the problem in 0.2.5
This situation is strange...
My local dry-runs are fine and I suspect github-actions
to be the culprit.
EDIT no
node
?github-actions supports up to v12 AFAIK.
I'm running v15 in local dev environment.
EDIT no
cat
the installed source of src/publish.js:5
installed via npm
within the pipeline, to double-check the code...But why would the npm i
output [email protected]
Please see the logs of the following command:
npm install -g \
semantic-release \
@semantic-release/github \
@semantic-release/git \
@semantic-release/exec \
@semantic-release/changelog \
@semantic-release/npm \
semantic-release-chrome \
semantic-release-firefox-add-on \
aggregate-error \
sign-addon
output
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated js-select@0.6.0: Package no longer supported. Contact support@npmjs.com for more info.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated jetpack-id@1.0.0: Jetpack extensions are no longer supported by Firefox. Use web-ext instead to build a WebExtension.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
/opt/hostedtoolcache/node/12.19.0/x64/bin/semantic-release -> /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release/bin/semantic-release.js
> dtrace-provider@0.8.8 install /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/dtrace-provider
> node-gyp rebuild || node suppress-error.js
make: Entering directory '/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/dtrace-provider/build'
TOUCH Release/obj.target/DTraceProviderStub.stamp
make: Leaving directory '/opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/dtrace-provider/build'
> core-js@2.6.12 postinstall /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> [email protected] postinstall /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/semantic-release-firefox-add-on/node_modules/spawn-sync
> node postinstall
> [email protected] postinstall /opt/hostedtoolcache/node/12.19.0/x64/lib/node_modules/sign-addon/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/semantic-release-firefox-add-on/node_modules/addons-linter/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/semantic-release-firefox-add-on/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/semantic-release-firefox-add-on/node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
+ @semantic-release/exec@5.0.0
+ semantic-release-firefox-add-on@0.2.7
+ sign-addon@3.1.0
+ @semantic-release/git@9.0.0
+ semantic-release@17.3.0
+ @semantic-release/npm@7.0.8
+ semantic-release-chrome@1.1.3
+ aggregate-error@3.1.0
+ @semantic-release/github@7.2.0
+ @semantic-release/changelog@5.0.1
added 1870 packages from 1354 contributors in 40.666s
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
Is your feature request related to a problem? Please describe.
Firefox AMO sometimes requests the upload of source code and instructions on how to build the code. Also, it'd be nice to provide release notes but that's less critical in my view then the stuff reviewers need.
Describe the solution you'd like
There should be a publish parameter for both fields.
Describe alternatives you've considered
Right now it's a manual workaround to go to the AMO page, and edit the pending release.
Additional context
$ /Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/.bin/semantic-release
[12:47:09 AM] [semantic-release] › ℹ Running semantic-release version 15.13.18
[12:47:09 AM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "semantic-release-firefox-add-on"
[12:47:09 AM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[12:47:09 AM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[12:47:09 AM] [semantic-release] › ✔ Loaded plugin "prepare" from "semantic-release-firefox-add-on"
[12:47:09 AM] [semantic-release] › ✔ Loaded plugin "publish" from "semantic-release-firefox-add-on"
[12:47:09 AM] [semantic-release] › ⚠ This run was not triggered in a known CI environment, running in dry-run mode.
[12:47:09 AM] [semantic-release] › ⚠ Run automated release from branch test-semantic-release-firefox in dry-run mode
[12:47:11 AM] [semantic-release] › ✔ Allowed to push to the Git repository
[12:47:11 AM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "semantic-release-firefox-add-on"
[12:47:11 AM] [semantic-release] › ✖ Failed step "verifyConditions" of plugin "semantic-release-firefox-add-on"
[12:47:11 AM] [semantic-release] › ✖ An error occurred while running semantic-release: Error: FIREFOX_API_KEY is missing from the environment
FIREFOX_SECRET_KEY is missing from the environment
at throwErrors (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release-firefox-add-on/src/utils.js:3:15)
at verifyConditions (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release-firefox-add-on/src/verifyConditions.js:34:5)
at validator (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at /Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
at next (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/p-reduce/index.js:17:9)
at processTicksAndRejections (internal/process/task_queues.js:85:5) {
pluginName: 'semantic-release-firefox-add-on'
}
AggregateError:
Error: FIREFOX_API_KEY is missing from the environment
FIREFOX_SECRET_KEY is missing from the environment
at throwErrors (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release-firefox-add-on/src/utils.js:3:15)
at verifyConditions (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release-firefox-add-on/src/verifyConditions.js:34:5)
at validator (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at /Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
at next (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/p-reduce/index.js:17:9)
at /Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/pipeline.js:54:11
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at Object.pluginsConf.<computed> [as verifyConditions] (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/lib/plugins/index.js:80:11)
at run (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/index.js:82:3)
at module.exports (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/index.js:168:22)
at module.exports (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/semantic-release/cli.js:55:5) {
name: 'AggregateError'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Command failed: yarn semantic-release
at checkExecSyncError (child_process.js:623:11)
at Object.execSync (child_process.js:659:15)
at /Users/Emmanuel/Sources/tophat-dev-tools-extension/release/run.ts:27:5
at Object.<anonymous> (/Users/Emmanuel/Sources/tophat-dev-tools-extension/release/run.ts:28:3)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Module.m._compile (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/ts-node/src/index.ts:473:23)
at Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Object.require.extensions.<computed> [as .ts] (/Users/Emmanuel/Sources/tophat-dev-tools-extension/node_modules/ts-node/src/index.ts:476:12)
at Module.load (internal/modules/cjs/loader.js:643:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Describe the bug
semantic-release-firefox-add-on
fails to publish an add-on with the following config (which has only extensionId
and targetXpi
).
semantic-release-firefox-add-on
refers to 'artifacts/artifacts/XXX.xpi' wrongly in the publishment phase though artifacts/XXX.xpi
is generated.
[
"semantic-release-firefox-add-on",
{
"extensionId": "[email protected]",
"targetXpi": "dist.xpi"
}
],
Here is the fragment of our error log.
Downloaded:
artifacts/plantuml_visualizer-1.5.2-an+fx.xpi
Extension ID: [email protected]
SUCCESS
[11:55:12 AM] [semantic-release] › ✖ Failed step "publish" of plugin "semantic-release-firefox-add-on"
[11:55:12 AM] [semantic-release] › ✖ An error occurred while running semantic-release: Error: ENOENT: no such file or directory, rename 'artifacts/artifacts/plantuml_visualizer-1.5.2-an+fx.xpi' -> 'artifacts/dist.xpi'
at Object.renameSync (fs.js:661:3)
at publish (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release-firefox-add-on/src/publish.js:58:8)
at validator (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/p-reduce/index.js:16:18) {
errno: -2,
syscall: 'rename',
code: 'ENOENT',
path: 'artifacts/artifacts/plantuml_visualizer-1.5.2-an+fx.xpi',
dest: 'artifacts/dist.xpi',
pluginName: 'semantic-release-firefox-add-on'
}
Error: ENOENT: no such file or directory, rename 'artifacts/artifacts/plantuml_visualizer-1.5.2-an+fx.xpi' -> 'artifacts/dist.xpi'
at Object.renameSync (fs.js:661:3)
at publish (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release-firefox-add-on/src/publish.js:58:8)
at validator (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/home/runner/work/plantuml-visualizer/plantuml-visualizer/node_modules/p-reduce/index.js:16:18) {
errno: -2,
syscall: 'rename',
code: 'ENOENT',
path: 'artifacts/artifacts/plantuml_visualizer-1.5.2-an+fx.xpi',
dest: 'artifacts/dist.xpi',
pluginName: 'semantic-release-firefox-add-on'
}error Command failed with exit code 1.
To Reproduce
We've faced this issue in our OSS (https://github.com/WillBooster/plantuml-visualizer). You may see the full log of semantic-release-firefox-add-on
when we tried to publish an add-on in GitHub Actions (https://github.com/WillBooster/plantuml-visualizer/runs/597736803).
Expected behavior
semantic-release-firefox-add-on
with the default parameters should refer to 'artifacts/artifacts/XXX.xpi' instead of 'artifacts/XXX.xpi'.
Screenshots
Please see the error log (https://github.com/WillBooster/plantuml-visualizer/runs/597736803)
Desktop (please complete the following information):
Additional context
I believe the default value of artifactsDir
should be .
instead of ./artifacts
because targetXpi
(https://github.com/tophat/semantic-release-firefox-add-on/blob/master/src/publish.js#L58-L61) probably includes the directory path ./artifacts
in addition to .xpi
file name.
Version: 0.2.2
Runs on: ubuntu-latest on GitHub Actions
The publish step fails when I submit my add-on to AMO. Although a new version is actually uploaded for review, the publish step fails, so the subsequent plugins are not executed.
web-ext
seems to throw an error when submitting a listed add-on (ref. mozilla/web-ext#804 ).
Could you please work around it? (like https://github.com/fregante/web-ext-submit ?)
Log:
[3:08:17 PM] [semantic-release] › ℹ Start step "publish" of plugin "semantic-release-firefox-add-on"
Building web extension from dist/firefox/production
Validating add-on [ . ]
...
Validating add-on [............................................................]
Validation results: https://addons.mozilla.org/en-US/developers/upload/********************************
Signing add-on [ . ]
Signing add-on [...............................................................]
Your add-on has been submitted for review. It passed validation but could not be automatically signed because this is a listed add-on.
FAIL
[3:08:23 PM] [semantic-release] › ✖ Failed step "publish" of plugin "semantic-release-firefox-add-on"
[3:08:23 PM] [semantic-release] › ✖ An error occurred while running semantic-release: o: The extension could not be signed
at /home/runner/work/uBlacklist/uBlacklist/node_modules/web-ext/dist/web-ext.js:1:66345
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at publish (/home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release-firefox-add-on/src/publish.js:25:42)
at validator (/home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/home/runner/work/uBlacklist/uBlacklist/node_modules/p-reduce/index.js:16:18) {
pluginName: 'semantic-release-firefox-add-on'
}
o: The extension could not be signed
at /home/runner/work/uBlacklist/uBlacklist/node_modules/web-ext/dist/web-ext.js:1:66345
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at publish (/home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release-firefox-add-on/src/publish.js:25:42)
at validator (/home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
at /home/runner/work/uBlacklist/uBlacklist/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
at async Promise.all (index 0)
at next (/home/runner/work/uBlacklist/uBlacklist/node_modules/p-reduce/index.js:16:18) {
pluginName: 'semantic-release-firefox-add-on'
}
##[error]Process completed with exit code 1.
Configure the e2e folder to build and upload the fake add-on
dryRun: false
and actually publish a fake add-on.
addons-dev.allizom.org
seems available instead (ref).Originally posted by @iorate in #94 (comment)
Thank you for merging my PR (#90), fixing it (sorry for not knowing that webExt.cmd.sign
uses a temporary directory) and adding tests.
However, I cannot install v0.2.3 to my project because the postinstall step fails:
> [email protected] postinstall /path/to/my/project/node_modules/semantic-release-firefox-add-on
> yarn-deduplicate
yarn-deduplicate: command not found
npm WARN [email protected] requires a peer of semantic-release@^16.0.0 but none is installed. You must install peer dependencies yourself.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `yarn-deduplicate`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
It's because yarn-deduplicate
is a dev dependency so isn't installed to my project, and even if I install yarn-deduplicate
manually, it fails because my project has no yarn.lock
(using npm
and package-lock.json
instead).
Would you please update the postinstall script for non-yarn projects?
Hi, thanks for the package, i have some issues with extensionId
:
I've tried to use the next value, as specified in mine manifest.json:
"browser_specific_settings": {
"gecko": {
"id": "{f597ac1d-8bad-5110-82f9-bcd6b655c47b}"
}
}
but received an error:
Cannot set custom ID {f597ac1d-8bad-5110-82f9-bcd6b655c47b} because manifest.json declares ID {f597ac1d-8bad-5110-82f9-bcd6b655c47b}
As I understood it is related to web-ext issue where the suggested solution is to omit extensionId
value.
However in this case I cant pass verifyConditions step.
No extensionId was specified in package.json. Omitting this would create a new extension instead of a new version
Can I run webext without extensionId?
Desktop (please complete the following information):
Additional context
I need gecko.id in the manifest to access storage.sync feature.
Replace felixfbecker/semantic-release-firefox
on the semantic-release plugin list.
felixfbecker/semantic-release-firefox
is currently broken. It relies on running puppeteer to interact with the web interface of the mozilla webstore to sign and upload extensions, this makes it brittle as the website is subject to change.
tophat/semantic-release-firefox-add-on
uses Mozilla's web extension api
Is your feature request related to a problem? Please describe.
Inspired by this issue
When utilizing the semantic-release package's pre-release functionality, the semantic-release-chrome's chrome web api call throws a version format error.
This is preventing me from publishing a new version of my chrome extension to a staging extension while maintaining the pre-release functionality on my develop branch.
Describe the solution you'd like
Add an optional boolean allowPrerelease
field to the PluginConfig interface. When allowPrerelease
is specified and set to true
, the semantic version number is parsed from the given version string instead of using the raw string. For example, if 1.0.0-develop.1
is the given pre-release version, then 1.0.0
will be parsed and used for the version.
Additionally, we can set the original release version (1.0.0-develop.1
) to the version_name field for displaying purpose.
Issues and pull request events (open, closed) should be sent to #semantic-release-firefox
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.