Bump nifi-framework.version from 2.9.0 to 2.10.0 in /flow-diff#79
Conversation
dependabot
Bot
added
dependencies
Bumps `nifi-framework.version` from 2.9.0 to 2.10.0. Updates `org.apache.nifi:nifi-framework-core-api` from 2.9.0 to 2.10.0 Updates `org.apache.nifi.registry:nifi-registry-flow-diff` from 2.9.0 to 2.10.0 --- updated-dependencies: - dependency-name: org.apache.nifi:nifi-framework-core-api dependency-version: 2.10.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: org.apache.nifi.registry:nifi-registry-flow-diff dependency-version: 2.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
sfc-gh-pvillard
force-pushed
the
dependabot/maven/flow-diff/nifi-framework.version-2.10.0
branch
from
3d9c916 to
8aba87b
Compare
sfc-gh-dchaffelson
left a comment
sfc-gh-dchaffelson
left a comment
There was a problem hiding this comment.
Approving this bump. I checked the source change that rides along with it — dropping the Collections.emptySet() argument from the StandardFlowComparator constructor is the right adaptation: nifi-registry-flow-diff 2.10.0 removed that (external controller-service IDs) parameter, and since flow-diff always passed an empty set, there's no behavioural change. CI compiling green confirms the signature lines up.
Same merge-ordering caveat as the sibling PRs — this also touches FlowDiff.java, so a rebase for whichever of the batch lands last.
sfc-gh-dchaffelson
left a comment
sfc-gh-dchaffelson
left a comment
There was a problem hiding this comment.
Approving — bump + the accompanying StandardFlowComparator adaptation is behaviour-preserving (empty-set param removed in 2.10.0). Version split confirmed intentional.
sfc-gh-pvillard
deleted the
dependabot/maven/flow-diff/nifi-framework.version-2.10.0
branch
2 participants
Bumps
nifi-framework.versionfrom 2.9.0 to 2.10.0.Updates
org.apache.nifi:nifi-framework-core-apifrom 2.9.0 to 2.10.0Updates
org.apache.nifi.registry:nifi-registry-flow-difffrom 2.9.0 to 2.10.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)