Release version 0.12.1

Git ref: 40fffb8d

Checklist

Basics

1. The CI pipeline succeeded, including all unit tests and code quality checks. (https://git.ligo.org/emfollow/gwcelery/pipelines/110523)
2. CHANGES.rst lists all significant changes since the last release. It is free from spelling and grammatical errors.
3. The latest Readthedocs documentation build passed and the latest docs are correctly rendered. Autodoc-generated API docs for tasks are shown.
4. If there is milestone for this release, then the list of issues and merge requests that have been addressed is accurate. Any unaddressed issues and merge requests have been moved to another milestone.

Playground deployment

4. Sentry does not show any new unresolved issues on playground that indicate new bugs or regressions.
5. The playground deployment has run for at least 10 minutes.
6. The Flower monitor is reachable and shows no unexpected task failures.
7. The Flask dashboard is reachable.
8. The playground deployment is connected to LVAlert.
9. The playground deployment is connected to GCN (receiving only). GCN's playground instance is down.

Mock events

10. The playground deployment has produced an MDC superevent.
11. The MDC superevent has the following annotations.
    • bayestar.multiorder.fits
    • bayestar.fits.gz
    • bayestar.png
    • bayestar.volume.png
    • bayestar.html
    • p_astro.json
    • p_astro.png
    • em_bright.json
    • em_bright.png
    • LALInference.posterior_samples.hdf5
    • LALInference.multiorder.fits
    • LALInference.fits.gz
    • LALInference.png
    • LALInference.volume.png
    • LALInference.html
12. The MDC superevent has the following labels.
    • EMBRIGHT_READY
    • [ ] GCN_PRELIM_SENT GCN's playground instance is down.
    • PASTRO_READY
    • PE_READY
    • SKYMAP_READY
13. [ ] The MDC superevent has two automatic preliminary VOEvent if GCN_PRELIM_SENT is applied. GCN's playground instance is down.
14. Issuing a manual preliminary alert from the Flask dashboard sends another preliminary alert.
    • The alert is sent successfully if ADVOK or an ADVNO label is not applied this time.
    • Alternatively, a preliminary alert is blocked due to presence of ADVOK or ADVNO.
15. The MDC superevent has either an ADVOK or an ADVNO label.
16. Issuing an ADVOK signoff through GraceDB results in an initial VOEvent.
17. Issuing an ADVNO signoff through GraceDB results in a retraction VOEvent.
18. Requesting an update alert through the Flask dashboard results in an update VOEvent.