Update customize to the latest version 🚀#5
Open
greenkeeper[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
Author
Version 2.0.0 just got published. |
Author
Version 2.0.1 just got published. |
Author
Version 2.0.1 just got published. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version 2.0.0 of customize just got published.
The version 2.0.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 customize.
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.
Commits
The new version differs by 21 commits .
195a34cBump to version: v2.0.0d1b891aMerge branch 'next'09331ceUpdate documentation69cbd21Remove obsolete precommit-hook (and husky)7f7e1d4Fix tests, remove dependency on "m-io" in favour of "glob"94a8038Remove dependency on "q" (now completely)ef29319Remove dependency on "q"631ec00Remove obsolete "trace" from dev-dependencies51c75ddchore: enable no-console rule in eslintf1edef6chore: enable no-console rule in eslint130e29cchore: eslint with standard-config instead of standardb67a2dc2.0.0-alpha1aba06d2Run thought and add thought-plugin-jsdoc56c95c0BREAKING: Remove support for js-quantities in configuration schemas3042778Remove lodash dependencyThere are 21 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴