Updating Version for PhyloPickMe

[jrusinko]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115381

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

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

[jrusinko]

Thanks I corrected the version number.

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115424

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.1 -m "<description of version>" 4310b2bb83073857fa5f8f1d3c6ec0a0a1200b04
git push origin v1.0.1

[jrusinko]

I updated the release number to match. @JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/115424

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.1 -m "<description of version>" 4310b2bb83073857fa5f8f1d3c6ec0a0a1200b04
git push origin v1.0.1

[jrusinko]

I eliminated the using statistics line @JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/115424

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

[jrusinko]

I eliminated the using Sparse Arrays and using CSV lines @JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/115424

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

[jrusinko]

I eliminated the remaining standard libraries from the dep [compat] sections @JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Version 1.0.1 already exists