Skip to content

Conversation

@ximinez
Copy link
Owner

@ximinez ximinez commented Mar 18, 2025

High Level Overview of Change

Context of Change

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Performance (increase or change in throughput and/or latency)
  • Tests (you added tests for code that already exists, or your new feature included in this PR)
  • Documentation update
  • Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
  • Release

API Impact

  • Public API: New feature (new methods and/or new fields)
  • Public API: Breaking change (in general, breaking changes should only impact the next api_version)
  • libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
  • Peer protocol change (must be backward compatible or bump the peer protocol version)

This change is Reviewable

@ximinez ximinez force-pushed the unlwarning branch 3 times, most recently from 9e26188 to 0bbe361 Compare March 25, 2025 16:31
@ximinez ximinez force-pushed the unlwarning branch 3 times, most recently from 7fa5a06 to ed7531f Compare April 2, 2025 14:45
@ximinez ximinez force-pushed the unlwarning branch 5 times, most recently from 6c090e7 to 3729fcf Compare April 10, 2025 21:42
@ximinez ximinez added NoCI and removed NoCI labels Apr 11, 2025
@ximinez ximinez force-pushed the unlwarning branch 2 times, most recently from c9dd941 to 46f9de4 Compare April 28, 2025 18:46
@ximinez ximinez force-pushed the unlwarning branch 4 times, most recently from 16840b8 to 932aabf Compare July 18, 2025 22:37
@ximinez ximinez force-pushed the unlwarning branch 3 times, most recently from b0a8226 to e3aa70b Compare July 24, 2025 22:25
@ximinez ximinez force-pushed the unlwarning branch 4 times, most recently from 33df2ad to 583e304 Compare August 4, 2025 17:08
@ximinez ximinez force-pushed the unlwarning branch 4 times, most recently from 85f45af to 02f38a6 Compare November 4, 2025 23:30
@ximinez ximinez force-pushed the unlwarning branch 4 times, most recently from f2af94f to 61d7791 Compare November 10, 2025 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants