Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New version: CategoryData v0.3.0 #124050

Merged
merged 1 commit into from
Jan 30, 2025
Merged

New version: CategoryData v0.3.0 #124050

merged 1 commit into from
Jan 30, 2025

Conversation

JuliaRegistrator
Copy link
Contributor 

This version ensures compatibility with TensorKit v0.13+ by dropping the TensorKit compatibility and instead relying only on the new TensorKitSectors.jl.
While this package should otherwise behave the same, the breaking changes are that the older versions of TensorKit will necessarily no longer be supported.

@JuliaRegistrator
New version: CategoryData v0.3.0
dfb6e11 
UUID: 8fccf25a-f50e-468c-8fba-3cb130506274
Repo: https://github.com/lkdvos/CategoryData.jl.git
Tree: 11498ec6b7c18e56ebd8519680f42b2e5ab96fdf

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
JuliaRegistrator referenced this pull request in lkdvos/CategoryData.jl Jan 30, 2025
@borisdevos @lkdvos
CategoryData compatibility with TensorKitSectors (#21)
88542ff 
* change TensorKit to TensorKitSectors everywhere

* replace TensorKit -> TensorKitSectors in tests as well

* change TensorKit dep/compat to TensorKitSectors dep/compat

* rename version to 0.3

* change compat of SparseArrayKit

* change compat of SparseArrayKit

* bump version to v0.3.0

* missed some TensorKit replacements in tests

* add TensorOperations dependency for @tensor

* more TensorKit replacements...

* change julia compat to 1.10

* fix typo Rsymbol

* move TensorOperations dependency to test dependency

* format

* Update CI

---------

Co-authored-by: Lukas Devos <ldevos98@gmail.com>
@github-actions GitHub Actions
Copy link
Contributor

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round (~20 minutes).

2. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

@JuliaTagBot JuliaTagBot merged commit 02353a6 into master Jan 30, 2025
20 checks passed
@JuliaTagBot JuliaTagBot deleted the registrator-categorydata-8fccf25a-v0.3.0-7c1ac3b200 branch January 30, 2025 22:21
@JuliaTagBot JuliaTagBot mentioned this pull request Jan 30, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
BREAKING minor release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@JuliaRegistrator @JuliaTagBot