Dangling sprocket manifest

[hennevogel]

If you're unlucky a dangling sprocket manifest can lead to the app being unable to serve assets. I just had this:

public/assets/.sprockets-manifest-f7b474132b17e060b63dc139c7c4c265.json
public/assets/.sprockets-manifest-f105d3d7fe2d4512811565989b31f6e2.json

f10... is the dangling one, f7b the one from the package. This lead the app to pick up f10... and to unserable assets.

Interestingly this manifest is dangling for a long time and before the package update it was this situation:

public/assets/.sprockets-manifest-d24617ec3c9c90a8b0a0f1de3d1624f5.json
public/assets/.sprockets-manifest-f105d3d7fe2d4512811565989b31f6e2.json

where it was not a problem. We had this in production once already and I just came across this on another instance in an update to 2.9 via packages.

[hennevogel]

I guess we should at least warn about dangling manifest files during the package installation/update...