Package Version Constraint Issue: Kentico.Xperience.Lucene incompatible with newer Xperience versions

[liamgold]

Summary
The Kentico.Xperience.Lucene package (v12.4.0) has an overly restrictive version constraint that prevents it from working with newer compatible versions of Kentico.Xperience.Admin and related packages.

Environment
• .NET Version: 9.0
• Kentico.Xperience.Lucene: 12.4.0
• Kentico.Xperience.Admin: 30.8.3 (desired)
• Kentico.Xperience.WebApp: 30.8.3

Problem Description
The Kentico.Xperience.Lucene.Admin package v12.4.0 requires an exact version of Kentico.Xperience.Admin = 30.6.0, but our solution uses v30.8.3. This creates a dependency resolution conflict:

Detected package version outside of dependency constraint: 
Kentico.Xperience.Admin 30.6.0 requires Kentico.Xperience.WebApp (= 30.6.0) 
but version Kentico.Xperience.WebApp 30.8.3 was resolved.

Expected Behaviour
The Lucene package should work with compatible newer versions of Xperience packages within the same major version (30.x.x series).

Suggested Fix
Update the package constraints in your Directory.Packages.props file to use version ranges instead of exact versions:

<PackageVersion Include="Kentico.Xperience.Admin" Version="[30.6.0,31.0.0)" />
<PackageVersion Include="Kentico.Xperience.WebApp" Version="[30.6.0,31.0.0)" />
<PackageVersion Include="Kentico.Xperience.Core" Version="[30.6.0,31.0.0)" />

[seangwright]

@liamgold if you look at the previous versions of the Directory.Packages.props file you can see we've always taken this dependency versioning approach.

• v30.6.0
• v30.5.1
• v30.0.1

Additionally, the Kentico Community Portal is using the latest version of the Lucene integration and is running on v30.8.1.

No one has reported issues with this dependency versioning approach so far... how are you configuring your package dependency management?

NuGet should manage using the latest version of the dependency specified across all your projects.

[liamgold]

In our Directory.Packages.props it has the following:

    <PackageVersion Include="Kentico.Xperience.Admin" Version="30.8.3" />
    <PackageVersion Include="Kentico.Xperience.Lucene" Version="12.4.0" />
    <PackageVersion Include="Kentico.Xperience.WebApp" Version="30.8.3" />

But the generated packages.lock.json uses what Kentico.Xperience.Lucene expects to use, see:

Other people may not have reported it as an issue, as it's just a warning when building rather than an error. Does the warning appear when building the Community Portal?

[liparova]

Hi @liamgold,

Thanks for the information — we’ll review it internally and get back to you shortly.

[seangwright]

@liamgold

The Kentico Community Portal has the same entry in its packages.lock.json.

There are 0 warnings when building it, however I'm using Central Package Management (CPM) which might resolve these kinds of issues automatically...

Or maybe you have different warnings/settings enabled in your Directory.Build.props (or Directory.Packages.props if using CPM)

[liamgold]

@seangwright I think that's because in Community Portal, you don't register the Lucene package at all in the Core project. You do everything in the Web project.

On my example project, I have the indexing, and the search service inside the Core project, meaning Lucene is installed in the Core and Web projects.

This makes the Core project then have the transitive dependency. On the Community Portal, if you install Lucene in the Core project too, you'll also get the same warning message: