aethant / aethant/merino

An in-range update of browser-sync is breaking the build 🚨

Abierto
#405 2 comentarios 0 reacciones 0 asignados Ver en GitHub
greenkeeper
Lenguaje dominante
Sin datos de lenguaje
Estrellas
3
Forks
1
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

## The dependency [browser-sync](https://github.com/BrowserSync/browser-sync) was updated from `2.26.5` to `2.26.6`.

🚨 [View failing branch](https://github.com/aethant/merino/compare/master...aethant:greenkeeper%2Fbrowser-sync-2.26.6).

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

browser-sync 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.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/aethant/merino/builds/542653880?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 11 commits.



  • 0b3d98b v2.26.6

  • fdfc681 tests: add e2e tests to package.json

  • c56cfd9 Merge pull request #1698 from emeitch/fix_deprecated_header

  • 2fd598f Merge pull request #1690 from XhmikosR/xmr-ci

  • 841ccd5 Merge pull request #1694 from coliff/patch-1

  • 209c9c1 Merge pull request #1697 from gaards/update-localtunnel

  • 87bee4b Use getHeaders or _headers

  • 77abfd3 Update localtunnel

  • 1f073f9 Remove gittip from README (service closed down)

  • 51792b1 AppVeyor tweaks.

  • 9c9d71a CI: Add Node.js 12 and 10.


See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Start with the failing branch comparison and the Travis CI build linked in the issue to identify which build step fails after browser-sync moves from 2.26.5 to 2.26.6. Reproduce the failure with the updated dependency, determine whether the project or dependency version needs adjustment, and confirm that the build passes.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
node.js
Área
build-system
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.