Skip to content

feat: add deprecate command with custom reason #10814

feat: add deprecate command with custom reason

feat: add deprecate command with custom reason #10814

Triggered via pull request April 17, 2026 08:49
Status Success
Total duration 3m 56s
Artifacts

ci.yml

on: pull_request
🔠 Lint project
27s
🔠 Lint project
💪 Type check
1m 20s
💪 Type check
🧪 Unit tests
49s
🧪 Unit tests
🧪 Component tests
2m 16s
🧪 Component tests
🖥️ Browser tests
3m 52s
🖥️ Browser tests
🧹 Unused code check
45s
🧹 Unused code check
🌐 i18n validation
22s
🌐 i18n validation
Matrix: ♿ Accessibility audit
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
eslint(no-shadow): app/components/Package/DeprecatePackageModal.vue#L62
'message' is already declared in the upper scope.
eslint(no-shadow): app/components/Package/DeprecatePackageModal.vue#L40
'v' is already declared in the upper scope.
regexp(no-unused-capturing-group): server/utils/readme.ts#L561
Capturing group number 1 is defined but never used.
eslint(no-shadow): app/composables/useSelectedPackageManager.ts#L16
'pm' is already declared in the upper scope.
🧪 Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: codecov/test-results-action@0fa95f0e1eeaafde2c782583b36b28ad0d8c77d3. 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/
🧪 Unit tests
This action is being deprecated in favor of 'codecov-action'. Please update CI accordingly to use 'codecov-action@v5' with 'report_type: test_results'. The 'codecov-action' should and can be run at least once for coverage and once for test results