Hi everyone, Last week I did these tasks: - *Add a default refactoring scope. *Now you can define a default environment through Refactorings Settings, this is useful when you are doing refactoring changes in Global environment. You can see the new behavior in this video: https://www.youtube.com/watch?v=NkxGP0P9klA . Check PR <https://github.com/pharo-project/pharo/pull/8999> to know the changes. - *Improve "Set up score command" *Check PR <https://github.com/pharo-project/pharo/pull/9039> to know the changes. -* Fix move method with empty protocol* (Move to package of defining class enh #8929 <https://github.com/pharo-project/pharo/issues/8929>) Check PR <https://github.com/pharo-project/pharo/pull/9040> to know the changes. - *Add preview rename class refactoring* Check PR <https://github.com/pharo-project/pharo/pull/9043> to know the changes. - I was fixing the issue: https://github.com/pharo-project/pharo/issues/6218 but I found two issues more, these are: RBNamespace doesn't support alias #9041 <https://github.com/pharo-project/pharo/issues/9041> , Inline method refactoring doesn't handle well, handling calls to super or overrides #9042 <https://github.com/pharo-project/pharo/issues/9042> Still in progress. - I was improving the creation of cascades to fix: Inline temp refactoring can create code with different behavior. #6056 <https://github.com/pharo-project/pharo/issues/6056>Still in progress. Tasks for this week: - Fix issue: RBNamespace doesn't support alias #9041 <https://github.com/pharo-project/pharo/issues/9041> - Fix issue: Inline method refactoring doesn't handle well, handling calls to super or overrides #9042 <https://github.com/pharo-project/pharo/issues/9042> - Fix issue: Inline senders refactoring does not correctly manage errors #6218 <https://github.com/pharo-project/pharo/issues/6218> - Finish to fix: Create cascade issue <https://github.com/pharo-project/pharo/issues/6056>. (Fix when the object is referenced after cascade block, fix the assignation when we have returns in called methods) - Fix issue: Introduce class Deprecation as Refactoring #9033 <https://github.com/pharo-project/pharo/issues/9033> <https://github.com/pharo-project/pharo/issues/8871> - Fix issue: move to component refactoring issue. <https://github.com/pharo-project/pharo/issues/8499> <https://github.com/pharo-project/pharo/issues/6218> Regards, Evelyn C.