Issue for JuliaRegistrator

[giopaglia]

Issue for JuliaRegistrator.

[giopaglia]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Register Failed
@giopaglia, it looks like you are not a publicly listed member/owner in the parent organization (aclai-lab).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[giopaglia]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Register Failed
@giopaglia, it looks like you are not a publicly listed member/owner in the parent organization (aclai-lab).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[giopaglia]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Register Failed
@giopaglia, it looks like you are not a publicly listed member/owner in the parent organization (aclai-lab).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

[giopaglia]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/100127

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

[giopaglia]

@JuliaRegistrator register

Release notes:

This package contains the current state of SoleData.jl. The code in SoleData.jl, so far, had nothing to do with symbolic logics, and must, thus, be parted from the Sole.jl framework.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/100127

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

[giopaglia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/100843

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.0.2 -m "<description of version>" 438e43d9857dcd53701a917d9dac2b04f74664c1
git push origin v0.0.2

[giopaglia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/100868

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

[giopaglia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/108631

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

[giopaglia]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112127

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