Closed dlfivefifty closed 5 months ago
Let's create a release-0.13 branch, as this would simplify collecting all the changes.
Edit: I've created one now. Would you mind changing the target branch for this PR?
Done. But what else is going in release-0.13?
There are some other minor changes that might be useful, like not exporting Zeros/Ones/Fill/Block
and asking users to import these from the corresponding packages.
What's wrong with exporting them?
It just makes the package more prone to breakages, as breaking changes upstream get translated to this package as well, which shouldn't be the case usually. Typically, one may bump the minor or patch version of a package to incorporate a breaking version of a dependency.
ok I see your point
Codecov Report
Attention: Patch coverage is
95.45455%
with1 lines
in your changes are missing coverage. Please review.Additional details and impacted files
```diff @@ Coverage Diff @@ ## release-0.13 #195 +/- ## ================================================ + Coverage 88.37% 89.53% +1.15% ================================================ Files 11 11 Lines 1204 1108 -96 ================================================ - Hits 1064 992 -72 + Misses 140 116 -24 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.