Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

build(defaults): update to v1.6.0 #652

Merged
merged 3 commits into from
Oct 20, 2017
Merged

Conversation

joshwiens
Copy link
Member

  • Updates to minimum Node version of 4.8 ( npm 5 compatibility )
  • Update devDependencies via npm run webpack-defaults
  • Semantic changes to both CI configurations

@codecov
Copy link

codecov bot commented Oct 20, 2017

Codecov Report

Merging #652 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #652   +/-   ##
=======================================
  Coverage   87.41%   87.41%           
=======================================
  Files           7        7           
  Lines         302      302           
  Branches       68       68           
=======================================
  Hits          264      264           
  Misses         36       36           
  Partials        2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cfde50...ce1e5a8. Read the comment docs.

@michael-ciniawsky michael-ciniawsky changed the title chore: Update to defaults 1.6 build(defaults): update to v1.6.0 Oct 20, 2017
@michael-ciniawsky michael-ciniawsky merged commit 5286ab2 into master Oct 20, 2017
@michael-ciniawsky michael-ciniawsky deleted the d3viant0ne-Defaults-1.6 branch October 20, 2017 16:01
@felixjung
Copy link

Why was this not listed as a breaking change in the release notes? Our build is now failing because of the Node version requirement 😢

@michael-ciniawsky
Copy link
Member

The node version bump itself is within the semver minor range, I know it's annoying in your case, but we needed to bump it bc of npm@5 and we simply can't release any nitty-gritty as semver major. It's assumed that folks use the @latest within their current semver major range

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants