[ruby] Update mongoid_rails_migrations 1.6.1 → 1.6.2 (patch) #592
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
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?
✳️ mongoid_rails_migrations (1.6.1 → 1.6.2) · Repo
Commits
See the full diff on Github. The new version differs by 2 commits:
Prepare 1.6.2 + test matrix updateAdd benchmark dependency (#63)✳️ mongoid (9.0.9 → 9.0.10) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 4 commits:
Bump version to 9.0.10 (#6099)MONGOID-5864 Rails metadata (#6094)MONGOID-5919 Restrict Criteria.from_hash method (#6083) (#6084)MONGOID-5899 Write conflict error when accessing embedded documents via [] operator after direct DB update (#6077)Release Notes
5.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
fix release infra (#365)Bump version to 5.2.0 (#364)RUBY-3651 Add support for jruby 10 (#353)only try to load candidate tasks if the submodule has been loaded (#363)Final (?) tweaks to release workflow (#362)Release Notes
2.22.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
an empty change to give us something to commit, so we can create a PR (#2965)Use correct repository for drivers-github-tools (#2963)Bump version to 2.22.0 (#2962)RUBY-3722 Properly handle SocketError (#2961)RUBY-3726 Use new toolchain (#2958)RUBY-3520 Sort option for updateOne and replaceOne (#2938)RUBY-3705 Skip tests that fail on latest (#2953)RUBY-3652 Remove serverless testing (#2942)Fix ArgumentError when a server is marked unknown (#2949)🆕 benchmark (added, 0.5.0)
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