release: ship v0.26.1 draft and fixture fixes - #136
Merged
Merged
Conversation
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
1 participant
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.
The fixes from #135 are merged, but users installing from npm still receive v0.26.0. This prepares v0.26.1 with the escaped-Windows-path fixture redaction fix, compiler canvas/source-duration fixes, and the scoped Windows 8.7.0 active-timeline fix.
Updates the package and lockfile versions, dates the changelog, regenerates the command reference, and adds a pinned install command to the end-to-end review guide. No additional runtime changes.
Validation: all 1,017 tests passed through the repository's pre-commit gate; lint and generated docs passed. A fresh install of the exact npm tarball passed CLI/library/version checks, compiler canvas/source-duration/bounds checks, fixture redaction/leak rejection, and active-timeline writes/ID preservation/restore against the contributed fixture.
npm publish --dry-runpassed.The patched CapCut desktop round-trip remains pending in #50. #52 still needs reporter confirmation, and the assigned mask-keyframe work in #44 needs an app-authored fixture and rendered interpolation evidence. This release makes no new desktop compatibility claim.