tjue/kokosbananas
0
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity

Bump spotify profile to v2 (192 kbps re-encode) #14

Merged
arne merged 1 commit from spotify-v2-bitrate into main 2026-06-29 09:50:27 +02:00
Conversation 0 Commits 1 Files changed 10 +77 -19
arne commented 2026-06-29 09:50:19 +02:00
Owner
Copy link

Why

Production was still serving 96 kbps Spotify audio. ADR-0018 raised the bitrate to 192 kbps as an in-place profile update, but that never re-encodes existing renditions (transcode idempotency keys on episode+master+profile_id), so the old files survived.

What

  • Bump the spotify profile to v2 (libvorbis 192 kbps / VBR q6) — per ADR-0005 a version bump is the auditable re-encode trigger. A re-transcode now produces fresh v2 renditions; main and spotify-v1 are skipped.
  • spotify-v1 retained dormant; the versionless /audio/... URL + feed already resolve to the latest version.
  • Docs + tests updated; ADR-0020 records the bump and the rule: encode-affecting changes are version bumps, not in-place edits.

After merge (prod)

Deploy → re-transcode both episodes (creates spotify-v2 @192k) → regenerate feeds.

Testing

go build, go vet, full go test ./... green.

🤖 Generated with Claude Code

## Why Production was still serving 96 kbps Spotify audio. ADR-0018 raised the bitrate to 192 kbps as an **in-place** profile update, but that never re-encodes existing renditions (transcode idempotency keys on `episode+master+profile_id`), so the old files survived. ## What - Bump the `spotify` profile to **v2** (libvorbis 192 kbps / VBR q6) — per ADR-0005 a version bump is the auditable re-encode trigger. A re-transcode now produces fresh v2 renditions; `main` and `spotify-v1` are skipped. - `spotify-v1` retained dormant; the versionless `/audio/...` URL + feed already resolve to the latest version. - Docs + tests updated; **ADR-0020** records the bump and the rule: encode-affecting changes are version bumps, not in-place edits. ## After merge (prod) Deploy → re-transcode both episodes (creates spotify-v2 @192k) → regenerate feeds. ## Testing `go build`, `go vet`, full `go test ./...` green. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ADR-0018 raised spotify 96→192 kbps via an in-place profile update, but that
never re-encodes existing renditions (transcode idempotency keys on
episode+master+profile_id). So deployed environments with prior renditions kept
serving the old 96 kbps files.

Per ADR-0005, a profile version bump is the auditable trigger to reprocess the
back catalog. Bump spotify to v2 (libvorbis 192 kbps / q6); a re-transcode now
produces fresh v2 renditions. spotify-v1 is retained, dormant — the versionless
URL + feed already resolve to the latest version. Docs/tests updated; rule of
thumb recorded in ADR-0020: encode-affecting changes are version bumps, not
in-place edits.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
arne merged commit 9adcde3066 into main 2026-06-29 09:50:27 +02:00
arne deleted branch spotify-v2-bitrate 2026-06-29 09:50:27 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tjue/kokosbananas!14
No description provided.