New version: NeuroTreeModels v1.1.2

[JuliaRegistrator]

• Registering package: NeuroTreeModels
• Repository: https://github.com/Evovest/NeuroTreeModels.jl
• Created by: @jeremiedb
• Version: v1.1.2
• Commit: 1539a5f8fa4634e23d433995522b279b19df14fe
• Reviewed by: @jeremiedb
• Reference: Evovest/NeuroTreeModels.jl@1539a5f#commitcomment-141135903
• Description: Differentiable tree-based models for tabular data

[github-actions]

Your new version pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

• A patch release is not allowed to narrow the supported ranges of Julia versions. The ranges have changed from Pkg.Versions.VersionRange[VersionRange("1.6.0-1")] (in 1.1.1) to Pkg.Versions.VersionRange[VersionRange("1.9.0-1")] (in 1.1.2).

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simply retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

---

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

[jeremiedb]

PR to close in favor of #105209

I retriggered registrator in the comment of the new commit that fixed the issue (bump to minor release). Should it have been made into the original commit message to avoid the opening of a new PR?