Skip to content

fix(v8/publish): Ensure all packages are tagged with v8 on when publishing to NPM #4931

fix(v8/publish): Ensure all packages are tagged with v8 on when publishing to NPM

fix(v8/publish): Ensure all packages are tagged with v8 on when publishing to NPM #4931

Triggered via pull request March 25, 2026 12:30
@Lms24Lms24
ready_for_review #19974
lms/ref-fix-tags
Status Success
Total duration 8s
Artifacts

project-automation.yml

on: pull_request
Check if PR is in project
4s
Check if PR is in project
Mark as In Progress
0s
Mark as In Progress
Mark as In Review
0s
Mark as In Review
Mark as Done
0s
Mark as Done
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Check if PR is in project
content not found with ID PR_kwDOADLKPM7NVQCB
Check if PR is in project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/update-project-action@f980378bc179626af5b4e20ec05ec39c7f7a6f6d. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/