[gsavit]

I think it's a good point. Down the road it could be smart to explore an expanded idea of release defaults and the ability to assume away new questions about edge cases that show up in the flow. For now, we're committed to having Runway perform reliably and safely - which to start with means being explicit about options/changes that occur on a third party provider's side.

In general, my opinion (or Runway's!) isn't as important as factors on the customer side - types of apps, industries/verticals, team makeup - which are likely to make a difference in which checkboxes and options are considered important or not. It probably makes sense to include those factors when thinking about how we can further streamline everyone's release process in the future.

[estsauver]

I think that's a reasonable place to be. If you introduced a "Breaking build changes: New Checkbox Requirement" email most teams could just pipe that to pagerduty/opsgenie and have a reasonable way to ensure a working green deploy pipeline.

[gsavit]

Or Runway will take care of the piping! Integrations with PagerDuty et al are certainly on the roadmap :)