fix(options)!: Make not_planned the default close-issue-reason by david-allison · Pull Request #807 · actions/stale (original) (raw)

This seems like the sane default.

I realize it's technically a breaking change so may require a v6, but I doubt many users have workflow that changes base on the close-issue-reason attribute so blast radius is probably pretty small... could also argue that the previous value was simply "unset" and this isn't so much a breaking change as simply a "enhancement" of setting the value...