Repository navigation
Release 0.10.0: ISRC matching for linked event tracks and duplicate reconciliation - #69
Merged
Merged
Conversation
A Deezer, YouTube or SoundCloud event track with no recorded provenance is now matched to an active collection content carrying the same ISRC, under the existing duration guard. Fuzzy title/artist matching and staged-file scoring stay forbidden for these rows, so a remix never lands on its original. Apply re-verifies the ISRC before any Rekordbox write. Health > Backups gains a previewed, trash-first reconciliation of the downloads 0.9.0 already produced: a ready download that duplicates a collection content is matched to it, an applied duplicate is replaced by the original inside one guarded mutation, and a refused trash is retried through the consent loop. The preview reports ISRC coverage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Version, release date (2026-10-09) and lockfiles aligned; release license inventories regenerated. optional_component.json and web_audio_component.json stay at the published 0.9.0 pins until release-pin.yml produces the hosted 0.10.0 manifests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From Release Pin run 37939332081 on this branch; only version, archive name, download URL, size and SHA-256 change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 0.10.0. Since 0.9.0, a track added to an event from a Deezer link was only recognised as already in the Rekordbox collection when Syncbox held a download record for that exact Deezer item. That record rarely exists, so tracks plainly in the collection were downloaded again and duplicated in Rekordbox.
readydownload duplicating one collection content: the download is trashed first, then the row is matched (no Rekordbox write);appliedduplicate: inside one guardedmutate(), the event tag moves to the original and the duplicate is soft-deleted, then the download is trashed;cleanupitem.ui/package.json, sidecar, shell, both components, lockfiles,release-build.jsondated 2026-10-09, README install links, reproducibility expectations), license inventories regenerated, component manifests from the hosted Release Pin run.OpenSpec change:
openspec/changes/reconcile-deezer-event-tracks-by-isrc. Read-only preview on the owner's production data: 27 linked tracks all with ISRC, 16 proposed relinks (all checked by hand as the same recordings), 0 Deezer downloads without ISRC.Test plan
uv run --locked --exact --managed-python pytest -q)generate_release_licenses.py --check,uv lock --checkx3,cargo metadata --locked,git diff --checkRelease Pin / component manifestgreen on this PRrelease.ymlbuild-only preflight (both roots, ZIP comparison)🤖 Generated with Claude Code