register

[x66ccff]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Error in (Julia)Project.toml: UUID 3ba4a88b-5b67-4a96-bb04-131d22fbab27 refers to package 'ThArrays' in registry but Project.toml has 'THArrays'

[x66ccff]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Error in (Julia)Project.toml: Package 'THArrays' with UUID: e582e8a5-1f6a-498d-9b54-5d1908f43d65 not found in registry or stdlib

[x66ccff]

@JuliaRegistrator register(branch="THArrays-src")

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/123311

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.5.2 -m "<description of version>" 4a488b4e84e8c73f739779f51aedafa9f19b8948
git push origin v1.5.2

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

[x66ccff]

@JuliaRegistrator register(branch="THArrays-src")

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/123311

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

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

[x66ccff]

@JuliaRegistrator register(branch="THArrays-src")

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/123311

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.5.2 -m "<description of version>" ac29e812806f8be98148d6e24414ecec38e26e37
git push origin v1.5.2

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

[x66ccff]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/123311

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.5.2 -m "<description of version>" fbb24ac524f43a5f997efbb9362c90624cc6d290
git push origin v1.5.2

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

[x66ccff]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/123311

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.5.2 -m "<description of version>" 2744420e3680a760953f158e558ef7a5e3567fcb
git push origin v1.5.2

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