Skip to content

Conversation

@veprbl
Copy link
Member

@veprbl veprbl commented Aug 14, 2025

We should be fine now, with new RNG service. Even if we not, we should have an issue/PR associated with every TODO.

Briefly, what does this PR introduce?

What kind of change does this PR introduce?

  • Bug fix (issue #__)
  • New feature (issue #__)
  • Documentation update
  • Other: __

Please check if this PR fulfills the following:

  • Tests for the changes have been added
  • Documentation has been added / updated
  • Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No

Does this PR change default behavior?

No

We should be fine now, with new RNG service. Even if we not, we should have an issue/PR associated with every TODO.
@wdconinc
Copy link
Contributor

wdconinc commented Aug 14, 2025

OT, slightly. I've been wanting to make it clearer what the ST_MT comparison is. I don't want people to look at that and say "oh, look, this PR doesn't introduce any differences."

wdconinc
wdconinc previously approved these changes Aug 14, 2025
@veprbl veprbl added this pull request to the merge queue Aug 15, 2025
Merged via the queue into main with commit 742c63a Aug 15, 2025
119 checks passed
@veprbl veprbl deleted the pr/MT_check branch August 15, 2025 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants