Skip to content

chore: bump go-openaudio to pick up CID-preserving track merge (OpenAudio/go-openaudio#410) - #994

Merged
dylanjeffers merged 1 commit into
mainfrom
chore/bump-etl-preserve-cids
Jul 16, 2026
Merged

chore: bump go-openaudio to pick up CID-preserving track merge (OpenAudio/go-openaudio#410)#994
dylanjeffers merged 1 commit into
mainfrom
chore/bump-etl-preserve-cids

Conversation

@dylanjeffers

Copy link
Copy Markdown
Contributor

Bumps github.com/OpenAudio/go-openaudio (+ pkg/etl) from the 2026-07-13 pin to today's main (b4a5ebe), picking up OpenAudio/go-openaudio#410: a track update carrying explicit "track_cid": null no longer wipes track_cid/orig_file_cid/audio_upload_id at index time.

Context: track 1960897973 (BURKO - Labyrinth) had its CIDs wiped by a 2026-07-14 edit, breaking stream/download/stems-archive; the row was backfilled manually from its content-node upload record. #993 stops the API from signing empty-cid URLs; this bump stops the wipe from happening at all. 125 other tracks are affected and pending backfill.

go build ./... passes locally; dependency delta is 3 days of upstream main.

🤖 Generated with Claude Code

Pulls in OpenAudio/go-openaudio#410: mergeTrackFromMetadata no longer
lets a track update carrying explicit null wipe track_cid,
orig_file_cid, or audio_upload_id. Complements #993 (don't sign media
links with an empty cid) by stopping the wipe at index time.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@dylanjeffers
dylanjeffers merged commit 915c37d into main Jul 16, 2026
2 checks passed
@dylanjeffers
dylanjeffers deleted the chore/bump-etl-preserve-cids branch July 16, 2026 23:20
dylanjeffers added a commit that referenced this pull request Jul 27, 2026
…audio#421) (#996)

Bumps both `github.com/OpenAudio/go-openaudio` and `.../pkg/etl` pins
from `b4a5ebe` (2026-07-16) to `1d9f697` — the merge of
**OpenAudio/go-openaudio#421**, same flow as #994 did for the #410 CID
fix.

## What the new pin brings (ETL / entity manager)

- Persist `orig_filename` on track create/update (never-clear, like the
CIDs) — new stem rows no longer rely on the `/stems` endpoint's title
fallback
- Ignore explicit `"stem_of": null` on track updates so client edits
can't unlink a stem from its parent (#410 failure class)
- Upsert the `stems` join row when an update carries `stem_of` (on-chain
repair path for lost links)

Intervening upstream commits also included (library-only for api):
mediorum transcode/retry fixes (#338, #417#419) and core/logging spam
guards (#420). Nothing release- or mainnet-config-related.

## Relation to #995

#995 is the unblocking change (endpoint tolerates NULLs already in the
DB); this bump prevents recurrence at the write path. Both trace back to
the July stems-invisible incident (Andrew Lux's "Alone" remix contest).

Verified locally: `go build ./...`, stems endpoint tests, and `go test
./indexer/...` all pass on the new pin.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant