bin/sf in salesforce-deploy-tool-0.9.3 vs bin/sf in salesforce-deploy-tool-0.9.4

@@ -152,13 +152,13 @@
     # Push the code without destructiveChanges.xml. This step is allways necessary
     # even when it is a destructive change. This is because if a class is referencing
     # a field to be deleted, then we first need to push the class to remove that 
     # reference and only then SF will allow us to remove the field on the second
     # push
-    sfdt.build_number = options.build_number if not options.build_number.nil?
-    sfdt.set_version
     begin
+      sfdt.build_number = options.build_number if not options.build_number.nil?
+      sfdt.set_version
       sfdt.push
     ensure
       sfdt.clean_version
     end
 
@@ -187,9 +187,11 @@
       dc_gen.generate_destructive_changes
       $stdout = stdout_tmp
     
       # Destructive push
       begin
+        sfdt.build_number = options.build_number if not options.build_number.nil?
+        sfdt.set_version
         sfdt.push
       ensure
         sfdt.clean_version
       end
     end