fix: scipy sparse bug

[Bento007]

Reason for Change

• BUG: scipy 1.15.0 breaking validation #1165

Changes

• pin scipy to scipy<1.15

Testing

• unit tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.47%. Comparing base (093e4ae) to head (61876b9).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1166   +/-   ##
=======================================
  Coverage   90.47%   90.47%           
=======================================
  Files          18       18           
  Lines        2069     2069           
=======================================
  Hits         1872     1872           
  Misses        197      197           

Components	Coverage Δ
cellxgene_schema_cli	91.77% <0.00%> (ø)
migration_assistant	91.26% <0.00%> (ø)
schema_bump_dry_run_genes	79.80% <0.00%> (ø)
schema_bump_dry_run_ontologies	99.53% <0.00%> (ø)

[nayib-jose-gloria]

as you (correctly) pointed out previously, the long-tail of the 5.3 updates in main means this is going to be annoying to release as a patch.

do you think its worth reverting main to 5.2.1 and creating a feature branch now to re-apply all the 5.3 commits since then to a feature branch? cc: @joyceyan

[Bento007]

@nayib-jose-gloria, why 5.2.1? Also we can do a 5.2.3 release with the patch and merge that back into main. That should retain all of the 5.3 changes and the 5.2.3 patch.

[joyceyan]

do you think its worth reverting main to 5.2.1 and creating a feature branch now to re-apply all the 5.3 commits since then to a feature branch?

@nayib-jose-gloria do you mean reverting main to 5.2.2? i think effort wise the two choices (revert main to 5.2.2 and release this change as 5.2.3 vs release this change as a 5.2.3 patch) seem fairly equivalent to me. i would probably slightly prefer reverting main to 5.2.2 and moving the 5.3 commits to a feature branch since we don't have a timeline set for actually releasing 5.3 yet

[Bento007]

These changes were made in 5.2.3