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.

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

Prepare for upcoming Seurat v5 release #55

Open
Gesmira opened this issue Oct 3, 2023 · 2 comments
Open

Prepare for upcoming Seurat v5 release #55

Gesmira opened this issue Oct 3, 2023 · 2 comments

Comments

@Gesmira
Copy link

Gesmira commented Oct 3, 2023

I am opening this issue as a notification because dyngen is listed here as a package that relies (depends/imports/suggests) on Seurat. As you may know, we recently released Seurat v5 as a beta in March of this year, with new updates for spatial, multimodal, and massively scalable analysis. For more information on updates and improvements, check out our website https://satijalab.org/seurat/.
We are now preparing to release Seurat v5 to CRAN, and plan to submit it on October 23rd. While we have tried our best to keep things backward-compatible, it is possible that updates to Seurat and SeuratObject might break your existing functionality or tests. We wanted to reach out before the new version is on CRAN, so that there's time to report issues/incompatibilities and prepare you for any changes in your code base that might be necessary.

We apologize for any disruption or inconvenience, but hope that the improvements to Seurat v5 will benefit your users going forward.
To test the upcoming release, you can install Seurat from the seurat5 branch using the instructions available on this page: https://satijalab.org/seurat/articles/install.

Thank you!
Seurat v5 team

@rcannood
Copy link
Member

rcannood commented Oct 3, 2023

Hi @Gesmira from the Seurat team!

Thanks for reaching out. Did you already run a revdepcheck?

Thanks,
Robrecht

@Gesmira
Copy link
Author

Gesmira commented Oct 3, 2023

Hi Robrecht,
We did. Your package did not come up as showing failures, but because there may be potential false negatives, we wanted to inform all reverse dependencies so they can run their own tests to ensure compatability.
Best,
Gesmira

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants