...

• When moving between patch (also known as incremental) version changes such as 0.1.0 to 0.1.1 users should be safe to assume a clean upgrade can occur with no risk of behavior changes other than bug fixes and no compatibility issues.
• When moving between minor changes such as 0.1.0 to 0.2.0 users can expect new behaviors and bug fixes but backward compatibility should be protected.
• When moving between major changes such as 0.x.y to 1.0.0 there may be backward compatibility impacting changes largely focused on removal of deprecated items.
  

Migrating to 1.23.0

• The resolution for CVE-2023-36542 included the addition of a new Access Policy component restriction named Reference Remote Resources applied to the following components:
  • CaptureChangeMySQL
  • ConsumeJMS
  • DBCPConnectionPool
  • ExtractGrok
  • GrokReader
  • HikariCPConnectionPool
  • HadoopDBCPConnectionPool
  • HBase_2_ClientService
  • JMSConnectionFactoryProvider
  • PublishJMS
  • ValidateJson
  • ValidateXml
• Deployments with fine-grained Access Policies may require assigning the Reference Remote Resources permission to users who should be able to configure applicable components
• The nifi-riemann-nar and nifi-hbase_1_1_2-client-service-nar are no longer included in the standard binary, but can be downloaded from Maven Central
• RethinkDB Processors are deprecated for removal in 2.0.0
• Upgrading dependencies from H2 Database Engine version 2.1 to 2.2 required internal automated migration

...