Skip to content

Conversation

@MattIPv4
Copy link
Member

@MattIPv4 MattIPv4 commented Jul 3, 2025

Description

Per discussion in #7824 (comment), the publish matrix sometimes generates a failure in the post-step for actions/setup-node due to a cache issue. I suspect this is due to us enabling pnpm caching for actions/setup-node in this job when we never invoke pnpm install, resulting in the post-step being unable to find dependencies to cache if a cache hit didn't occur during actions/setup-node earlier in the job.

Validation

Dispatch this workflow on this branch. May need to manually delete whatever cache entry is hit and re-dispatch.

Cannot publish arbitrary commits via the job, will need to merge and then test in main.

Related Issues

N/A

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

Copilot AI review requested due to automatic review settings July 3, 2025 01:14
@MattIPv4 MattIPv4 requested a review from a team as a code owner July 3, 2025 01:14
@vercel
Copy link

vercel bot commented Jul 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jul 3, 2025 1:14am

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR prevents actions/setup-node from attempting to cache pnpm dependencies in the publish workflow since no installation step runs, avoiding cache lookup failures.

  • Removed the cache: pnpm option from the setup step
  • Added an explanatory comment to clarify why caching is disabled

@codecov
Copy link

codecov bot commented Jul 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.37%. Comparing base (2aa8ae6) to head (5fcb461).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7939      +/-   ##
==========================================
- Coverage   75.42%   75.37%   -0.05%     
==========================================
  Files          96       96              
  Lines        8354     8354              
  Branches      219      220       +1     
==========================================
- Hits         6301     6297       -4     
- Misses       2051     2055       +4     
  Partials        2        2              

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

@MattIPv4 MattIPv4 added the github_actions:pull-request Trigger Pull Request Checks label Jul 3, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jul 3, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jul 3, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 97 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 100 🟢 96 🟢 100 🟠 82 🔗
/en/about/previous-releases 🟢 99 🟢 96 🟢 100 🟠 83 🔗
/en/download 🟢 98 🟢 100 🟢 100 🟢 91 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🟢 92 🔗

@ovflowd
Copy link
Member

ovflowd commented Jul 3, 2025

Fast-tracking as a hot fix! cc @nodejs/web-infra

@ovflowd ovflowd added this pull request to the merge queue Jul 3, 2025
@ovflowd ovflowd added the fast-track Fast Tracking PRs label Jul 3, 2025
Merged via the queue into main with commit 3dcb550 Jul 3, 2025
20 of 21 checks passed
@ovflowd ovflowd deleted the MattIPv4/disable-publish-pnpm-cache branch July 3, 2025 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fast-track Fast Tracking PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants