New version of all of rails (7.0.8) produced dependency conflicts #97
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?
✳️ rails ( → 7.0.8) · Repo
Release Notes
7.0.8
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 33 commits:
Preparing for 7.0.8 releaseMerge pull request #44370 from mohits/patch-1Upgrade stringio to 3.0.8 to make sure guides CI passForce upgrade bundler to invalidate Bundler cache on CIRequire job used in this test fileWe expect queue adapters to be objects, no classesUpgrade gemfile to invalidate docker cacheMerge pull request #49121 from skipkayhil/hm-backport-49090Fix change_column not setting precision for sqliteMerge pull request #47865 from bensheldon/enqueue-error-messageMerge pull request #48095 from ippachi/triple-dot-range-unscopeMerge pull request #48657 from alpaca-tc/fix-association-with-has-many-inversingMerge pull request #48653 from alpaca-tc/fix-association-pretty-printMerge pull request #49122 from skipkayhil/hm-fix-stable-compat-testsFix Compatibility tests using `@internal_metadata`Merge pull request #49101 from xfifix/fix/sti_class_nameMerge pull request #49089 from emilyqiu1005/emilyqiu/add-kill-to-mysql-read-queriesMerge pull request #49053 from skipkayhil/hm-fix-48789Fix no _method input in form_for namespaced modelTry to build with sqlite3 1.6.3Merge pull request #49038 from skipkayhil/hm-fix-twz-to-sFix TimeWithZone#to_s being overriden with ENV setImprove guide for Customizing form builderFix `webdrivers` on `7-0-stable` branch for issue #48973. (#48977)Merge pull request #49011 from skipkayhil/hm-backport-48974Document how to remove to_s deprecation warnings when defaul format is changedFix 6.1 change_table setting datetime precisionDo not log internal options when running migrationsEnsure all migration versions use TableDefinitionFix some Migration versions not inheriting optionsMerge pull request #49006 from skipkayhil/hm-backport-48969Fix 6.1 change_column setting datetime precisionMerge tag 'v7.0.7.2' into 7-0-stableDepfu 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