The devDependency semantic-release was updated from 15.13.15 to 15.13.16.

🚨 View failing branch.

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

semantic-release 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 @semantic-release/commit-analyzer was updated from 6.1.1 to 6.2.0.

🚨 View failing branch.

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

@semantic-release/commit-analyzer 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 🌴

Overview

I think we should adopt Semantic Release as the default mechanism to release in Project Helix (at least for all libraries, services are a different discussion) and adjust the starter repo to include it.

Details

I've been using Semantic Release for https://github.com/adobe/fastly-native-promises simply because the original project used it, and I have grown to like it.

Cons:

• you have to commit using npm run commit and fill out a questionnaire
• it encourages bigger commits than I prefer

Pros:

• the release can be fully automated, in fact semantic-release only works in a CI environment
• you get proper NPM releases like: https://www.npmjs.com/package/@adobe/fastly-native-promises/v/1.3.2 (without doing anything)
• you get proper GitHub releases like https://github.com/adobe/fastly-native-promises/releases/tag/v1.3.2 (without doing anything)
• you get a proper CHANGELOG.md like https://github.com/adobe/fastly-native-promises/blob/v1.3.2/CHANGELOG.md#132-2019-01-22 (without doing anything)
• issues get a nice status update once they have been fixed in a release like this: adobe/fastly-native-promises#27 (comment) and they get tagged as released (without doing anything)
• same for PRs: adobe/fastly-native-promises#28 (comment)

Proposed Actions

• adjust this repo to use semantic-release
• implement semantic-release for helix-shared
• implement semantic-release for helix-pipeline
• implement semantic-release for htlengine
• implement semantic-release for helix-cli
• implement semantic-release for git-server
• implement semantic-release for helix-simulator
• implement semantic-release for vscode-helix (there is a plugin for the VS Code Marketplace)

The devDependency eslint-plugin-import was updated from 2.17.3 to 2.18.0.

🚨 View failing branch.

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

eslint-plugin-import 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 @semantic-release/git was updated from 7.0.11 to 7.0.12.

🚨 View failing branch.

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

@semantic-release/git 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 snyk was updated from 1.195.0 to 1.195.1.

🚨 View failing branch.

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

snyk 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 eslint-plugin-jsx-a11y was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

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

eslint-plugin-jsx-a11y 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 🌴

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.

Error type: undefined

https://circleci.com/gh/adobe/helix-auth-fastly/1

#!/bin/bash -eo pipefail
npm run lint

> @adobe/[email protected] lint /home/circleci/project
> eslint .


Oops! Something went wrong! :(

ESLint: 6.6.0.

ESLint couldn't find a configuration file. To set up a configuration file for this project, please run:

    eslint --init

ESLint looked for configuration files in /home/circleci/project and its ancestors. If it found none, it then looked in your home directory.

If you think you already have a configuration file or if you need more help, please stop by the ESLint chat room: https://gitter.im/eslint/eslint

Initialising a git repo with a branch name as here:

https://github.com/adobe/helix-library/blob/1ceaa97fd374b108fcdb0af377594131178f1e60/create-helix-shared.js#L177

causes an error with git available from macOS Command Line Developer Tools (2.24.3):

(node:7797) UnhandledPromiseRejectionWarning: Error: Command failed: git init -b main
error: unknown switch `b'

Instead, one should use the following two separate commands:

git init
git checkout -b main

as suggested in stackoverflow

The devDependency snyk was updated from 1.170.0 to 1.171.0.

🚨 View failing branch.

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

snyk 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 🌴

🚨 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.

The devDependency @semantic-release/release-notes-generator was updated from 7.1.7 to 7.2.0.

🚨 View failing branch.

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

@semantic-release/release-notes-generator 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 🌴

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

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update actions/checkout digest to a5ac7e5

Detected dependencies

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

See adobe/helix-redirect-accelerator#1

The devDependency eslint-config-airbnb was updated from 17.1.0 to 17.1.1.

🚨 View failing branch.

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

eslint-config-airbnb 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 snyk was updated from 1.157.0 to 1.157.1.

🚨 View failing branch.

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

snyk 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 @semantic-release/npm was updated from 5.1.10 to 5.1.11.

🚨 View failing branch.

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

@semantic-release/npm 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 snyk was updated from 1.177.0 to 1.177.1.

🚨 View failing branch.

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

snyk 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 @semantic-release/github was updated from 5.3.5 to 5.4.0.

🚨 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 🌴

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.

Is your feature request related to a problem? Please describe.
.gitignore and .vscode not copied over to new repos using bootstrapping

Describe the solution you'd like
copy .gitignore most helix-services have same structure like a node_modules directory etc etc.
Don't want to have to reinvent the wheel on listing things we don't want in our git commits.

Describe alternatives you've considered
copy and paste .gitignore and .vscode from another repo

The devDependency eslint-plugin-react was updated from 7.13.0 to 7.14.0.

🚨 View failing branch.

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

eslint-plugin-react 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 test folder is missing

The devDependency @semantic-release/changelog was updated from 3.0.3 to 3.0.4.

🚨 View failing branch.

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

@semantic-release/changelog 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 🌴