Revert pruning change in master378 and release another maintenance release #3975

As discussed, we pull out the pruning change, delete the github release and do a new one without it while the model compiler is in the process of being fixed. I would branch at current, to save the commit and reapply it as a cherry pick later on top of the new generated code.