Register package

[berquist]

Should we add 0.1.0 to the registry as-is, before any further development?

[berquist]

We agreed some time ago to not do so, but now we are ready to make a release. Probably pushing a tag will do it automatically?

[vcanogil]

We can use a register bot to register and release versions. I made a request for it to have access, you should receive it (hopefully) soon.

[berquist]

Ok, I added it.

[berquist]

What version should it be tagged as? 0.2.0? I really think the previous version was 0.1.0 proper even if not tagged.

[vcanogil]

Version was updated, so registering the package.
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/88006

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.2.0 -m "<description of version>" a14e987d0f0e158997efbafb96451221b21f2b13
git push origin v0.2.0

Also, note the warning: This looks like a new registration that registers version 0.2.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

[berquist]

Done in JuliaRegistries/General#88006 🎉