We published metadata but the tarball never made it to the storage backend
We published the tarball but the Pursuit docs failed
We published the tarball and Pursuit docs but failed to add the package to the package sets
Of these three original concerns, only the second is really relevant.
We only publish the metadata if the tarball already made it to the storage backend, so you can already retry.
This PR!
The package sets are now independent of the publishing workflow, and if a package failed to be added there's the manual endpoint for re-attempting adding the package to the package sets.
We have some cases where a package fails to be added to Pursuit and, other than Pulp, there's currently no way to retry. In this PR I branch the publish workflow with the following process:
When you publish a package, we check whether the version has already been published. If not, then we go through the normal publishing workflow. If so, then we check whether the docs made it to Pursuit. If not, then we retry only the Pursuit publishing process (we don't repackage the tarball). If so, then we terminate publishing and provide you a link to your published documentation and post the metadata.
Fixes https://github.com/purescript/registry-dev/issues/343. In that issue we talked about three possible failure cases:
Of these three original concerns, only the second is really relevant.
We have some cases where a package fails to be added to Pursuit and, other than Pulp, there's currently no way to retry. In this PR I branch the
publishworkflow with the following process:When you publish a package, we check whether the version has already been published. If not, then we go through the normal publishing workflow. If so, then we check whether the docs made it to Pursuit. If not, then we retry only the Pursuit publishing process (we don't repackage the tarball). If so, then we terminate publishing and provide you a link to your published documentation and post the metadata.