New version: WaterLily v0.2.2

[JuliaRegistrator]

• Registering package: WaterLily
• Repository: https://github.com/weymouth/WaterLily.jl
• Created by: @weymouth
• Version: v0.2.2
• Commit: 971e50cb0f6bd53a224fd498f1e77e7756b1ae7c
• Reviewed by: @weymouth
• Reference: WaterLily-jl/WaterLily.jl@971e50c#commitcomment-54265798

[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:

• Does not meet sequential version number guideline: version 0.2.2 skips over 0.2.1

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.

---

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.

[giordano]

@weymouth did you skip version number on purpose?

[weymouth]

I did version 0.2.1 a few days ago not realizing that I needed to manually sync with the registry. I tried to rename this version 0.2.1, but register bot didn't like that either.

If it's ok to skip registering 0.2.1, let's just do that and move on.

[giordano]

I tried to rename this version 0.2.1, but register bot didn't like that either.

My educated guess is that that's because you're manually creating the git tags before successful registration, instead of letting TagBot create them for you after successful registration of a version. You should simply not create git tags manually.

[weymouth]

Will do from now on.