Upgrading Byte Buddy version to 1.12.6

[eyalkoren]

No description provided.

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-12-21T08:25:37.181+0000

• Duration: 70 min 28 sec

• Commit: 414c006

Test stats 🧪

Test	Results
Failed	0
Passed	2639
Skipped	21
Total	2660

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark test.

• run compatibility tests : Run the JDK Compatibility test.

• run integration tests : Run the APM-ITs.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

Thanks Eyal, I understand now the whole problem! Then I guess the <= should be the way to go as you said

[tobiasstadler]

Maybe the problem is that ignore does not check against the version in the pom but the version in "Maven Central"? So an update from < 1.9.16 to version 1.9.16 would be ignored, but not an update from 1.9.16 to something > 1.9.16?

[eyalkoren]

@tobiasstadler I don't think so based on https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#ignore

[tobiasstadler]

@eyalkoren yes, I also read that. But for me it is not really clear what the ignored version refers to. https://github.community/t/configure-dependabot-to-only-create-prs-for-minor-or-patch-updates/117656 suggests it is the new version not the version in the pom.

[tobiasstadler]

Maybe

 - package-ecosystem: "maven"
    directory: "/"
   ....
-  package-ecosystem: "maven"
    directory: "/integration-tests/runtime-attach/runtime-attach-app/"
    ...
    ignore:
      - dependency-name: "net.bytebuddy:byte-buddy-agent"

does work?