Skip to content
CI

chore: Rename Component::name_in_manifest and short_name_in_manifest method to name and short_name #4202

Sign in to view logs

chore: Rename Component::name_in_manifest and short_name_in_manifest method to name and short_name

chore: Rename Component::name_in_manifest and short_name_in_manifest method to name and short_name #4202

Triggered via pull request March 26, 2026 18:23
@Cloud0310Cloud0310
opened #4778
Cloud0310:rename-method
Status Success
Total duration 28m 59s
Artifacts 9

ci.yaml

on: pull_request
Matrix: build-all-features
Matrix: build-linux-main
Matrix: build-linux-pr
Matrix: build-linux-stable
Matrix: build-macos-aarch64
Matrix: build-macos-x86_64
Matrix: build-windows-main
Matrix: build-windows-pr
Matrix: build-windows-stable
build-freebsd-main
0s
build-freebsd-main
build-freebsd-stable
0s
build-freebsd-stable
check
3m 18s
check
doc
5s
doc
conclusion
2s
conclusion
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build-windows-pr (release, x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1. 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/
build-windows-pr (release, aarch64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1. 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/
build-windows-pr (dev, x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1. 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/
build-windows-pr (dev, aarch64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1. 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/
build-all-features (windows-latest, x86_64-pc-windows-msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1. 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/

Artifacts

Produced during runtime
Name Size Digest
rustup-init-aarch64-apple-darwin Expired
4.7 MB
sha256:fc0512b1d737258faba4735639b4c52025fb57b308cb6f8cb2847215fb510409
rustup-init-aarch64-linux-android Expired
7.79 MB
sha256:9f8393eb1cd00547ce3b97ecb1f38bdff0a0542b00b35a919b8f274ba13ebd41
rustup-init-aarch64-pc-windows-msvc Expired
4.91 MB
sha256:7cec738a681c62c230830ad350011f75e82d9090179b2d50e1112dca920f388d
rustup-init-aarch64-unknown-linux-gnu Expired
7.79 MB
sha256:6b053aa76d4275c0aee9ac05f0dcf4918ff9365f94c489989a77b6db96dc0ed9
rustup-init-armv7-unknown-linux-gnueabihf Expired
6.54 MB
sha256:43945a15fd8d7941fff9b6ef23ba55e72cdc392fe8a0b09a31211a4591aa8fd1
rustup-init-x86_64-apple-darwin Expired
4.97 MB
sha256:9fdf9195aff5ba1e2776bdb933bea838582b07c81192e246674fba98593f5f34
rustup-init-x86_64-pc-windows-gnu Expired
5.61 MB
sha256:fd2ba1d25a1aaa97a33e1dfa2945d91a9cc33ecce2b7e8bd3f5377f1e98edc7d
rustup-init-x86_64-pc-windows-msvc Expired
5.05 MB
sha256:4a745baed44c414d2511ccb9b3431b1a7867dccb9bc0a369c664ae373965bdc4
rustup-init-x86_64-unknown-linux-gnu Expired
7.61 MB
sha256:04c68fb6c41bad712966335453b510c95b2b1b29c00643f6f3799dc9d207ce7d