I've got multiple lambda functions that need to be associated with each other for an AWS Simple Work Flow. For CI I've it set up to update the versions of each

I've got multiple lambda functions that need to be associated with each other for an AWS Simple Work Flow. For CI I've it set up to update the versions of each lambda in a project repo. During packaging and deployment I inject the configuration of the git sha so that the next lambda function in the workflow that is called is consistent. Once the new workflow lambda call-chain is in place I can test / validate the new environment and then roll over the lambda that starts the workflow. What I need to make sure of is that all the lambda functions / roles are updated before the starter so that the workflow doesn't break, as there could be breaking changes between commits. A suggestion would be to create a repo per lambda function, but that becomes a hassle to manage after a few dozen, and just throws in even more work on ensuring the order of updates necessary. It is easier to flow between commit versions.