leecade / leecade/fe

An in-range update of replace-ext is breaking the build 🚨

Open
#114 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency replace-ext was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

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

replace-ext 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/appveyor/branch: AppVeyor build failed (Details).
  • ❌ Travis CI - Branch: The build errored.
  • ❌ Build: Your Google Cloud Platform project is not set up correctly for this GitHub app. Please go through the setup flow again in the cloud console.
Commits

The new version differs by 5 commits.

  • 2c67ddd Release: 1.0.1
  • 8bee038 Fix: Preserve first dot of relative path (fixes #5)
  • a55455a Scaffold: Normalize repository
  • 9047016 Scaffold: Add Tidelift security & marketing
  • 93a5b14 Build: Enforce consistent line endings

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

No contributing guide indexed for this repository

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 with the Greenkeeper failing branch and compare it with master, then inspect the AppVeyor and Travis CI failure details. Trace the replace-ext 1.0.1 update through the project’s dependency configuration and identify the change needed for the build to pass with a supported dependency version.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system
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.