So far the names of generated IAM roles were taking the service name from serverless.yml and appending stack and stage etc. This seems to be changed in v1.65.0 to stackname instead of service name, so it is basically destroying the previously created role and creating the one with the new name. This is causing first deployments to fail, as deleting the role resource is not always possible (due to it having relations perhaps to other resources etc). But even if the roles are successfully deleted and new ones created, they might cause breaking changes in case old roles had some additional policies defined manually.
Could someone please advise, if this is expected behaviour or really an issue?