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
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.
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.
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.
Activity
JuliaRegistrator commentedon Jul 24, 2023
Registration pull request created: JuliaRegistries/General/88153
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:
GiggleLiu commentedon Jul 24, 2023
@JuliaRegistrator register
JuliaRegistrator commentedon Jul 24, 2023
Registration pull request updated: JuliaRegistries/General/88153
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:
GiggleLiu commentedon Aug 14, 2023
@JuliaRegistrator register
JuliaRegistrator commentedon Aug 14, 2023
Registration pull request created: JuliaRegistries/General/89584
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:
GiggleLiu commentedon Aug 17, 2023
@JuliaRegistrator register
JuliaRegistrator commentedon Aug 17, 2023
Registration pull request created: JuliaRegistries/General/89836
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:
GiggleLiu commentedon Oct 2, 2023
@JuliaRegistrator register
JuliaRegistrator commentedon Oct 2, 2023
Registration pull request created: JuliaRegistries/General/92607
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:
mroavi commentedon Oct 2, 2023
@JuliaRegistrator register
JuliaRegistrator commentedon Oct 2, 2023
Registration pull request created: JuliaRegistries/General/92610
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:
GiggleLiu commentedon Jun 1, 2024
@JuliaRegistrator register
JuliaRegistrator commentedon Jun 1, 2024
Registration pull request created: JuliaRegistries/General/108065
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:
GiggleLiu commentedon Mar 25, 2025
@JuliaRegistrator register
Release note
JuliaRegistrator commentedon Mar 25, 2025
Registration pull request created: JuliaRegistries/General/127665
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:
GiggleLiu commentedon Mar 25, 2025
@JuliaRegistrator register
Release notes:
Breaking changes
JuliaRegistrator commentedon Mar 25, 2025
Registration pull request updated: JuliaRegistries/General/127665
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:
GiggleLiu commentedon May 12, 2025
@JuliaRegistrator register
Release notes:
Breaking changes
marskeyword ofTensorNetworkModelargument tounity_tensors_labelsto be more accurate.varsfield ofTensorNetworkModeltonvars. It seems not nessesary to name the variables.TensorNetworkModel.OMEinsum.The following APIs are added:
BeliefPropgation: create a belief propagation model instance, which can be derived from the UAI model.belief_propagate: perform message passing until convergence, returns a BPState object and extra info.random_tensor_train_uaiandrandom_matrix_product_uai: two UAI models for testing.JuliaRegistrator commentedon May 12, 2025
Registration pull request created: JuliaRegistries/General/130749
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:
JuliaRegistrator commentedon May 12, 2025
Registration pull request updated: JuliaRegistries/General/130749
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:
GiggleLiu commentedon Jul 2, 2025
@JuliaRegistrator register
JuliaRegistrator commentedon Jul 2, 2025
Registration pull request created: JuliaRegistries/General/134043
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:
GiggleLiu commentedon Jul 30, 2025
@JuliaRegistrator register
JuliaRegistrator commentedon Jul 30, 2025
Registration pull request created: JuliaRegistries/General/135618
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:
GiggleLiu commentedon Sep 9, 2025
@JuliaRegistrator register
JuliaRegistrator commentedon Sep 9, 2025
Registration pull request created: JuliaRegistries/General/138194
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: