+1

No blockers or further PRs that should be included in this release
that I am aware of.

Thanks for RMing Ferenc!

Regards,
Gabor

On Wed, 21 Oct 2026 at 14:43, Ferenc Gerlits <[email protected]> wrote:
>
> Dear Community,
>
> I would like to initiate a discussion about the next release of MiNiFi C++.
> Since the 1.0.0 release in August, we have added several new features and many
> improvements, so I think it is time to create the next release, 1.1.0.
>
> I would be happy to take on RM duties for this release.
>
> ### New features ###
>
> * New AI processors based on sonos/tract: ClassifyImage, DetectObject and
>   DrawBoundingBox, written in Rust
> * New EncryptContentPGP and DecryptContentPGP processors, written in Rust
> * New, LMDB-based, flow file and content repository (experimental)
>
> ### Improvements ###
>
> * We now allow to explicitly unset optional properties, even if they have a
>   default value
> * Improved the Rust processor/controller service framework:
>   - Property characteristics (required/optional, validator etc) are now part
>     of the type system
>   - Easier to use error handling in Rust components
>   - Include Rust components in the Windows installer
> * Fixed an inaccuracy in the output of the CpuStat processor
> * Improved the PutOPCProcessor: it now creates a writable node
> * Fixed SSL handling in Kafka processors: always use system certs if no CA
>   cert location is given
> * Fixed a potential (but unlikely) out of memory issue in InputStream::read()
> * Fixed several memory leaks, including during flow file transfer/remove,
>   during failed flow updates, in OPC processors and in Python bindings
> * Extended Conan support to almost all dependencies, leading to much faster
>   build times
>
> ### Dependency upgrades ###
>
> * OpenSSL from 3.5.2 to 3.6.5
> * SOCI from 4.0.1 to 4.1.4
> * Abseil from 20260526.0 to 20260817.0
> * Grpc from 1.82.0 to 1.83.1
> * The minimum required Python version from 3.6 to 3.10
>
> Do you agree it is time for a new release? Are there any blockers or open PRs
> that we should definitely include in this release?
>
> Thanks,
>
> Ferenc Gerlits

Reply via email to