@anizami - thanks for the contribution, and sorry for not identifying the issues sooner! After some local testing, I was able to find out what was causing the issue.

@mdboom - could you review the addition of the configuration item and let me know if this is correct?

Marked this as "affects release" due to the new config item if nothing else. I personally have no problem adding a new config option in a patch release, but if you disagree we can change the milestone to 1.1.

@embray - fine by me - thought just to check, I thought that 'affects-release' just meant that for bugs it was a problem with a released version not just dev? (didn't think we used that for non-bugs?)

Yes -- the new ConfigurationItem definition looks fine.

It's used for enhancements too--any user-visible change between releases.

You can read it equivalently to "This needs a changelog entry". that's one of the main things I use it to check.

Damn, I think I must have lost the configuration changes when rebasing...

Recovered thanks to Dropbox. Version control redundancy is good.

So's git reflog ;)

@embray - thanks, learned something today!