An in-range update of ember-cli-moment-shim is breaking the build 🚨

Open
#1,765 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the failing branch linked in the issue and inspect the CircleCI build details for the update from ember-cli-moment-shim 3.7.1 to 3.8.0. Compare the dependency's listed commits with the failure, then verify that the project build and tests pass with the in-range update.

Written by the indexing model from the issue text.

Description

greenkeeper

🚨 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 devDependency ember-cli-moment-shim was updated from 3.7.1 to 3.8.0.

🚨 View failing branch.

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

ember-cli-moment-shim 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.

Status Details
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

  • 0d03b9a 3.8.0
  • 6486929 fix: Remove tz min into vendor tree.
  • 96825ab Bundle un-minified assets (#184)
  • b06bb63 Fix for fastboot (#172)
  • 5885a69 Upgrade Ember, and Friends (#171)
  • 254de7c Update to ember-cli 3.4.3 (#169)

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 🌴

Dominant language
JavaScript
Stars
120
Forks
75
PR merge metrics
No merged PRs in 30d

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.

More from code-corps/code-corps-ember

All issues in code-corps/code-corps-ember

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.