chore(deps-dev): bump jscpd from 5.0.7 to 5.0.14 in /cli - #606
Merged
Conversation
Bumps [jscpd](https://github.com/kucherenko/jscpd/tree/HEAD/rust/jscpd) from 5.0.7 to 5.0.14. - [Release notes](https://github.com/kucherenko/jscpd/releases) - [Changelog](https://github.com/kucherenko/jscpd/blob/master/CHANGELOG.md) - [Commits](https://github.com/kucherenko/jscpd/commits/v5.0.14/rust/jscpd) --- updated-dependencies: - dependency-name: jscpd dependency-version: 5.0.14 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
![aidd-bot[bot]](https://avatars.githubusercontent.com/in/3959336?s=60&v=4){kind=small}
dependabot
Bot
deleted the
dependabot/npm_and_yarn/cli/next/jscpd-5.0.14
branch
August 7, 2026 10:08
blafourcade
added a commit
that referenced
this pull request
Aug 14, 2026
The promote window was anchored at the most recent back-merge sync commit, on the assumption that everything before it already lived on main. A back-merge only folds main into next; it never carries next's own commits back to main. Work that landed on next after the previous promote but before the last back-merge therefore fell behind the boundary and was dropped for good, which is how #605, #606 and #607 went missing. Anchor the window at the newest sync, then widen it to older syncs until the replayed branch reproduces origin/next exactly, and filter every candidate through git cherry so commits main already carries under a rebased hash are never replayed. The tree comparison is now the acceptance test that drives the search rather than a final assertion. Key the no-op path on main and next sharing a tree instead of on an empty window: an empty window is precisely what silently swallowed the dropped commits. Fetch the promote branch so --force-with-lease leases against the real ref. Co-authored-by: aidd-bot[bot] <aidd-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
aidd-bot Bot
pushed a commit
that referenced
this pull request
Aug 14, 2026
Bumps [jscpd](https://github.com/kucherenko/jscpd/tree/HEAD/rust/jscpd) from 5.0.7 to 5.0.14. - [Release notes](https://github.com/kucherenko/jscpd/releases) - [Changelog](https://github.com/kucherenko/jscpd/blob/master/CHANGELOG.md) - [Commits](https://github.com/kucherenko/jscpd/commits/v5.0.14/rust/jscpd) --- updated-dependencies: - dependency-name: jscpd dependency-version: 5.0.14 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
aidd-bot Bot
added a commit
that referenced
this pull request
Aug 14, 2026
The promote window was anchored at the most recent back-merge sync commit, on the assumption that everything before it already lived on main. A back-merge only folds main into next; it never carries next's own commits back to main. Work that landed on next after the previous promote but before the last back-merge therefore fell behind the boundary and was dropped for good, which is how #605, #606 and #607 went missing. Anchor the window at the newest sync, then widen it to older syncs until the replayed branch reproduces origin/next exactly, and filter every candidate through git cherry so commits main already carries under a rebased hash are never replayed. The tree comparison is now the acceptance test that drives the search rather than a final assertion. Key the no-op path on main and next sharing a tree instead of on an empty window: an empty window is precisely what silently swallowed the dropped commits. Fetch the promote branch so --force-with-lease leases against the real ref. Co-authored-by: aidd-bot[bot] <aidd-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
blafourcade
pushed a commit
that referenced
this pull request
Aug 14, 2026
Bumps [jscpd](https://github.com/kucherenko/jscpd/tree/HEAD/rust/jscpd) from 5.0.7 to 5.0.14. - [Release notes](https://github.com/kucherenko/jscpd/releases) - [Changelog](https://github.com/kucherenko/jscpd/blob/master/CHANGELOG.md) - [Commits](https://github.com/kucherenko/jscpd/commits/v5.0.14/rust/jscpd) --- updated-dependencies: - dependency-name: jscpd dependency-version: 5.0.14 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
blafourcade
added a commit
that referenced
this pull request
Aug 14, 2026
The promote window was anchored at the most recent back-merge sync commit, on the assumption that everything before it already lived on main. A back-merge only folds main into next; it never carries next's own commits back to main. Work that landed on next after the previous promote but before the last back-merge therefore fell behind the boundary and was dropped for good, which is how #605, #606 and #607 went missing. Anchor the window at the newest sync, then widen it to older syncs until the replayed branch reproduces origin/next exactly, and filter every candidate through git cherry so commits main already carries under a rebased hash are never replayed. The tree comparison is now the acceptance test that drives the search rather than a final assertion. Key the no-op path on main and next sharing a tree instead of on an empty window: an empty window is precisely what silently swallowed the dropped commits. Fetch the promote branch so --force-with-lease leases against the real ref. Co-authored-by: aidd-bot[bot] <aidd-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 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.
Bumps jscpd from 5.0.7 to 5.0.14.
Release notes
Sourced from jscpd's releases.
... (truncated)
Changelog
Sourced from jscpd's changelog.
... (truncated)
Commits
2a6a1a4release: cpd-v5.0.1464258a9release: cpd-v5.0.12ff1ae36fix(rust): rename cpd binary and npm platform packages to jscpdf768035docs(readme): fix jscpd@5 bin claim and refresh npm README115f7fbrelease: cpd-v5.0.11c4cf41arelease: cpd-v5.0.109f6b8f5docs: add Nix and Homebrew install instructions (#818)527bb08chore: remove defunct Universal Analytics tracking pixels from all READMEsdbe90b0docs: update project URLs to jscpd.dev, add curl install, clean up badgesdcef743release: cpd-v5.0.9Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)