Bump to v0.5.0

[milankl]

@maleadt @DilumAluthge @JeffreySarnoff I was wondering whether we can release and tag the current master as v0.4.3, meaning a non-breaking change. I believe all commits merged since v0.4.2 haven't been breaking but please let me know if we should use v0.5 instead

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4b657c0) 66.29% compared to head (405c64a) 66.29%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #62   +/-   ##
=======================================
  Coverage   66.29%   66.29%           
=======================================
  Files           3        3           
  Lines         181      181           
=======================================
  Hits          120      120           
  Misses         61       61           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[maleadt]

Relying on native codegen seems like a major change though... Maybe we should wait until 1.10 is released, and then release BFloat16s.jl 0.5? That way, people know there's been a major change, and can use Julia 1.10 to test their code.

[milankl]

Sounds great @maleadt, so you want to restrict compat to 1.10 too with v0.5?

[maleadt]

I don't think that's necessary, as support for older Julia versions does remain. It should probably be noted in the release notes that it's important to test on 1.10 too, given that the package works significantly different on that version of Julia.