tensor4all / FastMPOContractions.jl

http://tensor4all.org/FastMPOContractions.jl/
MIT License
2 stars 0 forks source link

Register #4

Open shinaoka opened 4 months ago

shinaoka commented 4 months ago

@JuliaRegistrator register()

shinaoka commented 4 months ago

@JuliaRegistrator register()

JuliaRegistrator commented 4 months ago

Registration pull request created: JuliaRegistries/General/108273

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.2.2 -m "<description of version>" 29cc89958b8e4ae0e4ae5ad19a14c242cf54a2b8
git push origin v0.2.2

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

shinaoka commented 2 months ago

@JuliaRegistrator register()

JuliaRegistrator commented 2 months ago

Registration pull request created: JuliaRegistries/General/111225

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.2.2 -m "<description of version>" 4eed68b968cee172b59b6d65833f8a36e76d403f
git push origin v0.2.2

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

shinaoka commented 2 months ago

@JuliaRegistrator register()

JuliaRegistrator commented 2 months ago

Registration pull request created: JuliaRegistries/General/111482

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.2.3 -m "<description of version>" f782722e68993abec51725ec86af6950d2db0628
git push origin v0.2.3
shinaoka commented 2 weeks ago

@JuliaRegistrator register()

JuliaRegistrator commented 2 weeks ago

Registration pull request created: JuliaRegistries/General/115752

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.2.4 -m "<description of version>" 3e73a3ca0c8d73780eb3673ee59f5799b4c374ba
git push origin v0.2.4