register

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Error in (Julia)Project.toml: Package 'FastMPOContractions' with UUID: f6e391d2-8ffa-4d7a-98cd-7e70024481ca not found in registry or stdlib

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111484

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.3.7 -m "<description of version>" 0103130ee3060c1841fab6adb82c1d61f4d12a6a
git push origin v0.3.7

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

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112576

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

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/117853

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.3.9 -m "<description of version>" 5e44c75ff0f5b69c74d6e84557ff33d5dbfa613e
git push origin v0.3.9

[terasakisatoshi]

@JuliaRegistrator register

[JuliaRegistrator]

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

[terasakisatoshi]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/119550

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.0 -m "<description of version>" 550c4413adf36883560f6fc350196e677f743257
git push origin v0.4.0

[JuliaRegistrator]

Error while trying to register: Version 0.4.0 already exists

[JuliaRegistrator]

Error while trying to register: Version 0.4.0 already exists

[terasakisatoshi]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Error in (Julia)Project.toml: Package 'ProjMPSs' with UUID: 3cac4759-b6c4-45be-a543-65afe6a1360a not found in registry or stdlib

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: Error in (Julia)Project.toml: Package 'PartitionedMPSs' with UUID: 17ce1de9-5131-45e3-8a48-9723b6e2dc23 not found in registry or stdlib

[shinaoka]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/121643

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.2 -m "<description of version>" d8c5c65cb8aba3662e0169e978391ad261c6ab70
git push origin v0.4.2

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