Skip to content

chore(react-email): upgrade glob to ^13.0.6#2988

Open
Shamir14feb wants to merge 1 commit intoresend:canaryfrom
Shamir14feb:chore/upgrade-glob-v13
Open

chore(react-email): upgrade glob to ^13.0.6#2988
Shamir14feb wants to merge 1 commit intoresend:canaryfrom
Shamir14feb:chore/upgrade-glob-v13

Conversation

@Shamir14feb
Copy link

@Shamir14feb Shamir14feb commented Mar 4, 2026

Summary

Bumps the glob dependency in packages/react-email from ^11.0.0 to ^13.0.6.

Changes

  • packages/react-email/package.json — Updated glob from ^11.0.0 to ^13.0.6
  • pnpm-lock.yaml — Lockfile updated accordingly

Motivation

  • Align with the current major version of glob (v13) and its fixes/improvements
  • v13 reduces dependency count; our usage of the API is unchanged

Compatibility

No code changes. Existing usage in src/commands/export.ts (import { glob } from 'glob' and glob.sync(pattern, { absolute: true })) remains valid in v13. The only v13 breaking change is the CLI moving to glob-bin; we only use the programmatic API.

Checklist

  • Updated dependency in packages/react-email/package.json
  • Ran pnpm install and updated lockfile
  • No source code changes required

Summary by cubic

Upgraded glob in packages/react-email from ^11.0.0 to ^13.0.6 to adopt the latest fixes and reduce transitive dependencies. No source changes; our programmatic usage remains compatible, and the lockfile is updated.

Written for commit fc2f985. Summary will update on new commits.

@changeset-bot
Copy link

changeset-bot bot commented Mar 4, 2026

⚠️ No Changeset found

Latest commit: fc2f985

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

@vercel
Copy link

vercel bot commented Mar 4, 2026

@shamir-ahmed is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

@socket-security
Copy link

@socket-security
Copy link

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 Critical
Critical CVE: Basic FTP has Path Traversal Vulnerability in its downloadToDir() method in npm basic-ftp

CVE: GHSA-5rq4-664w-9x2c Basic FTP has Path Traversal Vulnerability in its downloadToDir() method (CRITICAL)

Affected versions: < 5.2.0

Patched version: 5.2.0

From: pnpm-lock.yamlnpm/basic-ftp@5.0.5

ℹ Read more on: This package | This alert | What is a critical CVE?

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 support@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/basic-ftp@5.0.5. 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

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 4, 2026

Open in StackBlitz

npm i https://pkg.pr.new/resend/react-email@2988

commit: fc2f985

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.

2 participants