release: v0.21.0 — nine opportunity-mined items (the #50 repair path, portability, discovery) - #98
Merged
Merged
Conversation
…without a segment id
- relink --stage copies each relinked video/audio into assets/<kind>/ and points the material at the copy, so the repaired draft is portable (pyJianYingDraft#177) - fixture --check scans the finished bundle (SANITIZE_REPORT.json and README included) for residual home paths, emails, device ids and the account name, with file:line findings and a non-zero exit; a bundle dir as the argument re-checks without rebuilding (#50, #59) - every write refusal now names its gate - refused [editor-open] / [version-boundary] / [draft-changed-on-disk] / [mirror-newer] - so the next pasted stderr line is unambiguous about which gate fired (#50 side finding)
…enerate the reference
…ncryption translations, v0.21.0 highlights
… portability, discovery)
Two composed bugs, found by smoking a bundle built under /home instead of /tmp: the verify pass scanned report.out_dir, which is itself redacted (/home/USER/...) and so not a filesystem path; and the home-path scan flagged the redactor's own USER placeholder, which every correctly redacted home-dir bundle (and every Windows/macOS temp dir) contains. The check now scans the real --out path and captures the account segment so exactly the USER placeholder passes.
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.
v0.21.0 — nine items mined from what users are actually hitting, across this repo's issues, its forks, and the wider CapCut/JianYing tooling ecosystem.
New
sync-timelines --nested— opt-in repair for builds that keep the live timeline underTimelines/<id>/(the #50 case, confirmed on CapCut Mac 9.2.8): copies the root timeline into the nested documents, each keeping its own GUID. What commands read is unchanged; nothing happens without the flag.lint --pip— validates the PIP + local-mask workflow (#78): overlay / keyframe / mask-attachment counts, missing media by path, CI-friendly exit codes.catalogue <query>— find a resource id by name across every bundled and harvested table; paste an id to get its name back.import-srt/import-ass--clone-style— imported captions keep the draft's existing style, no segment id lookup needed.relink --stage— relinked media is copied into the draft folder, so the repaired draft survives moving machines.fixture --check— verifies a diagnostic bundle leaks no home path, email, or device id before you share it;capcut fixture <bundle-dir> --checkre-checks an existing bundle.lintmedia-unregistered— info-only note for drafts whosedraft_meta_info.jsonregisters no media (reported as "file inaccessible" on CapCut 9.1).refused [editor-open]/[version-boundary]/[draft-changed-on-disk], so an error line is unambiguous about why the write stopped.Fixed
fixture --checkworks for projects under a home directory (scans the real output path; the redactor'sUSERplaceholder is not a finding).No command was removed and no existing flag changed meaning. Full details in the changelog.