Update mongoose 7.4.3 → 7.4.4 (patch) #76
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 (7.4.3 → 7.4.4) · Repo · Changelog
Release Notes
7.4.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
chore: release 7.4.4
Merge pull request #13739 from maybesmurf/master
Merge pull request #13747 from Idnan/master
Merge pull request #13759 from yury-ivaniutsenka/fix_change_stream
Merge pull request #13758 from Automattic/vkarpov15/mongoose-autopopulate-96
Merge pull request #13761 from Automattic/vkarpov15/gh-13725
fix(schema): support 'ascending', 'asc', 'descending', 'desc' for index direction
Merge branch 'master' of github.com:Automattic/mongoose
Merge branch '6.x'
chore: release 6.11.6
Merge pull request #13742 from Cooldogyum/master-1
fix(query+populate): add `refPath` to projection by default, unless explicitly excluded
fix(ChangeStream): add _bindEvents to addListener function
fix: missing typings for option includeResultMetadata
docs: link v7 migration guide
types: re-enhanced Document's methods
Merge pull request #13736 from Automattic/vkarpov15/gh-13607
Merge pull request #13733 from Automattic/vkarpov15/gh-12671-2
Merge pull request #13737 from Automattic/vkarpov15/gh-13710
Merge pull request #13741 from hasezoey/fixmd
Merge pull request #13734 from Automattic/vkarpov15/gh-13713
docs(discriminators): fix lint-md
types: enhanced Document's methods
types: export InferSchemaType
fix(cursor): bubble up resumeTokenChanged event from change streams
docs(middleware): clarify that query middleware applies to document by default
docs(migrating_to_6): add note about incompatible packages
Merge pull request #13726 from Automattic/vkarpov15/gh-13698
Merge pull request #13729 from hasezoey/fixmd
Merge pull request #13728 from Automattic/vkarpov15/gh-10435
docs(field-level-encryption): add missing languages for code-blocks
docs(source): add "field-level-encryption" to file-index
docs: add brief note on TypeScript generic usage for embedded discriminator `path()` calls
test: run transaction tests as part of replica set tests in CI
add sample test failure
style: fix lint
fix(connection): reset document state in between transaction retries
👉 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