Hello lovely humans,
mongoose just published its new version 4.7.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 mongoose. 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?
Good luck with your project :sparkles:
The new version differs by 29 commits .
chore: release 4.7.0
Merge pull request #4668 from rockmacaca/class-models
Merge branch 'master' of github.com:Automattic/mongoose
feat(document): support .set() on virtual subpaths
test(document): repro #4716
Merge pull request #4732 from kidlj/patch-1
fix(query): ensure correct casting when setting array element
test(query): repro #4274
fix doc mess
Merge pull request #4726 from Sebmaster/fix/stack-perf
Merge pull request #4725 from iMasoud/patch-1
feat(populate): support populate virtuals on nested schemas
test(populate): repro #4715
fix(document): dont set defaults on not-selected nested paths
test(document): repro #4707
There are 29 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap: