Not quite. This was merely a simple deployment mishap due to repurposing a flag which triggered deprecated code paths that should have been gutted out.