This release drops support for fusions in the mutation data format. Going forward fusions can only be imported in the Structural Variant (SV) format. This is mainly a refactoring effort to simplify the codebase and pave the way for the development of novel structural variant visualizations in the future. The release additionally includes several enhancements related to the handling of SV data (see below).
🧬 Features
- Improved handling of structural variants @averyniceday @alisman (#9736 cbioportal-frontend#4332)
- Structural variant API no longer backed by fusion typed events in the mutation event/mutation table
- Structural variant/fusion events are now linked to a separate genetic profile and stored inside the structural variant table
📘 Documentation
- Updates to data formats (fusion files now deprecated, updated structural variant format). More information on file formats here.
🗄 Database Migration
- Change structure of Structural Variant table
- Non-backward compatible database migration. Fusion events stored in a v4.x.x database will not be automatically migrated and will not be present in a v5.x.x portal. Studies featuring fusion mutation data must be converted independently and re-imported. Tools for converting fusion to structural variant files here. See migration notes here.
- Several molecular profile ids were renamed from
{study_id}_fusionto{study_id}_structural_variants
🕵️♀️ Full commit logs
- Backend: v4.1.19...v5.0.0
- Frontend: cBioPortal/cbioportal-frontend@v4.1.19...v5.0.0
🏷Notes on versioning and release procedure
https://docs.cbioportal.org/4.-development/release-procedure#a-note-on-versioning