Update mongoose 8.5.1 → 8.5.2 (patch) #111
Merged
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mongoose (8.5.1 → 8.5.2) · Repo · Changelog
Release Notes
8.5.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
chore: release 8.5.2
Merge pull request #14769 from Automattic/vkarpov15/gh-6691-2
fix: allow setting document array default to `null`
Merge pull request #14762 from Automattic/vkarpov15/perf-clone-primitives
Merge pull request #14760 from Automattic/vkarpov15/gh-14759
Merge pull request #14756 from Automattic/vkarpov15/gh-14748
address code review comments and fix a couple of other spots where we get _id through getter
perf(clone): avoid further unnecessary checks if cloning a primitive value
Merge pull request #14758 from abdelrahman-elkady/patch-1
Merge pull request #14755 from Automattic/vkarpov15/gh-14751
types: improve return value for Types.Subdocument.cast()
Update test/types/schema.test.ts
fix(model+document): avoid depopulating manually populated doc as getter value
docs: fix a wrong example in v6 migration guide
types: allow calling `SchemaType.cast()` without `parent` and `init` parameters
fix: better edge case handling
fix(query): handle casting $switch in $expr
Merge pull request #14752 from adf0nt3s/bsager/fix-incorrect-shardkey-set
Merge pull request #14746 from hasezoey/mms10
Correct shardkey access in buildBulkWriteOps
chore(deps-dev): bump mongodb-memory-server from 9.4.0 to 10.0.0
chore(workflows/tsd): update node-version to 16 for types test
chore(workflows/test): update mongodb versions to their latest patch
Merge pull request #14744 from Automattic/vkarpov15/gh-14736
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands