Skip to content

MINIFICPP-2813 Upgrade thirdparty libraries part 1#2174

Draft
lordgamez wants to merge 22 commits into
apache:mainfrom
lordgamez:MINIFICPP-2813_part_1
Draft

MINIFICPP-2813 Upgrade thirdparty libraries part 1#2174
lordgamez wants to merge 22 commits into
apache:mainfrom
lordgamez:MINIFICPP-2813_part_1

Conversation

@lordgamez
Copy link
Copy Markdown
Contributor

@lordgamez lordgamez commented May 14, 2026

This is the first part of upgrading the thirdparty libraries before releasing MiNiFi C++ 1.0:

  • Upgrade jsoncons lib to v1.7.0
  • Upgrade paho.mqtt.c library to v1.3.16
  • Upgrade grpc to v1.80.0
  • Upgrade benchmark lib to v1.9.5
  • Upgrade ArgParse lib to v3.2
  • Upgrade librdkafka to v2.14.1
  • Upgrade Absiel lib to version 20260107.1
  • Upgrade RpMalloc to v1.4.5
  • Upgrade liblzma to v5.8.3
  • Upgrade lz4 library to v1.10.0
  • Upgrade zlib to v1.3.2
  • Upgrade Lua to version 5.4.8
  • Upgrade magic_enum lib to v0.9.8
  • Upgrade zstd to v1.5.7
  • Upgrade libssh2 to version 1.11.1
  • Upgrade json-schema-validator to v2.4.0 and nlohmann_json to v3.12.0
  • Upgrade kubernetes lib to v0.14.0 and libwebsockets lib to v4.5.8
  • Upgrade mimalloc to version 3.3.2
  • Upgrade yaml-cpp to version 0.9.0
  • Upgrade MbedTLS to v3.6.6 and Open62541 to v1.5.4
  • Upgrade alpine docker base image to version 3.22.4
  • Upgrade gsl-lite to version 1.1.0

Note: Each upgrade is done in a separate commit, so it is recommended to review the PR commit by commit for easier understanding.


Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically main)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file?
  • If applicable, have you updated the NOTICE file?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

@lordgamez lordgamez marked this pull request as draft May 14, 2026 10:01
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.

1 participant