Skip to content

chore(ci): use github-hosted runner for publishing#2934

Merged
gabrielmfern merged 1 commit intocanaryfrom
chore/use-github-runner-for-release
Feb 4, 2026
Merged

chore(ci): use github-hosted runner for publishing#2934
gabrielmfern merged 1 commit intocanaryfrom
chore/use-github-runner-for-release

Conversation

@gabrielmfern
Copy link
Member

@gabrielmfern gabrielmfern commented Feb 4, 2026

Provenance is not supported on runners that aren't hosted by GitHub, so I think it's worth it for us to use GItHub's just for the release workflow.

https://github.com/resend/react-email/actions/runs/21676909109/job/62499778929


Summary by cubic

Switch the release workflow to a GitHub-hosted runner to enable npm provenance when publishing packages. Updated runs-on to ubuntu-latest in .github/workflows/release.yml.

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

@gabrielmfern gabrielmfern requested a review from joaopcm February 4, 2026 15:22
@gabrielmfern gabrielmfern self-assigned this Feb 4, 2026
@vercel
Copy link

vercel bot commented Feb 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
react-email Ready Ready Preview, Comment Feb 4, 2026 3:22pm
react-email-demo Ready Ready Preview, Comment Feb 4, 2026 3:22pm

Request Review

@changeset-bot
Copy link

changeset-bot bot commented Feb 4, 2026

⚠️ No Changeset found

Latest commit: da3e273

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

@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 Medium
Install-time scripts: npm sharp during install

Install script: install

Source: node install/check.js || npm run build

From: ?npm/next@16.1.6npm/sharp@0.34.5

ℹ Read more on: This package | This alert | What is an install script?

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: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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

Confidence score: 5/5

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

@gabrielmfern gabrielmfern merged commit ed0f358 into canary Feb 4, 2026
15 of 16 checks passed
@gabrielmfern gabrielmfern deleted the chore/use-github-runner-for-release branch February 4, 2026 15:25
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