Update loopback-component-explorer to the latest version 🚀 #7
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 5.1.0 just got published. |
Version 5.2.0 just got published. |
Version 5.3.0 just got published. |
Version 5.4.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits.
See the full diff |
Version 6.0.0 just got published. |
Version 6.0.1 just got published. |
Version 6.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Version 6.2.0 just got published. |
|
|
Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
|
|
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 5.0.0 of loopback-component-explorer just got published.
The version 5.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 loopback-component-explorer.
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 20 commits.
7da9a135.0.03ea35aeMerge pull request #219 from strongloop/scoped_models414a512Increment loopback-swagger verdecb7a9Merge pull request #220 from strongloop/remove-strml-from-reviewsfb8f871CODEOWNERS: turn off PR notifications for STRML6553c5bMerge pull request #218 from strongloop/version_changeaf3b8b5version no to 5.0.0c629599Merge pull request #217 from strongloop/updateonly_feature015f5e7bump swagger version to 4.x183e105Add stalebot configuration5814cf4Update Issue and PR Templates (#216)c0c9bd7Merge pull request #215 from strongloop/piiReturnQ320176991e2fUpdate translated strings Q3 20175f7da2eMerge pull request #214 from strongloop/translate41c4d54Merge pull request #203 from strongloop/replicate-issue-templateThere are 20 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 🌴