Skip to content

Fix release notes after 0.4.22-related merging race #2871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 27, 2025
Merged

Fix release notes after 0.4.22-related merging race #2871

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/src/release_notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ Upcoming
- ``/v0/admin/users/offboard``:
Offboarding a user now also deletes the ledger API user in the participant node.

- Scan

- Added a ``record_time_match`` property to ``/v0/state/acs``, ``/v0/holdings/state`` and ``/v0/holdings/summary`` API requests.
Finds a snapshot that exactly matches the specified ``record_time`` if set to ``exact`` (default),
or finds the first snapshot at or before the specified ``record_time`` if set to ``at-or-before```.

0.4.22
------

Expand All @@ -34,12 +40,6 @@ Upcoming
is in catchup mode because there are too many markers.
Catchup mode only triggers when one or more of the SVs failed to convert the markers assigned to them for too long.

- Scan

- Added a ``record_time_match`` property to ``/v0/state/acs``, ``/v0/holdings/state`` and ``/v0/holdings/summary`` API requests.
Finds a snapshot that exactly matches the specified ``record_time`` if set to ``exact`` (default),
or finds the first snapshot at or before the specified ``record_time`` if set to ``at-or-before```.

0.4.21
------

Expand Down