Currently npm deploy and the sentr integration (sentry release adding) are done within one github action.
If npm addition succeeds but sentry integration fails there's no possibility to restart the sentry part.
So please consider a solution for this, i.e.
-) split npm addition and sentry loading into two seperate actiosn so that the failing action can be restarted
-) allow a restart of the deploy run by detecting ist that the npm release has already been added and either skip the npm deploy in this case or ignore this specific error
Currently npm deploy and the sentr integration (sentry release adding) are done within one github action.
If npm addition succeeds but sentry integration fails there's no possibility to restart the sentry part.
So please consider a solution for this, i.e.
-) split npm addition and sentry loading into two seperate actiosn so that the failing action can be restarted
-) allow a restart of the deploy run by detecting ist that the npm release has already been added and either skip the npm deploy in this case or ignore this specific error