Update loopback-datasource-juggler to version 3.6.0 🚀#249
Open
greenkeeperio-bot wants to merge 1 commit intomasterfrom
Open
Update loopback-datasource-juggler to version 3.6.0 🚀#249greenkeeperio-bot wants to merge 1 commit intomasterfrom
greenkeeperio-bot wants to merge 1 commit intomasterfrom
Conversation
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
2 participants
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.
Hello lovely humans,
loopback-datasource-juggler just published its new version 3.6.0.
This version 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-datasource-juggler.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 427 commits (ahead by 427, behind by 72).
6bbad5e3.6.0156b638Merge pull request #1356 from strongloop/datetype-allow-strings5d10c72create sequence for nosql id (#1354)6342a03Merge pull request #1364 from strongloop/query-order6cfdcc0Fix order of query results5e80837Add DateString type97f243fMerge pull request #1360 from strongloop/datatype-test/use-predefined-date8e97385datatype.test: use predefined datef804663Merge pull request #1358 from strongloop/api-doc-2ef61c86Update api documentsbf7ea4cMerge pull request #1333 from strongloop/api-doc-refactorf7fe187Datasource documentation tune-up238175bAdded unit tests specific to DateType where null (#1349)e9ff88fFix/geo null (#1334)ee254a1Merge pull request #1339 from strongloop/invalid-datesThere are 250 commits in total. See the full diff.