Hi, It will not be release issue, may be development team added some code which causing this issue. Refer below links for more details. https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_dml_non_mix_sobjects.htm http://stackoverflow.com/questions/2387475/how-to-avoid-mixed-dml-operation-error-in-salesforce-tests-that-create-users
There you cannot perform DML on what salesforce calls setup objects(User in this case) and non-setup object in the same context. There is a workaround that can be found here although
It will not be release issue, may be development team added some code which causing this issue.
Refer below links for more details.
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_dml_non_mix_sobjects.htm
http://stackoverflow.com/questions/2387475/how-to-avoid-mixed-dml-operation-error-in-salesforce-tests-that-create-users
Best Regards,
-Vivek
To fix this issue please try below :-
1) Future Method http://amitsalesforce.blogspot.in/search/label/Future%20Method
2) RunAs if you are using test class http://salesforce.stackexchange.com/questions/66046/mixed-dml-operation-dml-operation-on-setup-object-is-not-permitted-after-you-ha?rq=1
How to avoid MIXED_DML_OPERATION error in Salesforce tests that create Users
http://stackoverflow.com/questions/2387475/how-to-avoid-mixed-dml-operation-error-in-salesforce-tests-that-create-users
MIXED_DML_OPERATION error in Salesforce Apex Trigger when updating User objects
http://stackoverflow.com/questions/10136237/mixed-dml-operation-error-in-salesforce-apex-trigger-when-updating-user-objects
Please let us know if this will help you
Thanks
Amit Chaudhary