qiskit-community · coruscating · Feb 8, 2024 · Jan 31, 2024 · Feb 1, 2024 · Feb 1, 2024
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -361,11 +361,21 @@ There are a few other build options available:
 
 ### Deprecation policy
 
-Qiskit Experiments is part of Qiskit and, therefore, the [Qiskit Deprecation
-Policy](https://github.com/Qiskit/qiskit/blob/main/DEPRECATION.md) fully applies here.
-Public-facing changes must come with a deprecation warning for at least three months or
-two version cycles before the old feature is removed. Deprecations can only happen on
-minor releases and not on patch releases.
+Qiskit Experiments's deprecation policy is based on Qiskit's [Deprecation
+Policy](https://github.com/Qiskit/qiskit/blob/45e42525224e9e1857300e7e5529273fe619c9e4/DEPRECATION.md)
+prior to its 1.0 release. Public-facing changes must come with a deprecation warning
+for at least three months or two version cycles before the old feature is removed.
+Deprecations can only happen on minor releases and not on patch releases.
+
+The timeline for deprecating an existing feature is as follows:
+
+* Minor release 1: An alternative path is provided. A `PendingDeprecationWarning` should be issued
+  when the old path is used, indicating to users how to switch to the new path and the release
+  in which the old path will no longer be available.
+* Minor release 2: The `PendingDeprecationWarning` becomes a `DeprecationWarning`. The release note
+  should indicate the feature has been deprecated and how to switch to the new path.
+* Minor release 3: The old feature is removed. The release note should indicate that the feature has
+  been removed and how to switch to the new path.
 
 #### Adding deprecation warnings
 
@@ -389,6 +399,15 @@ Utilities](https://docs.quantum.ibm.com/api/qiskit/utils) to add warnings:
       pass
 ```
 
+Note that these pre-deprecation and deprecation warnings will cause the CI to fail, but features up
+for deprecation should continue to be tested until their removal. All such expected warnings
+should be caught in tests:
+
+```python
+  with self.assertWarns(DeprecationWarning):
+      # Test something deprecated here
+```
+
 ### Development cycle
 
 The development cycle for Qiskit Experiments is all handled in the open using project

diff --git a/releasenotes/notes/0.5/experiment_data_fixes-f69c3569a8ba1342.yaml b/releasenotes/notes/0.5/experiment_data_fixes-f69c3569a8ba1342.yaml
@@ -8,19 +8,19 @@ features:
     :meth:`.ExperimentData.get_service_from_provider` enabling the automatic
     setting of the experiment database service via passing the provider.
   - |  
-    The `start_datetime`property of :class:`.ExperimentData`is now being
+    The ``start_datetime`` property of :class:`.ExperimentData` is now being
     set to the time the experiment data was created.
   - |
-    The `end_datetime` property of :class:`.ExperimentData` is now being
+    The ``end_datetime`` property of :class:`.ExperimentData` is now being
     set to the latest time a successful job terminated.
   - |
-    The `creation_datetime` and `updated_datetime` properties of :class:`.ExperimentData`
+    The ``creation_datetime`` and ``updated_datetime`` properties of :class:`.ExperimentData`
     are now being read from the server when saving the experiment.
   - |
-    All the datetime properties are stored in UTC and converted to local when using getters.
+    All the datetime properties are now stored in UTC and converted to local time when using getters.
   - |
     :meth:`.ExperimentData.save` can now raise exceptions when saving
-    fails, unless the `suppress_errors` flag is set (on by default)
+    fails, unless the ``suppress_errors`` flag is set (on by default).
 
 
 fixes:

diff --git a/...es/0.5_deprecations-4188ada026cb682b.yaml → ....6/0.5_deprecations-4188ada026cb682b.yaml b/...es/0.5_deprecations-4188ada026cb682b.yaml → ....6/0.5_deprecations-4188ada026cb682b.yaml
@@ -7,14 +7,11 @@ upgrade:
       allowed. Use ``physical_qubits`` keyword argument with a sequence type input.
     * The ``scipy_linear_lstsq`` and ``scipy_gaussian_lstsq`` fitters for the
       :class:`.StateTomographyAnalysis` and :class:`.ProcessTomographyAnalysis`
-      classes have been removed. Use the :func:`.linear_lstsq`, :func:`.cvxpy_linear_lstsq`,
-      or :func:`.cvxpy_gaussian_lstsq` fitters instead.
+      classes have been removed. Use the :func:`.cvxpy_linear_lstsq` 
+      and :func:`.cvxpy_gaussian_lstsq` fitters instead.
     * Curve fit solvers ``curve_fit()`` and ``multi_curve_fit()`` as well as fit functions
       ``bloch_oscillation_x()``, ``bloch_oscillation_y()``, and ``bloch_oscillation_z()`` have been
       removed. Use the LMFIT library instead.
-    * The scipy lstsq tomography fitters ``scipy_linear_lstsq`` and ``scipy_gaussian_lstsq`` have
-      been removed. Use the `linear_lstsq`, `cvxpy_linear_lstsq`, or `cvxpy_gaussian_lstsq` fitter
-      instead.
     * The ``flat_top_widths`` argument and experiment option of the
       :class:`.CrossResonanceHamiltonian` experiment and its subclass have been removed. Use
       ``durations`` instead.

diff --git a/releasenotes/notes/0.6/0.6_release-4d766733941ad57a.yaml b/releasenotes/notes/0.6/0.6_release-4d766733941ad57a.yaml
@@ -0,0 +1,9 @@
+---
+prelude: >
+    Qiskit Experiments 0.6 adds numerous features and improvements. It is compatible with Qiskit 1.0.
+    Notable changes include refactoring the analysis results to a Pandas dataframe, and refactoring
+    curve fit data into a new :class:`ScatterTable` container based on dataframes that is stored
+    by default as an artifact in :class:`ExperimentData` along with the summary of fit results.
+    New experiments include :class:`StarkP1Spectroscopy`, :class:`StarkRamseyXY`,
+    :class:`StarkRamseyXYScan`. The supported provider for running jobs on IBM backends has 
+    switched from ``qiskit-ibm-provider`` to ``qiskit-ibm-experiment``.
diff --git a/releasenotes/notes/0.6/access_figure_without_extension-5b7438c19e223d6b.yaml b/releasenotes/notes/0.6/access_figure_without_extension-5b7438c19e223d6b.yaml
@@ -0,0 +1,4 @@
+---
+feature:
+  - |
+    Figures in :class:`.ExperimentData` objects can now be accessed without the ``.svg`` extension.
diff --git a/...me-analysis-results-ec8863e826a70621.yaml → ...me-analysis-results-ec8863e826a70621.yaml b/...me-analysis-results-ec8863e826a70621.yaml → ...me-analysis-results-ec8863e826a70621.yaml
diff --git a/...ataframe-curve-data-a8905c450748b281.yaml → ...ataframe-curve-data-a8905c450748b281.yaml b/...ataframe-curve-data-a8905c450748b281.yaml → ...ataframe-curve-data-a8905c450748b281.yaml
diff --git a/...-with-unshared-axis-9f7bfe272353086b.yaml → ...-with-unshared-axis-9f7bfe272353086b.yaml b/...-with-unshared-axis-9f7bfe272353086b.yaml → ...-with-unshared-axis-9f7bfe272353086b.yaml
diff --git a/...st-equality-checker-dbe5762d2b6a967f.yaml → ...st-equality-checker-dbe5762d2b6a967f.yaml b/...st-equality-checker-dbe5762d2b6a967f.yaml → ...st-equality-checker-dbe5762d2b6a967f.yaml
diff --git a/releasenotes/notes/0.6/add_warning_analysis_without_data-bfc802da52591f13.yaml b/releasenotes/notes/0.6/add_warning_analysis_without_data-bfc802da52591f13.yaml
@@ -0,0 +1,4 @@
+---
+other:
+  - |
+    Display a warning when running an analysis on :class:`.ExperimentData` objects which do not contain data.
diff --git a/...ngle-representation-f5c40007416cf938.yaml → ...ngle-representation-f5c40007416cf938.yaml b/...ngle-representation-f5c40007416cf938.yaml → ...ngle-representation-f5c40007416cf938.yaml
@@ -18,7 +18,7 @@ other:
 upgrade:
   - |
     The representation of pulses in the :class:`.FixedFrequencyTransmon` library 
-    was changed from complex amplitude to (``amp``,``angle``) representation. All pulses
+    was changed from complex amplitude to (``amp``, ``angle``) representation. All pulses
     now include an ``angle`` parameter, and the default values of ``amp`` are set
     as type ``float`` instead of ``complex``.
   - |

diff --git a/...s/attach-other-cals-2f539e7799ceb6c8.yaml → ...6/attach-other-cals-2f539e7799ceb6c8.yaml b/...s/attach-other-cals-2f539e7799ceb6c8.yaml → ...6/attach-other-cals-2f539e7799ceb6c8.yaml
@@ -8,6 +8,6 @@ fixes:
   - |
     :class:`.qiskit_experiments.library.FineXDragCal` and 
     :class:`.qiskit_experiments.library.EFRoughXSXAmplitudeCal` were updated to
-    attach `"sx"` and `"x"` calibrations to their circuits, respectively.
-    Previously, they only attached the `"x"` and `"x12"` calibrations that they
+    attach ``"sx"`` and ``"x"`` calibrations to their circuits, respectively.
+    Previously, they only attached the ``"x"`` and ``"x12"`` calibrations that they
     were calibrating. See issue `#1158 <https://github.com/Qiskit-Extensions/qiskit-experiments/issues/1158>`_.
diff --git a/...rough-frequency-cal-8582610249e2327b.yaml → ...rough-frequency-cal-8582610249e2327b.yaml b/...rough-frequency-cal-8582610249e2327b.yaml → ...rough-frequency-cal-8582610249e2327b.yaml
diff --git a/...broadcasting-option-8a3b72bfc1df9668.yaml → ...broadcasting-option-8a3b72bfc1df9668.yaml b/...broadcasting-option-8a3b72bfc1df9668.yaml → ...broadcasting-option-8a3b72bfc1df9668.yaml
@@ -1,7 +1,7 @@
 ---
 features:
   - |
-    Added a `broadcast` option to the :class:`.CompositeAnalysis`. When `broadcast=True` is passed, 
+    Added a ``broadcast`` option to :class:`.CompositeAnalysis`. When ``broadcast=True`` is passed, 
     this option will be applied to child experiment analyses within the class. This means it will iterate
     through the child analysis classes and apply the given option to each of 
     them.
diff --git a/releasenotes/notes/0.6/bugfix_expdata_copy-2c73a21ad720858d.yaml b/releasenotes/notes/0.6/bugfix_expdata_copy-2c73a21ad720858d.yaml
@@ -0,0 +1,5 @@
+---
+fixes:
+  - |
+    The :meth:`.ExperimentData.copy` method under ExperimentData class now copies the provider. 
+
diff --git a/...als-no-coupling-map-5114ae9faa2f9e69.yaml → ...als-no-coupling-map-5114ae9faa2f9e69.yaml b/...als-no-coupling-map-5114ae9faa2f9e69.yaml → ...als-no-coupling-map-5114ae9faa2f9e69.yaml
diff --git a/...ircuit-count-method-a095bd74aaa1d2fb.yaml → ...ircuit-count-method-a095bd74aaa1d2fb.yaml b/...ircuit-count-method-a095bd74aaa1d2fb.yaml → ...ircuit-count-method-a095bd74aaa1d2fb.yaml
@@ -3,9 +3,7 @@ features:
   - |
     A new method :meth:`BaseExperiment.job_info` has been added that will
     output the number of jobs the experiment is expected to be split into
-    based on the provided backend.
-  - |
-    Refer to issue
-    `#1247 https://github.com/Qiskit-Extensions/qiskit-experiments/issues/1247`
+    based on the provided backend. Refer to issue
+    `#1247 <https://github.com/Qiskit-Extensions/qiskit-experiments/issues/1247>`_
     for more details.
 
diff --git a/...latten-result-false-026a89c09cc7a004.yaml → ...latten-result-false-026a89c09cc7a004.yaml b/...latten-result-false-026a89c09cc7a004.yaml → ...latten-result-false-026a89c09cc7a004.yaml
diff --git a/...es/device-component-c9ec9011c529425c.yaml → ....6/device-component-c9ec9011c529425c.yaml b/...es/device-component-c9ec9011c529425c.yaml → ....6/device-component-c9ec9011c529425c.yaml
diff --git a/releasenotes/notes/0.6/drop_python_3_7_support-0529a7122e94b004.yaml b/releasenotes/notes/0.6/drop_python_3_7_support-0529a7122e94b004.yaml
@@ -0,0 +1,4 @@
+---
+upgrade:
+  - |
+    Dropped support for Python 3.7 and added support for Python 3.12.
diff --git a/...ynamics-requirement-6109a8846c0f88c2.yaml → ...ynamics-requirement-6109a8846c0f88c2.yaml b/...ynamics-requirement-6109a8846c0f88c2.yaml → ...ynamics-requirement-6109a8846c0f88c2.yaml
diff --git a/...tes/exp-data-pickle-61511b6e926e3198.yaml → ...0.6/exp-data-pickle-61511b6e926e3198.yaml b/...tes/exp-data-pickle-61511b6e926e3198.yaml → ...0.6/exp-data-pickle-61511b6e926e3198.yaml
diff --git a/...a_metadata_save_fix-912b7180a28cfb03.yaml → ...a_metadata_save_fix-912b7180a28cfb03.yaml b/...a_metadata_save_fix-912b7180a28cfb03.yaml → ...a_metadata_save_fix-912b7180a28cfb03.yaml
diff --git a/releasenotes/notes/0.6/experiment_data_save_bugfixes-48fe62bf2bfe38b8.yaml b/releasenotes/notes/0.6/experiment_data_save_bugfixes-48fe62bf2bfe38b8.yaml
@@ -0,0 +1,6 @@
+---
+fixes:
+  - |
+    The :attr:`ExperimentData.auto_save` setter no longer saves sub-experiments twice.
+  - |
+    :meth:`ExperimentData.save` now handles correctly figures in sub-experiments when ``flatten_results=True``.
diff --git a/...ibrations-roundtrip-47f09bd9ff803479.yaml → ...ibrations-roundtrip-47f09bd9ff803479.yaml b/...ibrations-roundtrip-47f09bd9ff803479.yaml → ...ibrations-roundtrip-47f09bd9ff803479.yaml
diff --git a/...s/figure_return_SVG-4ad72fc8a3bee3cb.yaml → ...6/figure_return_SVG-4ad72fc8a3bee3cb.yaml b/...s/figure_return_SVG-4ad72fc8a3bee3cb.yaml → ...6/figure_return_SVG-4ad72fc8a3bee3cb.yaml
diff --git a/...x-curve-fit-weights-fb43d3aa5ed1c91c.yaml → ...x-curve-fit-weights-fb43d3aa5ed1c91c.yaml b/...x-curve-fit-weights-fb43d3aa5ed1c91c.yaml → ...x-curve-fit-weights-fb43d3aa5ed1c91c.yaml
diff --git a/.../fix-guess-rb-decay-f78e40a7d6d8dd67.yaml → .../fix-guess-rb-decay-f78e40a7d6d8dd67.yaml b/.../fix-guess-rb-decay-f78e40a7d6d8dd67.yaml → .../fix-guess-rb-decay-f78e40a7d6d8dd67.yaml
diff --git a/.../notes/half-angle-x-600debac368ce2c6.yaml → ...es/0.6/half-angle-x-600debac368ce2c6.yaml b/.../notes/half-angle-x-600debac368ce2c6.yaml → ...es/0.6/half-angle-x-600debac368ce2c6.yaml
diff --git a/...s/irb-circuit-order-619845a707519c44.yaml → ...6/irb-circuit-order-619845a707519c44.yaml b/...s/irb-circuit-order-619845a707519c44.yaml → ...6/irb-circuit-order-619845a707519c44.yaml
diff --git a/...otes/matplotlib-fix-58d938b49771cf17.yaml → .../0.6/matplotlib-fix-58d938b49771cf17.yaml b/...otes/matplotlib-fix-58d938b49771cf17.yaml → .../0.6/matplotlib-fix-58d938b49771cf17.yaml
diff --git a/...tes/notes/mod-stark-1f1afb538a94fe9a.yaml → ...notes/0.6/mod-stark-1f1afb538a94fe9a.yaml b/...tes/notes/mod-stark-1f1afb538a94fe9a.yaml → ...notes/0.6/mod-stark-1f1afb538a94fe9a.yaml
diff --git a/...ms_without_schedule-20555d98875a626b.yaml → ...ms_without_schedule-20555d98875a626b.yaml b/...ms_without_schedule-20555d98875a626b.yaml → ...ms_without_schedule-20555d98875a626b.yaml
@@ -1,8 +1,8 @@
 ---
 upgrade:
   - |
-    The variables `__drive_freq_parameter__` and `__readout_freq_parameter__`
-    have been removed from `Calibrations`. These variables were given special
+    The variables ``__drive_freq_parameter__`` and ``__readout_freq_parameter__``
+    have been removed from :class:`.Calibrations`. These variables were given special
     treatment which is inconsistent with the framework. To replace them a
     mechanism to define and add parameters without a schedule has been added to
     the basis gate library. This has the added benefit of making the API of 

diff --git a/...-clifford-synthesis-0e66c62fa3088fba.yaml → ...-clifford-synthesis-0e66c62fa3088fba.yaml b/...-clifford-synthesis-0e66c62fa3088fba.yaml → ...-clifford-synthesis-0e66c62fa3088fba.yaml
diff --git a/...s/qiskit-dependency-3f6b8d71cc4d2c31.yaml → ...6/qiskit-dependency-3f6b8d71cc4d2c31.yaml b/...s/qiskit-dependency-3f6b8d71cc4d2c31.yaml → ...6/qiskit-dependency-3f6b8d71cc4d2c31.yaml
@@ -5,11 +5,11 @@ upgrade:
     ``qiskit``. This change follows the move in upstream Qiskit to rename
     ``qiskit-terra`` to ``qiskit``. The minimum required version was increased
     from 0.24 for ``qiskit-terra`` to 0.44 for ``qiskit`` (equivalent to
-    `qiskit-terra`` 0.25). The maximum ``qiskit`` version was set to ``<1.0``
+    ``qiskit-terra`` 0.25). The maximum ``qiskit`` version was set to ``<1.0``
     in anticipation of breaking changes in Qiskit 1.0. Closer to the Qiskit 1.0
     release, a patch release of ``qiskit-experiments`` will remove this
     constraint and address any compatibility issues. For more information see
     the `Qiskit repository renaming plan
     <https://github.com/Qiskit/RFCs/blob/5793e78dc8e4d8d17f8ef7fad789c6c5ebd3a061/0011-repo-rename.md>`__
-    and the `Qiskit issue <https://github.com/Qiskit/qiskit/issues/11240>`__
-    for the renaming of the package.
+    and the `Qiskit 1.0 migration guide <https://docs.quantum.ibm.com/api/migration-guides/qiskit-1.0>`__
+    for information on renaming of the package.
diff --git a/...tes/notes/qvplotter-04efe280aaa9d555.yaml → ...notes/0.6/qvplotter-04efe280aaa9d555.yaml b/...tes/notes/qvplotter-04efe280aaa9d555.yaml → ...notes/0.6/qvplotter-04efe280aaa9d555.yaml
diff --git a/.../rabi-and-qv-bugfix-34636baee6651af1.yaml → .../rabi-and-qv-bugfix-34636baee6651af1.yaml b/.../rabi-and-qv-bugfix-34636baee6651af1.yaml → .../rabi-and-qv-bugfix-34636baee6651af1.yaml
@@ -2,9 +2,9 @@
 fixes:
   - |
     Resolved a serialization issue that affected Rabi experiments when running it through 
-    `qiskit-ibm-provider` using custom amplitudes provided as a numpy array.
+    the backend provider using custom amplitudes provided as a numpy array.
   - |
-    Resolved an issue that caused QV experiments to fail when executed via `qiskit-ibm-provider` using
+    Resolved an issue that caused QV experiments to fail when executed via the backend provider using
     Qiskit Terra for calculating ideal probabilities, instead of Aer.
   - |
     Resolved a serialization issue that affected DRAG experiments with integral beta values specified.
diff --git a/...rb-v2-none-coupling-fda2b22afdef507b.yaml → ...rb-v2-none-coupling-fda2b22afdef507b.yaml b/...rb-v2-none-coupling-fda2b22afdef507b.yaml → ...rb-v2-none-coupling-fda2b22afdef507b.yaml
diff --git a/...s/remove-tomo-reset-3f21ec4d0dacba91.yaml → ...6/remove-tomo-reset-3f21ec4d0dacba91.yaml b/...s/remove-tomo-reset-3f21ec4d0dacba91.yaml → ...6/remove-tomo-reset-3f21ec4d0dacba91.yaml
@@ -4,5 +4,5 @@ other:
     Removed the reset instruction from the beginning of tomography experiments.
     Since qubits are usually reset between circuits, this change should have no
     impact on tomography experiments, but it should allow backends that do not
-    provide a reset instruction to run tomography experiments. `#1250
-    <https://github.com/Qiskit-Extensions/qiskit-experiments/issues/881>`
+    provide a reset instruction to run tomography experiments. See `#1250
+    <https://github.com/Qiskit-Extensions/qiskit-experiments/issues/881>`_.
diff --git a/...requirements-extras-d5768794acbce467.yaml → ...requirements-extras-d5768794acbce467.yaml b/...requirements-extras-d5768794acbce467.yaml → ...requirements-extras-d5768794acbce467.yaml
diff --git a/...me-provider-support-5358b72ec0035419.yaml → ...me-provider-support-5358b72ec0035419.yaml b/...me-provider-support-5358b72ec0035419.yaml → ...me-provider-support-5358b72ec0035419.yaml
@@ -8,4 +8,7 @@ upgrade:
     With the impending deprecation of the ``qiskit-ibm-provider`` package, support for
     ``qiskit-ibm-provider`` is now deprecated and will be removed
     in the next release. Users should migrate to ``qiskit-ibm-runtime`` following the
-    `migration guide <https://docs.quantum.ibm.com/api/migration-guides/qiskit-runtime-from-provider>`.
+    `migration guide
+    <https://docs.quantum.ibm.com/api/migration-guides/qiskit-runtime-from-provider>`_.
+    ``qiskit-ibm-runtime`` is not listed as a dependency for compatibility reasons, but users
+    will need it to run experiments on IBM backends.
diff --git a/...notes/scale_options-745ee6f8e560043f.yaml → ...s/0.6/scale_options-745ee6f8e560043f.yaml b/...notes/scale_options-745ee6f8e560043f.yaml → ...s/0.6/scale_options-745ee6f8e560043f.yaml
diff --git a/...e-figure-generation-0864216f34d3486f.yaml → ...e-figure-generation-0864216f34d3486f.yaml b/...e-figure-generation-0864216f34d3486f.yaml → ...e-figure-generation-0864216f34d3486f.yaml
diff --git a/...hods-for-experiment-099074e59faffb49.yaml → ...hods-for-experiment-099074e59faffb49.yaml b/...hods-for-experiment-099074e59faffb49.yaml → ...hods-for-experiment-099074e59faffb49.yaml
diff --git a/.../update-figure-name-2db258c30ffe9912.yaml → .../update-figure-name-2db258c30ffe9912.yaml b/.../update-figure-name-2db258c30ffe9912.yaml → .../update-figure-name-2db258c30ffe9912.yaml
diff --git a/...ve-circuit-metadata-ec7d3c6b08781184.yaml → ...ve-circuit-metadata-ec7d3c6b08781184.yaml b/...ve-circuit-metadata-ec7d3c6b08781184.yaml → ...ve-circuit-metadata-ec7d3c6b08781184.yaml
diff --git a/releasenotes/notes/access_figure_without_extension-5b7438c19e223d6b.yaml b/releasenotes/notes/access_figure_without_extension-5b7438c19e223d6b.yaml
diff --git a/releasenotes/notes/add_warning_analysis_without_data-bfc802da52591f13.yaml b/releasenotes/notes/add_warning_analysis_without_data-bfc802da52591f13.yaml
diff --git a/releasenotes/notes/bugfix_expdata_copy-2c73a21ad720858d.yaml b/releasenotes/notes/bugfix_expdata_copy-2c73a21ad720858d.yaml
diff --git a/releasenotes/notes/drop_python_3_7_support-0529a7122e94b004.yaml b/releasenotes/notes/drop_python_3_7_support-0529a7122e94b004.yaml
diff --git a/releasenotes/notes/dump-terra-0_24-47c5d4fb92f1d97b.yaml b/releasenotes/notes/dump-terra-0_24-47c5d4fb92f1d97b.yaml
diff --git a/releasenotes/notes/experiment_data_save_bugfixes-48fe62bf2bfe38b8.yaml b/releasenotes/notes/experiment_data_save_bugfixes-48fe62bf2bfe38b8.yaml