docs: Backfill API-CHANGELOG.md for 3.1.1 through 3.3.0 - #8159
Conversation
Adds version sections for 3.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.1, and 3.3.0 (all released since the changelog was last updated for 3.1.0), and moves the corresponding entries out of Unreleased. Entries that have only shipped in 3.4.0 betas remain in Unreleased.
There was a problem hiding this comment.
🟢 Approval recommended
The change is documentation-only and the updated changelog structure and entry placement appear consistent and coherent with the stated release mapping.
Pull request overview
Backfills API-CHANGELOG.md with explicit release sections for 3.1.1 through 3.3.0, moving already-shipped API notes out of Unreleased while keeping develop-only items in Unreleased for the next release cycle.
Changes:
- Added new changelog sections for releases 3.3.0, 3.2.1, 3.1.3, 3.1.2, and 3.1.1 (including “bugfixes only” notes where applicable).
- Moved the
account_txdelegation-filter entry into the 3.3.0 section and adjusted 3.2.0 headings to be release-scoped. - Kept develop-only API notes (e.g., vault_info error improvements, input validation changes, ledger metadata additions) under
Unreleased.
File summaries
| File | Description |
|---|---|
| API-CHANGELOG.md | Reorganized and backfilled API changelog entries into the correct released versions while preserving unreleased items. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🟡 Changes recommended
The markdown heading levels make the new 3.4.0 content no longer part of ## Unreleased, leaving Unreleased effectively empty and breaking the intended document structure.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
API-CHANGELOG.md:35
- After nesting 3.4.0 under
Unreleased, theAdditions in 3.4.0/Bugfixes in 3.4.0headings should also be demoted one level to keep a consistent heading hierarchy.
### Additions in 3.4.0
- `ledger`: `nftoken_id`, `nftoken_ids`, and `offer_id` are now included in transaction metadata when transactions are expanded (`expand`, or admin-only `full`), matching the `tx`, `account_tx`, and `subscribe` (`transactions` stream) responses. ([#5706](https://github.com/XRPLF/rippled/pull/5706))
### Bugfixes in 3.4.0
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
| ## Unreleased | ||
|
|
||
| This section contains changes targeting a future version. | ||
|
|
||
| ### Additions | ||
| ## XRP Ledger server version 3.4.0 | ||
|
|
High Level Overview of Change
API-CHANGELOG.md hasn't been updated since the 3.1.0 release: everything shipped in 3.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.1, and 3.3.0 was still sitting under
Unreleased. This PR adds version sections for each of those releases and moves the entries that already shipped out ofUnreleased. Entries that have only landed ondevelop/3.4.0 betas (not yet in a final release) stay inUnreleased.Context of Change
Doc-only change, no code changes. Release mapping was determined by checking which tag first contains each entry's PR merge commit on
develop:Delegateobject in delegating and authorized account directories for proper deletion #6681, feat: Add Formats and Flags to server_definitions #6321, fix: Peer crawler port field type inconsistency #6318, fix: Minor RPC fixes #6730, fix: Make assorted RPC fixes #6529API Impact
libxrplchange (any change that may affectlibxrplor dependents oflibxrpl)