Skip to content

Address Platforms/emscripten/browser_test/package-lock.json Dependabot alerts #158395

Open

Description

@ezio-melotti

Dependabot is currently reporting a few vulnerabilities in Platforms/emscripten/browser_test/package-lock.json.
These alerts are separate from the regular updates listed in dependabot.yml.

There are 5 solutions to this problem:

  1. manually update those deps and fix the alerts;
  2. manually ask dependabot to create security updates for each alert (like 1);
  3. manually dismiss the alert;
  4. configure Dependabot to check and create PRs to update the deps in package-lock.json;
  5. configure Dependabot to ignore package-lock.json (if possible);

If we decide to go with 1/2/3, we would need to manually intervene for any future alert, so 4/5 are better solutions in the long term. If we go with 4/5 it should be enough to list the main branch in dependabot.yml to solve the alerts since Dependabot only looks at the main branch, unless we want to update deps on maintenance branches and/or keep all branches aligned.

@hoodmane, do you have any preference?

Footnotes

  1. https://github.com/python/cpython/pull/158394 ↩

Activity

  1. added
    infraCI, GitHub Actions, buildbots, Dependabot, etc.
    3.16new features, bugs and security fixes
    on Sep 29, 2026
  2. freakboy3742 commented on Sep 30, 2026

    @freakboy3742
    Contributor

    FWIW, my preference would be 4/5 - automated processes for this sort of thing are always preferable. If there's an option to have that automatically for maintenance branches as well, then all the better; but I'm not sure if that breaks any other tooling around tracking back ports.

  3. hoodmane commented on Sep 30, 2026

    @hoodmane
    Contributor

    I agree that not having to manually update the dependencies would be great and backporting them is also preferable.

  4. added a commit that references this issue on Oct 13, 2026
  5. ezio-melotti commented on Oct 13, 2026

    @ezio-melotti
    MemberAuthor

    I merged gh-159234 which resulted in 3 PRs:

    I merged the first, but this didn't resolve any of the 3 remaining Dependabot alerts. The 4th was manually fixed in gh-158394 on main, but the PRs for 3.15/3.14 don't include follow-redirects bumps. I'm currently investigating how to solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.16new features, bugs and security fixesinfraCI, GitHub Actions, buildbots, Dependabot, etc.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions