Package registration

[abraunst]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/79617

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 v1.0.0 -m "<description of version>" 1b9e221ecde39fd6723b210c84731d887033d246
git push origin v1.0.0

[abraunst]

@JuliaRegistrator register()

[JuliaRegistrator]

Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

[abraunst]

@JuliaRegistrator register()

[JuliaRegistrator]

Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

[abraunst]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/79623

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 v1.0.1 -m "<description of version>" 9879b01702b7e0b30bbacbf78348c1d4d7d200a5
git push origin v1.0.1

Also, note the warning: This looks like a new registration that registers version 1.0.1.
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.

[abraunst]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/125252

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 v1.0.3 -m "<description of version>" 24bc87c9203b28447f292d0c700018b2733184ca
git push origin v1.0.3

Also, note the warning: Version 1.0.3 skips over 1.0.2
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.

[abraunst]

@JuliaRegistrator register

add plot function, saner compose output

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/125252

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 v1.0.3 -m "<description of version>" 24bc87c9203b28447f292d0c700018b2733184ca
git push origin v1.0.3

Also, note the warning: Version 1.0.3 skips over 1.0.2
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.

[abraunst]

@JuliaRegistrator register

Release notes:

add plot function, saner compose output

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/125252

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 v1.0.3 -m "<description of version>" 24bc87c9203b28447f292d0c700018b2733184ca
git push origin v1.0.3

Also, note the warning: Version 1.0.3 skips over 1.0.2
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.

[abraunst]

@JuliaRegistrator register

Release notes:

add plot function, saner compose output

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/125254

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 v1.0.2 -m "<description of version>" 6a8991fe8d49f4b85ca7423d7b820d4c0914b191
git push origin v1.0.2