Merge pull request #186 from codex-team/feature/browser #95
npm-publish.yml
on: push
publish-core
/
publish
31s
publish-javascript
/
publish
39s
notify
7s
Annotations
28 warnings
|
publish-core / publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
publish-core / publish:
packages/browser/src/catcher.ts#L227
Missing JSDoc @param "settings" description
|
|
publish-core / publish:
packages/browser/src/addons/performance-issues.ts#L356
Missing JSDoc @param "webVitalsOptions" description
|
|
publish-core / publish:
packages/browser/src/addons/performance-issues.ts#L331
'supportsEntryType' was used before it was defined
|
|
publish-core / publish:
packages/browser/src/addons/performance-issues.ts#L116
'getWebVitalRatingThresholds' was used before it was defined
|
|
publish-core / publish:
packages/browser/src/addons/performance-issues.ts#L109
Missing JSDoc @param "webVitalsOptions" description
|
|
|
|
|
|
|
|
|
|
|
|
publish-javascript / publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
publish-javascript / publish:
packages/browser/src/catcher.ts#L227
Missing JSDoc @param "settings" description
|
|
publish-javascript / publish:
packages/browser/src/addons/performance-issues.ts#L356
Missing JSDoc @param "webVitalsOptions" description
|
|
publish-javascript / publish:
packages/browser/src/addons/performance-issues.ts#L331
'supportsEntryType' was used before it was defined
|
|
publish-javascript / publish:
packages/browser/src/addons/performance-issues.ts#L116
'getWebVitalRatingThresholds' was used before it was defined
|
|
publish-javascript / publish:
packages/browser/src/addons/performance-issues.ts#L109
Missing JSDoc @param "webVitalsOptions" description
|
|
|
|
|
|
|
|
|
|
|
|
notify
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, codex-team/action-codexbot-notify@v1, codex-team/action-nodejs-package-info@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
notify
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
notify
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
notify
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
notify
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
notify
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|