Add/newsletter + update install docs for early release of PyHealth 2.0 #798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the documentation to announce the early full release of PyHealth 2.0, clarify installation instructions, and highlight major new features and improvements. It also updates references to the legacy version and adds a newsletter entry detailing the 2.0 release and future plans.
Key documentation and communication updates:
PyHealth 2.0 Release Announcement
docs/newsletter/2026-01-pyhealth-2.0-release.rst) announcing the early release of PyHealth 2.0, summarizing major new features (dynamic memory support, parallelization, new models/datasets, improved interpretability), and outlining the future roadmap for the toolkit. [1] [2] [3]Installation Instructions and Versioning
README.rstanddocs/install.rstto recommend installing the latest PyHealth 2.0 release withpip install pyhealth, and clarified that this now installs version 2.0 rather than the legacy 1.16 version. The instructions also specify Python version requirements and highlight the improved features in 2.0. [1] [2]Tutorial and Reference Updates
README.rstanddocs/tutorials.rstto refer to "PyHealth 1.16" instead of "PyHealth 1.6" for consistency with the legacy versioning. [1] [2]Newsletter Archive
These changes ensure that users are informed about the major update, have clear installation guidance, and can easily find information about both the new and legacy versions.