Miss Dada  🏳️‍⚧️

Sounds like you might have accidentally updated some other dependency at the same time? I'd be really shocked if updating to a patch version broke your app

The exception is coming from sprockets (Sprockets::Railtie::ManifestNeededError). I don't know whether Rails core considers that "part of" Rails, but I do.

It's maintained by Rails, but the dependency lives in your Gemfile, it's not something you get transitively from Rails itself. That error sounds like you pulled a major version bump of sprockets. Definitely not something that changed in Rails 5.1.3 -> 5.1.4

I don't know where Rails ends and Sprockets begins but I'm supposedly an expert in this technology. It's all Rails to me. Everything in app/assets/config is Rails; manifest.js is definitely Rails. That new replacement for sprockets that uses webpack is also Rails.

The only distinction I'm trying to make is "thing that is a dependency of the gem called `rails`" vs "thing that is in your gemfile which is also maintained by the rails org"

I literally don't understand what it would mean to version these two independently because sprockets is part of Rails.

It's been over a year since I left the Rails team so I'm probably not the best person to speak on the relationship between the two at this point.

Looks like Rails itself depends on Sprockets, and it took a major version upgrade between those two patch versions of Rails: https://github.com/rails/rails/compare/v5.2.3 ……v5.2.4.1#diff-e79a60dc6b85309ae70a6ea8261eaf95R448