Release 0.13.1

[postlund]

0.13.1 Homer (2023-06-22)

Small patch release coming up! Second generation HomePod has
been added as device type. A bug when streaming from a buffer
(something inheriting BufferedIOBase) has been fixed. The bug
would render metadata detection unusable and playback to cut
off early.

Previous releases would send raw PCM samples encapsulated in
Apple Lossless Audio Codec (ALAC) frames. This is now changed
to send pure raw audio frames instead (without ALAC). This
has a big benefit in regards to performance as the ALAC
header is not byte-aligned, so it required a lot of bit
shifting and memory copying. This was extremly noticable on
low-end systems like raspberry pi. Hopefully the performance
is a lot better now. Issue #2057 contains more details
regarding this for those interested.

Changes:

Protocol: RAOP:

51dffc9 raop: Send autio as raw PCM
3d4c5ff raop: Fix bug when streaming from buffer

Other:

02a8cab device: Add second generation HomePod

All changes:

dd773cc build(deps): Bump mypy from 1.3.0 to 1.4.0 in /requirements
fb18e3a build(deps): Bump zeroconf from 0.66.0 to 0.69.0 in /requirements
02a8cab device: Add second generation HomePod
51dffc9 raop: Send autio as raw PCM
3d4c5ff raop: Fix bug when streaming from buffer

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (dd773cc) 88.82% compared to head (6363d0c) 88.82%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2067   +/-   ##
=======================================
  Coverage   88.82%   88.82%           
=======================================
  Files         163      163           
  Lines       10841    10841           
=======================================
  Hits         9629     9629           
  Misses       1212     1212           

Impacted Files	Coverage Δ
pyatv/const.py	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[michalmo]

@postlund looks like there's an issue with the release script that sets the tag to "v" (https://github.com/postlund/pyatv/actions/runs/5348749490/jobs/9699588903?pr=2067#step:7:7), which is already used for https://github.com/postlund/pyatv/releases/tag/v (0.12.1).

[postlund]

@michalmo Yeah, it's a problem when extracting name and version and passing it along to the next job. For some reason the variables are not saved/restored properly and becomes empty (thus the single "v"). I haven't managed to figure out how to fix this yet, but it's related to GitHub deprecating the ::set-output function in favor of piping to a file instead. I will continue to investigate.