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.
name
version specification
new version
rails
>= 4.2
5.2.4
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.
Make ActiveSupport::Logger Fiber-safe. Fixes #36752.
Use Fiber.current.__id__ in ActiveSupport::Logger#local_level= in order
to make log level local to Ruby Fibers in addition to Threads.
Example:
logger = ActiveSupport::Logger.new(STDOUT)
logger.level = 1
p "Main is debug? #{logger.debug?}"
Fiber.new {
logger.local_level = 0
p "Thread is debug? #{logger.debug?}"
}.resume
p "Main is debug? #{logger.debug?}"
Before:
Main is debug? false
Thread is debug? true
Main is debug? true
After:
Main is debug? false
Thread is debug? true
Main is debug? false
Alexander Varnin
Active Model
Type cast falsy boolean symbols on boolean attribute as false.
Fix circular autosave: true causes invalid records to be saved.
Prior to the fix, when there was a circular series of autosave: true
associations, the callback for a has_many association was run while
another instance of the same callback on the same association hadn't
finished running. When control returned to the first instance of the
callback, the instance variable had changed, and subsequent associated
records weren't saved correctly. Specifically, the ID field for the belongs_to corresponding to the has_many was nil.
Assign all attributes before calling build to ensure the child record is visible in before_add and after_add callbacks for has_many :through associations.
Allow programmatic click events to trigger Rails UJS click handlers.
Programmatic click events (eg. ones generated by Rails.fire(link, "click")) don't specify a button. These events were being incorrectly stopped by code meant to ignore scroll wheel and right clicks introduced in #34573.
Sudara Williams
Action Pack
No changes.
Active Job
No changes.
Action Mailer
No changes.
Action Cable
No changes.
Active Storage
No changes.
Railties
Use original bundler environment variables during the process of generating a new rails project.
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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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 (>= 4.2 → 5.2.4) · Repo
Release Notes
5.2.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
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