Chad ElliottandClaude Opus 5.5 7c74ae0ac3 Issue #2589: a content duplicate starts from the file, not from the other photo's record ...

The new record for a catalog photo whose bytes match another library photo copied that whole
record and reset a few fields, so the other photo's edits, history, versions, ratings and written
metadata (title, keywords, face regions) carried over, from a trashed photo too. It now starts as a
new photo and takes only what the bytes determine: format, size, kind, capture time, camera EXIF,
GPS, focus point, content hash, embedded lens data and preview-only state. The catalog's own
settings and metadata apply on top as before.

Tests: the duplicate test gives the other photo edits, history, a version, a title, keywords and a
Local baseline and checks none reach the new record; a reimport after a master and its virtual copy
were trashed counts each once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-29 23:56:50 -05:00

..

examples

refactor(bench): dispatch specialized render modes

2026-10-28 03:24:18 +00:00

src

Issue #2589: a content duplicate starts from the file, not from the other photo's record

2026-10-29 23:56:50 -05:00

tests/it

CI: one test binary per crate, line tables only, one WASM check (#2710)

2026-10-23 13:34:30 -04:00

build.rs

fonts: Georgian UI text from craft-fonts' Noto Sans Georgian on the web

2026-10-18 16:14:56 +04:00

Cargo.toml

chore(deps): refresh safe dependency bumps (#2994)

2026-10-25 19:30:51 -04:00