New package: JavisNB v0.1.0

[JuliaRegistrator]

• Registering package: JavisNB
• Repository: https://github.com/JuliaAnimators/JavisNB.jl
• Created by: @Wikunia
• Version: v0.1.0
• Commit: 9aa6c6c90efac517c172e8207a225cc8fcc3265b
• Reviewed by: @Wikunia
• Reference: Releases JuliaAnimators/JavisNB.jl#10 (comment)
• Description: Notebook integrations for Javis.jl

[github-actions]

Your new package 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:

• Package name similar to 1 existing package.
  1. Similar to Javis. Damerau-Levenshtein distance 2 is at or below cutoff of 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, simple 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.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

---

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.

[gpucce]

Hi,

The reason JavisNB can't be installed or loaded is that it depends on a version of Javis that is yet to be released. This is the case because most the functionality of JavisNB are exported from Javis itself and it will be the package holding all the notebooks functionalities. However, doing this required some changes in Javis that will be available in the next release, the one JavisNB depends on.

That said, we though it was not the case to relax the compat because otherwise there would be a downloadable release of JavisNB that does not work. At the same time if we release Javis 0.8 right now there would be no way to use it within a notebook until JavisNB is itself released.

What is the best way to go?

Thanks you in advance!

Taggin others for reference
@Wikunia

[giordano]

Registering a package which depends on an unregistered version makes the registry inconsistent. That's not something we want to do

[Wikunia]

Okay then I would suggest we Release v0.8 of Javis and would be great if we would not need to wait 3days for this to be released such that they can immediately work together.
I'm totally fine with waiting three days now though and then release Javis v0.8.

[Wikunia]

Would be great if this could be merged soon such that Javis users can use notebooks with the latest Javis version. Thanks in advance. Let us (@gpucce and me) know if there is anything else we should do. Thanks in advance!

[Wikunia]

Thank you ☺️