Skip to content

Conversation

@rfscholte
Copy link
Contributor

@rfscholte rfscholte commented Dec 29, 2025

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@rfscholte rfscholte requested a review from mthmulders December 29, 2025 12:36
@rfscholte rfscholte merged commit 933e203 into master Jan 16, 2026
36 checks passed
@rfscholte rfscholte deleted the copy-deps branch January 16, 2026 16:56
@github-actions
Copy link

@rfscholte Please assign appropriate label to PR according to the type of change.

@github-actions github-actions bot added this to the 3.9.1 milestone Jan 16, 2026
@rfscholte rfscholte added the enhancement New feature or request label Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants