Skip to content

Conversation

slawekjaranowski
Copy link
Member

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

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MCOMPILER-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean 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 clean 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.

@slawekjaranowski slawekjaranowski added the enhancement New feature or request label Feb 4, 2025
@slawekjaranowski slawekjaranowski merged commit 1954ef0 into apache:master Feb 4, 2025
26 checks passed
@slawekjaranowski slawekjaranowski deleted the dependabot-3.x branch February 4, 2025 20:59
@github-actions github-actions bot added this to the 4.0.0-beta-2 milestone Feb 4, 2025
@cdouillard
Copy link
Contributor

Hi @slawekjaranowski,

Since this PR was merged, I noticed that there were no PRs opened by dependabot on the main branch (dependency PRs were only open on the maven-compiler-plugin-3.x branch).

Yet there is, for example, a newer version available for mockito-core (5.15.2).

Maybe it's because of this PR: #174. Should it be reopened ?

@slawekjaranowski
Copy link
Member Author

Ok #174 reopened

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.

2 participants