Bump mongodb and connect-mongo in /examples/basic-mongo #69
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.
Bumps mongodb to 5.7.0 and updates ancestor dependency connect-mongo. These dependencies need to be updated together.
Updates
mongodb
from 2.2.36 to 5.7.0Release notes
Sourced from mongodb's releases.
... (truncated)
Changelog
Sourced from mongodb's changelog.
... (truncated)
Commits
e16246d
chore(main): release 5.7.0 [skip-ci] (#3735)6a574cf
feat(NODE-5407): update bson to 5.4.0 (#3754)1f880ea
feat(NODE-5274): deprecate write concern options (#3752)0668cd8
fix(NODE-5374): do not apply cursor transform in Cursor.hasNext (#3746)ccc5e30
chore: update release 4x workflow name (#3751)865e658
fix(NODE-4977): load snappy lazily (#3726)dda4ec0
chore(NODE-5382): add 4.x release workflow (#3748)b97132e
fix(NODE-5102): listDatabases nameOnly setting is sent as NaN (#3742)a329748
refactor(NODE-5352): refactor AbstractOperation to use async (#3729)1d31888
ci(NODE-5361): use task groups for lambda (#3740)Maintainer changes
This version was pushed to npm by w-a-james, a new releaser for mongodb since your current version.
Updates
connect-mongo
from 2.0.3 to 5.0.0Changelog
Sourced from connect-mongo's changelog.
... (truncated)
Commits
33cda2b
fix: createIndex now do not need to supply writeConcernf462a25
fix: declare express-session as peer dependency3f5ad83
build: update github pipeline node versionae1bae1
chore: upgrade mongodb to 5.0.0 (#466)0920663
fix: require engines newer than node 12.9 (#445)f22d702
fix typos in README.md (#443)8908b1c
chore: bump version to 4.6.0 for release9847304
fix: callback was already called when code throw after set function (#440)2a2cd78
fix: move mongodb to peerDependencies (#435)3e27376
chore: bump version to 4.5.0 for releaseMaintainer changes
This version was pushed to npm by mingchuno, a new releaser for connect-mongo since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.