Rethinking auto build on publish

[carolynvs]

As I was adding another flag to build for --driver, I was again faced with what to do about the publish command. Right now when we detect that the current bundle is out of date, we automatically build it before publishing.

The detection of a stale bundle is useful (and can still be improved!) but I am kind of torn on the auto build part.

1. We have flags on build that we don't expose on publish. I do not want to duplicate them all on publish because I think it's confusing.
2. Because they are not on publish we can end up with auto builds with the wrong flags, because the user didn't intend to build and would have use explicit flags otherwise.

I am wondering if before v1 we should change from auto-build to only stopping publish when we detect a bundle is stale?

Is anyone relying on auto build today and have feedback on this?