Skip to content

fix(deps): update dependency semver-diff to v5#588

Open
renovate[bot] wants to merge 1 commit into
devfrom
renovate/semver-diff-5.x
Open

fix(deps): update dependency semver-diff to v5#588
renovate[bot] wants to merge 1 commit into
devfrom
renovate/semver-diff-5.x

Conversation

@renovate

@renovate renovate Bot commented Sep 19, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
semver-diff 3.1.15.0.0 age confidence

Release Notes

sindresorhus/semver-diff (semver-diff)

v5.0.0

Compare Source

v4.0.0

Compare Source

Breaking

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 71b70e8 to 05deadd Compare September 27, 2025 03:34
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 05deadd to 2752a74 Compare November 2, 2025 03:42
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 2752a74 to 94cd7b9 Compare November 10, 2025 15:45
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 94cd7b9 to 4adbbf3 Compare November 23, 2025 10:55
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 4adbbf3 to 061877b Compare December 5, 2025 23:28
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch 2 times, most recently from 98cb47b to 7dc627a Compare January 8, 2026 16:34
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 7dc627a to 8cc620f Compare February 1, 2026 08:23
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 8cc620f to d7ba717 Compare February 21, 2026 06:34
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch 2 times, most recently from 86ea37c to 133ca05 Compare March 8, 2026 00:42
@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from 133ca05 to cda431d Compare April 30, 2026 08:12
@ghost

ghost commented Apr 30, 2026

Copy link
Copy Markdown

Rooviewer Clock   See task

Found 1 issue that will break the application at runtime.

  • ESM incompatibility: semver-diff v4+ is pure ESM but this project uses CommonJS require(). Upgrading to v5 will cause ERR_REQUIRE_ESM on startup. Consider staying on 3.x or replacing with the built-in semver.diff() from the semver package (v5 is deprecated for this reason).

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

Comment thread package.json
"rss-parser": "3.13.0",
"select-random-file": "1.2.4",
"semver-diff": "3.1.1",
"semver-diff": "5.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

semver-diff v4+ is pure ESM (release notes), but this project is CommonJS -- index.js loads it with require('semver-diff') and package.json has no "type": "module". This upgrade will cause an ERR_REQUIRE_ESM runtime crash on startup.

Additionally, v5.0.0 is itself deprecated ("the semver package now supports this built-in"). A safer path would be to stay on 3.x or replace the single call site in index.js with the equivalent semver.diff() from the semver package that is already an indirect dependency.

Fix it with Roo Code or mention @roomote and request a fix.

@renovate renovate Bot force-pushed the renovate/semver-diff-5.x branch from cda431d to 65ad95a Compare May 12, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants