🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

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 fix 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 main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

Invalid npm token.

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 for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization 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 📦🚀

Error message
(node:5954) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/swarali/.npm/_npx/5826/lib/node_modules/@adobe/create-helix-service/template/dot-eslintignore'
(node:5954) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5954) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: config
Error type: Invalid allowedVersions
Message: The following allowedVersions does not parse as a valid version or range: "<15>"

The dependency @adobe/helix-status was updated from 4.3.3 to 4.3.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/helix-status is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Run npm init @adobe/helix-service, go through the wizard (Development service) and you get:

Created directory xyz

Copying test/post-deploy.js
Copying test/index.test.js
Copying test/index-epsagon.test.js
Skipping template
Copying src/index.js
Skipping package.json
Skipping node_modules
Copying docs/API.md
Copying create-helix-service.js
Skipping README.md
Copying LICENSE.txt
Copying CONTRIBUTING.md
Copying CODE_OF_CONDUCT.md
Copying CHANGELOG.md
Copying completed

Patching package.json
Patching README.md
Patching package-lock.json
Patching .eslintignore
Patching .eslintrc.js
Patching .releaserc.js
Patching .npmignore
Patching .gitignore
Patching config.yml
(node:60791) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/acapt/.npm/_npx/60274/lib/node_modules/@adobe/create-helix-service/template/.circleci/config.yml'
(node:60791) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:60791) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Description
npm test doesn't show failing tests:

----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |      100 |      100 |      100 |      100 |                   |
 index.js |      100 |      100 |      100 |      100 |                   |
----------|----------|----------|----------|----------|-------------------|
npm ERR! Test failed.  See above for more details.

Expected behavior
Details about the failing test(s) should be provided when running npm test, e.g.

1) Index Tests
       index function return statusCode:

      AssertionError [ERR_ASSERTION]: 200 == 400
      + expected - actual

      -200
      +400
      
      at Context.it (test/index.test.js:30:12)

----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |      100 |      100 |      100 |      100 |                   |
 index.js |      100 |      100 |      100 |      100 |                   |
----------|----------|----------|----------|----------|-------------------|
npm ERR! Test failed.  See above for more details.

Description
The "istanbul": "^1.1.0-alpha.1" dependency in the package.json is redundant. We're using nyc in the scripts and the nyc dependency already includes istanbul.

Furthermore there's the risk of potential conflicts. request 2.88.0 e.g. has a dependency on nyc 14.1.1 which in turn conflicts with istanbul 1.1.0-alpha.1. This conflict leads to the following error when running npm test:

internal/modules/cjs/loader.js:584
    throw err;
    ^

Error: Cannot find module 'xunit'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)

To Reproduce
Steps to reproduce the behavior:

1. add [email protected] dependency to package.json
2. npm i && npm test
3. See above error

See adobe/helix-ops#35 for details.

adobe/helix-data-embed#2

Run npm init @adobe/helix-service and fill with wizard with "dummy" (to generate a helix-dummy service).
Run npm run deploy

-> the generated action is service: "https://adobeioruntime.net/api/v1/web/acapt/helix-services-private/[email protected]

Expect: action name is helix-dummy like everything else.

Wrong

curl https://adobeioruntime.net/api/v1/web/helix/helix-services/service@v1

correct

curl https://adobeioruntime.net/api/v1/web/helix/helix-services/data-embed@v1

Example: adobe/helix-data-embed@7255d2f

When creating a new helix service with npm init @adobe/helix-service, creation of the git repo fails:

(node:7451) UnhandledPromiseRejectionWarning: Error: Command failed: git init -b main
error: unknown switch `b'
usage: git init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]] [<directory>]

According to this stackoverflow article, one needs to specify the default branch name in two steps.

The devDependency @semantic-release/github was updated from 5.4.1 to 5.4.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@semantic-release/github is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @adobe/openwhisk-action-builder was updated from 1.3.1 to 1.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@adobe/openwhisk-action-builder is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Use the new urlPatternsToIgnore from epsagon/epsagon-node#211 to exclude the Coralogix Host names – then roll this out to other repos.

The key/value order for the monitoring config doesn't match, see adobe/helix-slack-notification@8f6ba09 for the latest example.

This causes havoc in New Relic and Statuspage when the service gets built for the first time.

Wrong:

  "wsk": {
    "name": "helix-services-private/helix-data-embed@${version}",
    "linksPackage": "helix-services"
  },

Correct:

  "wsk": {
    "name": "helix-services-private/data-embed@${version}",
    "linksPackage": "helix-services"
  },

see adobe/helix-data-embed@db45763 for a fix

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

helix-pingdom-status provides an easy wrapper to make services more monitorable.