[ruby - main] New version of ransack (4.1.0) produced dependency conflicts #2604
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
All good now, closing. |
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.
We've tested your project with an updated dependency and got errors while installing the dependencies.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, the build failed while installing dependencies. This means that while the new version is within the specified range, a version conflict between two or more packages will prohibit this version from being installed.
As this breaks fresh installs of your package, we've left this pull request open for you to investigate.
What changed?
✳️ ransack (>= 1.8, < 5.0 → 4.1.0) · Repo · Changelog
Release Notes
4.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 26 commits:
Release 4.1.0 (#1455)Fix wrong table aliases in Rails 6.1 (#1447)Merge pull request #1454 from activerecord-hackery/rubocopExclude docs for RuboCop runRuboCop can now target Ruby 3Merge pull request #1453 from activerecord-hackery/misc-bumpsCI on Ubuntu 22.04Bump Rubies to latest patch levelsDon't mention Ruby compatibility in contribution instructions (#1452)Test with Ruby 3.2 as well (#1451)Updates sorting example (#1442)Bump dns-packet from 5.3.1 to 5.6.1 in /docs (#1450)Drop Ruby 2.7 support (#1449)Bump postcss from 8.4.14 to 8.4.31 in /docs (#1443)Merge pull request #1448 from activerecord-hackery/more-rails-71See if bug report templates work on Rails 7.1Let main Gemfile use Rails 7.1 by defaultBump @babel/traverse from 7.18.2 to 7.23.2 in /docs (#1446)Merge pull request #1439 from yuki24/rails-7-1Test against rails v7.1.0Fix builds for Rails 7.1.0Add namespaced example (#1422)Bump semver from 5.7.1 to 5.7.2 in /docs (#1431)[skip ci] Update blog post link (#1425)Bump webpack from 5.74.0 to 5.76.1 in /docs (#1412)Bump @sideway/formula from 3.0.0 to 3.0.1 in /docs (#1417)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