Skip to content

chore(deps): bump 13 transitive dependencies - #493

Merged
anuragxxd merged 2 commits into
devfrom
chore/bump-transitive-deps
Oct 28, 2026
Merged

anuragxxd merged 2 commits into
devfrom
chore/bump-transitive-deps

Conversation

@anuragxxd

@anuragxxd anuragxxd commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

Description

Combines 13 open Dependabot security updates into one pull request. The dev rules require pull requests to be up to date before merging, so merging them one by one would take 13 consecutive CI runs. All of them change only package-lock.json (transitive dependencies):

Supersedes Update
#481 dompurify 3.1.6 → 3.4.17, mermaid 10.9.3 → 10.9.8, dagre-d3-es 7.0.10 → 7.0.13
#480 postcss-selector-parser 6.1.2 → 6.1.5
#479 terser-webpack-plugin 5.3.14 → 5.6.1 (drops serialize-javascript 6.0.2)
#441 handlebars 4.7.8 → 4.7.9
#440 picomatch 2.3.1 → 2.3.2, 4.0.3 → 4.0.4
#438 flatted 3.3.3 → 3.4.2
#437 minimatch 3.1.2 → 3.1.5, 9.0.5 → 9.0.9
#435 rollup 4.45.1 → 4.59.0 (and its nested copies 2.79.2 → 2.80.0, 3.29.5 → 3.30.0)
#434 basic-ftp 5.0.5 → 5.2.0
#433 ajv 6.12.6 → 6.14.0, 8.17.1 → 8.18.0
#429 qs 6.14.0 → 6.14.2
#421 lodash 4.17.21 → 4.17.23
#420 diff 5.2.0 → 5.2.2, 4.0.2 → 4.0.4

package-lock.json is the result of merging the 13 Dependabot branches into dev (no conflicts). The Dependabot pull requests are closed once this is merged. #482 was merged on its own. Not included: #483 (next 14 → 15), which fails to build the documentation (@next/font/google was removed in Next.js 15) and needs a migration of its own.

Prepared with Claude Code (an AI agent); Anurag Gupta is responsible for this pull request.

Checklist

  • My code follows the contributing guidelines of this project.
  • I am aware that all my commits will be squashed into a single commit, using the PR title as the commit message.
  • I have performed a self-review of my own code.
  • I have commented my code in hard-to-understand areas.
  • I have updated the user-facing documentation to describe any new or changed behavior.
  • My changes generate no new warnings.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have not reduced the existing code coverage.

Comments

Lockfile-only change, so there is no code, documentation or test to add; lint warnings were not compared against dev (0 errors). Checked locally on Node.js 24 with exactly this package-lock.json: npm ci, node --test scripts/release.test.js, npm run lint (includes the build), npm run build and npm test pass.

Summary by Sourcery

Enhancements:

  • Consolidate security-related updates to 13 transitive npm dependencies in the project lockfile.

Combines the open Dependabot security updates #481, #480, #479, #441,
#440, #438, #437, #435, #434, #433, #429, #421 and #420, which change
package-lock.json only.
@anuragxxd anuragxxd self-assigned this Oct 28, 2026
@sourcery-ai

sourcery-ai Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This lockfile-only PR merges 13 Dependabot branches into one conflict-free package-lock.json update, refreshing vulnerable transitive dependencies and nested copies while consolidating CI validation into a single review and merge. Reviewers should verify the lockfile resolutions and confirm the reported install, build, lint, release-test, and full-test results; the unrelated Next.js upgrade is intentionally out of scope.

File-Level Changes

Change Details Files
Consolidate 13 Dependabot security updates into a single npm lockfile refresh.
  • Update transitive versions for DOMPurify, Mermaid-related packages, minimatch, ajv, lodash, qs, diff, rollup, and other affected dependencies.
  • Refresh nested dependency copies and remove the superseded serialize-javascript path via the terser-webpack-plugin update.
  • Keep the change limited to package resolution metadata; no application source, tests, or documentation are modified.
package-lock.json
Validate the merged lockfile and dependency updates against the existing project workflows.
  • Run npm ci, release tests, lint/build, build, and the full test suite on Node.js 24.
  • Exclude the unrelated Next.js 14-to-15 migration because it requires a separate documentation build fix.
package-lock.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@anuragxxd
anuragxxd marked this pull request as ready for review October 28, 2026 05:04
@anuragxxd
anuragxxd enabled auto-merge (squash) October 28, 2026 05:04

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!

Fixed security issues:


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

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.

1 participant