The version 0.2.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ember-cli-node-assets.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv0.2.0
Addon authors upgrading from v0.1.x, note that this release impacts behavior when your addon is included as a transitive dependency! See the notes for the beta releases below.
Fixed
The engines entry in package.json now reflects that this addon requires Node 4+.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.2.0 of ember-cli-node-assets just got published.
The version 0.2.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ember-cli-node-assets. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v0.2.0Addon authors upgrading from v0.1.x, note that this release impacts behavior when your addon is included as a transitive dependency! See the notes for the beta releases below.
Fixed
engines
entry inpackage.json
now reflects that this addon requires Node 4+.Commits
The new version differs by 14 commits .
3ad049e
Released v0.2.0
0c14e69
Update README.md
4a0624b
Update README.md
e6fa7b0
Update engine entry
00602ce
Released v0.2.0-beta.2
dfa162c
Update CHANGELOG.md for 0.2.0-beta.2
33f2219
Call config functions with the proper
this
value.b6c686d
Update README.md
83253dc
Further README updates
b614585
0.2.0-beta.1
c9878db
CHANGELOG updates
ba3f4c3
Refactor and redocument for 0.2.0.
5754dcd
Bump dependencies, add Yarn
f9d6bb1
Mention AMD support
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: