I'm finding that the actions conflict with each other since they are running at the same time so one might fail with a "The process cannot access the file '' because it is being used by another process" error.
What about serializing the build into a single workflow like this? https://github.com/Clinical-Support-Systems/CommunityAbp.Emailing.Postmark/actions/runs/8468721854

(the package versioning and deploy push to nuget of this template is MUCH easier to wrap the head around than what I did, though I like validating the package for best practice and the serialized single workflow)
I'm finding that the actions conflict with each other since they are running at the same time so one might fail with a "The process cannot access the file '' because it is being used by another process" error.
What about serializing the build into a single workflow like this? https://github.com/Clinical-Support-Systems/CommunityAbp.Emailing.Postmark/actions/runs/8468721854
(the package versioning and deploy push to nuget of this template is MUCH easier to wrap the head around than what I did, though I like validating the package for best practice and the serialized single workflow)