Update js-beautify to the latest version 馃殌 #33
Closed
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 1.7.2 just got published.Update to this version instead 馃殌 CommitsThe new version differs by 8 commits.
See the full diff |
Version 1.7.3 just got published. |
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 1.7.1 of js-beautify just got published.
The version 1.7.1 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 js-beautify.
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 23 commits.
7c1b388Switch python to using twine0ac845e1.7.05b3c36cPython 1.7.09276881Bump version numbers in README.md1bd274dUpdate Changelog for 1.7.0ea252d1Package lock update9d733b5Merge pull request #1243 from bitwiseman/feature/polycbbb2e0Merge branch 'master' into feature/poly453bdc9Fixed yield function spacing468815eMerge pull request #1241 from simondel/mastera46f97cREADME, LICENSE, CHANGELOG and package.json are always addedf56a513Remove Object.value polyfill641d3bcDon't publish unnessessary files.ed61dc1Merge pull request #1240 from aecepoglu/unindent-chains-2258a361adding the generated filesThere are 23 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 馃尨