[Thelost77]

This pull request prepares v0.8.1. It has one commit.

v0.8.1 is the release of pull request #6, which corrects nine faults in the progress sync of pine. Pull request #6 is in main. No other change came after v0.8.0.

Release preparation

• docs/releases/v0.8.1.md: the release notes. They give the nine corrections in words for a user, and the changes of behavior that a user can see.
• README.md and docs/spruce/README.md: the new version in the release steps.

Changes of behavior that the notes name:

• A quit waits until the server has the last position. If the server does not answer, a quit can take up to 5 seconds.
• The play of a different item waits for the close of the old session. If the server does not answer, the wait ends after 10 seconds.
• The listening time that pine sends is lower than before, because the old values were too high. The release does not correct the values that the server has.

spruce has no change in this release. It links none of the changed packages (internal/abs and internal/app).

Verification

On macOS (Apple Silicon), on the commit of this pull request:

• gofmt -l .: no file
• go vet ./...: pass
• go build ./...: pass
• go mod verify: all modules verified
• golangci-lint run with version 2.14.0: 0 issues
• PINE_REQUIRE_LIBMPV=1 PINE_REQUIRE_DBUS=1 go test ./... -count=1: 27 packages pass
• go test -race ./... -count=1: 27 packages pass
• The two link checks of scripts/release.sh: spruce links no pine-only package, and pine links no spruce package.

Not verified

• scripts/release.sh did not run. It makes the tag and publishes the GitHub Release.
• No real Audiobookshelf server ran for the corrections of pull request fix(playback): correct nine faults in progress sync #6, and no real playback ran. The release notes say so.
• No binary of this release exists before the release. The Release workflow builds the binaries after the GitHub Release is published.

After the merge, the release is one command on main:

./scripts/release.sh v0.8.1

🤖 Generated with Claude Code