pelias / pelias/sorting

An in-range update of geolib is breaking the build 🚨

Open
#24 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
2
Forks
4
No merged PRs in 30d

Description

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! πŸ’œ πŸššπŸ’¨ πŸ’š

Find out how to migrate to Snyk at greenkeeper.io

The dependency geolib was updated from 3.2.2 to 3.3.0.

🚨 View failing branch.

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

geolib 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 could not complete due to an error (Details).
Release Notes for v3.3.0

3.3.0 (2020-05-24)

🧩 Features
  • re-export constants so they can be used by library consumers (1a5e214)
πŸ’‰ Improvements
  • update all deps and make release workflow work with external config (2cf5513)
  • update node image during ci (17c821f)
  • use external release-config to publish new releases with automated CHANGELOG.md (81b4bce)
Commits

The new version differs by 6 commits.

  • f7e5cd8 release: 3.3.0 - 2020-05-24T12:53:36.058Z [skip ci]
  • 17c821f chore: update node image during ci
  • 1a5e214 feat: re-export constants so they can be used by library consumers
  • 2cf5513 chore: update all deps and make release workflow work with external config
  • 6cd7713 Merge branch 'master' of github.com:manuelbieh/geolib
  • 81b4bce chore: use external release-config to publish new releases with automated CHANGELOG.md

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the failing branch and the linked Travis CI build, then compare the project's behavior with geolib 3.2.2 and 3.3.0. The payload names no project files or tests; done means identifying the dependency incompatibility and restoring a passing build.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.