I am currently using Turborepo to run semantic-release-monorepo in all the packages and this error occurs unless I set the concurrency to 1.
As running the semantic-release commands sequentially does add a sizeable amount of time to our workflow, is there a chance that we can have increased support for concurrency ?
hadasgazit
commented
2 months ago
Greetings!
In relation to this #54 I am running into a locked ref issue.
" ! [remote rejected] @test-repo/pkg-b-v2.0.0 -> @test-repo/pkg-b-v2.0.0 (cannot lock ref 'refs/tags/@test-repo/pkg-b-v2.0.0': reference already exists)\n" +I am currently using Turborepo to run semantic-release-monorepo in all the packages and this error occurs unless I set the concurrency to 1.
As running the semantic-release commands sequentially does add a sizeable amount of time to our workflow, is there a chance that we can have increased support for concurrency ?