Adjust changelog after v2.6.0 release [skip ci]

CHANGES.rst

@@ -5,15 +5,27 @@ Changelog
 ------------------
 
 -   RAVEN will now specify which events were involved in the log message when
-    waiting for both GW and external sky maps. 
+    waiting for both GW and external sky maps.
 
-2.6.0 (unreleased)
-------------------
+2.6.0 "Griffin" (2025-01-17)
+----------------------------
+
+-   Enable SSM triggers and HasSSM source property
 
 -   Add `HIGH_PROFILE` label to SSM preferred event and also log reason for
     the label.
 
--   Enabled SSM triggers and HasSSM source property
+-   Don't download p-astro file for SSM alert canvas, since they are not required
+    by policy.
+
+-   Make p_astro and em_bright fields optional when sending update notice,
+    in order to support Burst and SSM alerts.
+
+-   Launch Fermi sky map requests only after ten minutes following the FINAL
+    notice. This more closely matches the availability of these sky maps and
+    prevents a significant number of failed calls, both retryable and those
+    that will fail due to no sky map being available (e.g. after a FLIGHT notice
+    with no FINAL notice) compared to the previous method.
 
 -   Rework determining the preferred external event using a keyfunc method
     similar to the superevent manager. This now prioritizes, in order, by
@@ -22,19 +34,26 @@ Changelog
     is prioritized, whether the space-time joint FAR is better, and whether
     the temporal joint FAR is better.
 
+-   Reorganize RAVEN workflow to generalize IGWN alert sky map handler and
+    kafka JSON to VOEvent converter to be used by multiple pipelines in the
+    future.
+
 -   Check whether MOC to assign proper filename when downloading external
     sky maps.
 
--   Launch Fermi sky map requests only after ten minutes following the FINAL
-    notice. This more closely matches the availability of these sky maps and
-    prevents a significant number of failed calls, both retryable and those
-    that will fail due to no sky map being available (e.g. after a FLIGHT notice
-    with no FINAL notice) compared to the previous method.
-
--   When creating combined sky maps, set any negative values in the flattened
-    external sky map to zero. This at least prevents erroneous results when
+-   Set negative values in the flattened external sky map to zero when creating
+    combined skymaps. This at least prevents erroneous results when
     we receive a sky map with these invalid values.
 
+-   Fix coincidence search so SubGRB events can only be found in coincidence
+    with CBC-like events (group is CBC or from CWB BBH search).
+
+-   Plot external sky maps with contour lines and annotate with contained
+    areas; remove central RA/dec position.
+
+-   Fixed the broken link at the combined sky map png which was pointing to a
+    wrong URL.
+
 -   Roll back ligo-followup-advocate to 1.2.9 until SSM triggers are planned
     in production.
 
@@ -48,12 +67,6 @@ Changelog
     round-robin fashion to workers in the high-concurrency general-purpose
     queue.
 
--   Fix coincidence search so SubGRB events can only be found in coincidence
-    with CBC-like events (group is CBC or from CWB BBH search).
-
--   Don't download p-astro file for SSM alert canvas, since they are not required
-    by policy.
-
 -   Automatically rotate and compress log files to avoid running out of disk
     space. Logs are rotated and compressed once per week and deleted after one
     month.
@@ -66,21 +79,14 @@ Changelog
     to reflect the fact that it is now responsible for additional maintenance
     tasks including log rotation.
 
--   Fixed the broken link at the combined sky map png which was pointing to a
-    wrong URL.
-
--   Plot external sky maps with contour lines and annotate with contained
-    areas; remove central RA/dec position.
-
 -   Drop support for Python 3.10, conforming to
     `SPEC 0 — Minimum Supported Dependencies <https://scientific-python.org/specs/spec-0000/>`_.
 
--   Reorganize RAVEN workflow to generalize IGWN alert sky map handler and
-    kafka JSON to VOEvent converter to be used by multiple pipelines in the
-    future.
+-   Pin bilby==2.2.3, bilby_pipe==1.4.2, gwpy < 3.0.10, ligo.em-bright==1.2.1,
+    ligo-followup-advocate==1.2.11 which have been reviewed/to-be reviewed by sccb.
+    Avoid testing with python3.12 in this release since ligo.em-bright pin does not
+    support python3.12.
 
--   Make p_astro and em_bright fields optional when sending update notice,
-    in order to support Burst and SSM alerts.
 
 2.5.2 "Cactus cat" (2024-11-18)
 -------------------------------