I'm concerned that this is a breaking API change for extension authors. I'm assuming you checked all the callers in core code (since this PR has fixed up a caller to use `always()` instead of `done()`) - it's probably worth grepping through existing extensions to see if anyone else is calling it and expecting it to always resolve.