Skip to content

Update dependencies#2037

Merged
bluwy merged 2 commits into
nextfrom
update-next-deps
May 26, 2026
Merged

Update dependencies#2037
bluwy merged 2 commits into
nextfrom
update-next-deps

Conversation

@bluwy
Copy link
Copy Markdown
Member

@bluwy bluwy commented May 26, 2026

Update to latest (7 days before)

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 26, 2026

⚠️ No Changeset found

Latest commit: 44393e7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 26, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedpkg-pr-new@​0.0.741001007096100
Addedtypescript-eslint@​8.59.41001007498100
Added@​types/​node@​25.9.01001008196100
Addedfs-fixture@​2.14.0861009792100
Addedeslint@​10.4.08910010095100
Addedoxfmt@​0.50.0991009296100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 26, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yaml → npm/@vitest/[email protected] → npm/[email protected] → npm/@typescript-eslint/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@codecov
Copy link
Copy Markdown

codecov Bot commented May 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.62%. Comparing base (6a05002) to head (44393e7).

Additional details and impacted files 
@@           Coverage Diff           @@
##             next    #2037   +/-   ##
=======================================
  Coverage   80.62%   80.62%           
=======================================
  Files          61       61           
  Lines        2317     2317           
  Branches      638      636    -2     
=======================================
  Hits         1868     1868           
  Misses        397      397           
  Partials       52       52

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bluwy bluwy added this pull request to the merge queue May 26, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 26, 2026
@bluwy bluwy added this pull request to the merge queue May 26, 2026
Merged via the queue into next with commit 61eef67 May 26, 2026
12 checks passed
@bluwy bluwy deleted the update-next-deps branch May 26, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@beeequeue beeequeue beeequeue approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@bluwy @beeequeue