fix: process does not terminate after creating a commit with the --re… - #974
fix: process does not terminate after creating a commit with the --re…#974coffe0wl wants to merge 2 commits into
Conversation
Sorry, something went wrong.
|
Hi, @jimthedev Is there any chance this fix will land? The --retry workflow doesn't seem to work without it. |
Sorry, something went wrong.
|
I am also experiencing --retry not working; is that because of this missing PR? It just hangs forever: |
Sorry, something went wrong.
yes
it hangs, you can press ctrl-c to stop the execution, and the commit will be committed. |
Sorry, something went wrong.
|
The CI job for this is long gone so I can't re-run. I am creating an alternative branch and will give it a try. |
Sorry, something went wrong.
|
🎉 This issue has been resolved in version 4.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sorry, something went wrong.
|
Let me know if there are other PRs you want prioritized. I can't promise I will get to them all, but we can try :D Also if you can let me know if this worked, I'd appreciate it. |
Sorry, something went wrong.
Problem:
The problem appears when the user creates a commit with the --retry option.
When creating a commit without this parameter, the process will be completed by a function that acts as a prompt, since without this parameter this function is not executed because the data is taken from the cache, the process was not completed.
Therefore, a line was added that terminates the process in case there was no error.