Version 0.25.38 of @types/ramda was just published.

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

@types/ramda 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 🌴

https://ics.media/entry/18733

■ 目的
コミットコメントから判断して、package.jsonのバージョンを上げる仕組みを作る

■ ルール
コミットコメントを抽出してバージョンを上げる

■ 現在のpackage.jsonを取得するコマンド

• https://qiita.com/sakatam/items/d2b28be5a32a7b83a85f

■ npm versionコマンドで自動でアップデート

• npm version major => + 1.0.0

やること

• dockerファイルを作成する
• herokuにdockerで無事デプロイできるようにする

目的

現状のタグ名だと、どんな内容をマージしたかわからないので
マージしたブランチ名をわかるようなタグを生成する

かつ、デプロイされていないブランチもタグで可視化を試みる

現状

• master ブランチにマージ

master_2018_0924_2319

• production ブランチにマージ

production_2018_0925_0037

• staging ブランチにマージ

staging_2018_0925_0041

変更後

• master ブランチにマージ

master←←←issues/#300-change-hoge_2018_0924

• 同時にデプロイしていない � ことを示すタグも作成

#300-prod-no-deploy
#300-stg-no-deploy

• production ブランチにマージ

prod←←←#300_2018_0924

• 同時にデプロイしていない � ことを示すタグを削除

$ git tag -d #300-no-deploy

• staging ブランチにマージ

stg←←←#300_2018_0924

やること

タグの生成とタグ名を変更する

• cypress以外のパッケージの削除
• cypressをヘッドレスで実行する
• sampleのテストを作成する

https://medium.com/@MarkPieszak/using-pug-or-jade-templates-with-the-angular-cli-9e37334db5bc

🚨 You need to enable Continuous Integration on all 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The devDependency @types/node was updated from 10.10.0 to 10.10.1.

🚨 View failing branch.

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

@types/node 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 🌴

https://qiita.com/icoxfog417/items/92214aed64f47dfeade5

https://tech.recruit-mp.co.jp/dev-tools/post-14868/

まだ機能を実装していないので追加で実装する

process.envのファイルをenv.tsに書き込む

https://blog.angularindepth.com/building-interactive-lists-with-the-new-angular-7-drag-and-drop-tool-5f2402f8cb27

やること

1. ng update @angular/compiler-cli　を実行
2. ng serve を実行

https://github.com/angular-schule/angular-cli-ghpages

The devDependency @angular-devkit/build-angular was updated from 0.8.1 to 0.8.2.

🚨 View failing branch.

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

@angular-devkit/build-angular 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 🌴

wait-onのhttpを変更することで解決できた
https://github.com/bahmutov/start-server-and-test#note-for-webpack-dev-server-users

• 現状
  wait-on http://localhost:4200
  ↓
• 変更後
  wait-on http-get://localhost:4200