Register new version

[ivborissov]

The issue branch is dedicated to new versions registration. The workflow is as follows:

1. Set the version field in Project.json to your new desired version.
2. type `@JuliaRegistrator register()` in this branch or in the commit/branch, or using JuliaHub GUI.
3. Wait for TagBot to make release.
4. Done.

[JuliaRegistrator]

Error while trying to register: Version 0.4.12 already exists

[ivborissov]

register v0.4.13
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/87926

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.4.13 -m "<description of version>" e885233ec59f691a1450d63922a7f9a61322f514
git push origin v0.4.13

[ivborissov]

register v0.4.14
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/95813

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.4.14 -m "<description of version>" 4f4ffe4731ac5e1a5caaa9365bad97cce74261e5
git push origin v0.4.14

[ivborissov]

register v0.4.15
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/98067

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.4.15 -m "<description of version>" cda838254bbc300fde8c4790cf797b81514ce256
git push origin v0.4.15

[ivborissov]

register v0.4.15
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/98067

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.4.15 -m "<description of version>" 38ed4847c031682609d1df4d626a58a398b918fc
git push origin v0.4.15

[ivborissov]

register v0.4.15
@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/98067

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

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.4.15 -m "<description of version>" dc37eddbcc587574016d2004b3e8e5300bd743ab
git push origin v0.4.15