You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.2.0 -m "<description of version>" 0546ddbdd4443ffc1662523b5df2f10c71833197
git push origin v1.2.0
Also, note the warning: This looks like a new registration that registers version 1.2.0.
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.
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.2.0 -m "<description of version>" b46da807778610988be61501027edb36102fc30b
git push origin v1.2.0
Also, note the warning: This looks like a new registration that registers version 1.2.0.
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.
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.
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
To add release notes to this registration, just re-invoke JuliaRegistrator 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 v2.5.0 -m "<description of version>" fa5b924fb84736b47b8563361631cb6a58639640
git push origin v2.5.0
Also, note the warning: Version 2.5.0 skips over 2.4.0
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.
Activity
JuliaRegistrator commentedon May 13, 2022
Error while trying to register: "Tag with name
v1.1.5already exists and points to a different commit"ChrisRackauckas commentedon May 13, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon May 13, 2022
Registration pull request created: JuliaRegistries/General/60191
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:
Also, note the warning: This looks like a new registration that registers version 1.2.0.
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.
ChrisRackauckas commentedon May 13, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon May 13, 2022
Registration pull request updated: JuliaRegistries/General/60191
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:
Also, note the warning: This looks like a new registration that registers version 1.2.0.
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.
ChrisRackauckas commentedon Jul 20, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 20, 2022
Registration pull request created: JuliaRegistries/General/64646
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:
ChrisRackauckas commentedon Jul 20, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 20, 2022
Error while trying to register: "Tag with name
v1.2.1already exists and points to a different commit"ChrisRackauckas commentedon Jul 20, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 20, 2022
Registration pull request updated: JuliaRegistries/General/64646
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:
ChrisRackauckas commentedon Jul 20, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 20, 2022
Registration pull request updated: JuliaRegistries/General/64646
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:
ChrisRackauckas commentedon Jul 20, 2022
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 20, 2022
Registration pull request updated: JuliaRegistries/General/64646
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:
ChrisRackauckas commentedon Jul 11, 2024
@JuliaRegistrator register()
JuliaRegistrator commentedon Jul 11, 2024
Registration pull request created: JuliaRegistries/General/110848
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.
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:
ChrisRackauckas commentedon Feb 20, 2026
@JuliaRegistrator register()
JuliaRegistrator commentedon Feb 20, 2026
Registration pull request created: JuliaRegistries/General/148834
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
To add release notes to this registration, just re-invoke JuliaRegistrator 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:
ChrisRackauckas commentedon Apr 13, 2026
@JuliaRegistrator register()
JuliaRegistrator commentedon Apr 13, 2026
Registration pull request created: JuliaRegistries/General/152876
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
To add release notes to this registration, just re-invoke JuliaRegistrator 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:
ChrisRackauckas commentedon Apr 14, 2026
@JuliaRegistrator register()
JuliaRegistrator commentedon Apr 14, 2026
Registration pull request created: JuliaRegistries/General/152931
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
To add release notes to this registration, just re-invoke JuliaRegistrator 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:
ChrisRackauckas commentedon May 6, 2026
@JuliaRegistrator register()
JuliaRegistrator commentedon May 6, 2026
Registration pull request created: JuliaRegistries/General/154807
Recommendation: add release notes
Release notes help your users know what has changed in the new version. For breaking releases in particular, it's recommended to document what breaking changes were made (or point to where changes can be found, such as a changelog).
To add release notes, 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.
To add release notes to this registration, just re-invoke JuliaRegistrator 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:
Also, note the warning: Version 2.5.0 skips over 2.4.0
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.