chore(deps): update rust crate clap_complete to v4.6.0 - autoclosed #366
docker.yml
on: pull_request
Cargo and npm build
12m 50s
Annotations
47 warnings
|
Cargo and npm build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, actions-rs/toolchain@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/
|
|
Cargo and npm build:
src/cli/generator/dockerfile.rs#L28
fields `name`, `base_image`, and `commands` are never read
|
|
Cargo and npm build:
src/cli/generator/dockerfile.rs#L22
field `stages` is never read
|
|
Cargo and npm build:
src/cli/config_parser.rs#L792
function `resolve_env_vars` is never used
|
|
Cargo and npm build:
src/helpers/dockerhub.rs#L73
type `helpers::dockerhub::Tag` is more private than the item `OfficialRepoResults::results`
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/console/commands/cli/destroy.rs#L6
unused import: `CommandOutput`
|
|
Cargo and npm build:
src/cli/deployment_lock.rs#L6
unused import: `DeployTarget`
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
Unexpected input(s) 'command', 'args', valid inputs are ['toolchain', 'target', 'default', 'override', 'profile', 'components']
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
Unexpected input(s) 'command', 'args', valid inputs are ['toolchain', 'target', 'default', 'override', 'profile', 'components']
|
|
Cargo and npm build:
src/cli/config_parser.rs#L792
function `resolve_env_vars` is never used
|
|
Cargo and npm build:
src/helpers/dockerhub.rs#L73
type `helpers::dockerhub::Tag` is more private than the item `OfficialRepoResults::results`
|
|
Cargo and npm build:
src/mcp/protocol_tests.rs#L3
unused import: `super::*`
|
|
Cargo and npm build:
src/cli/generator/compose.rs#L354
unused imports: `AppSource`, `DeployConfig`, and `SslMode`
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/console/commands/cli/destroy.rs#L6
unused import: `CommandOutput`
|
|
Cargo and npm build:
src/cli/deployment_lock.rs#L6
unused import: `DeployTarget`
|
|
Cargo and npm build:
src/cli/generator/dockerfile.rs#L28
fields `name`, `base_image`, and `commands` are never read
|
|
Cargo and npm build:
src/cli/generator/dockerfile.rs#L22
field `stages` is never read
|
|
Cargo and npm build:
src/cli/config_parser.rs#L792
function `resolve_env_vars` is never used
|
|
Cargo and npm build:
src/helpers/dockerhub.rs#L73
type `helpers::dockerhub::Tag` is more private than the item `OfficialRepoResults::results`
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/mod.rs#L22
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/routes/marketplace/mod.rs#L6
ambiguous glob re-exports
|
|
Cargo and npm build:
src/console/commands/cli/destroy.rs#L6
unused import: `CommandOutput`
|
|
Cargo and npm build:
src/cli/deployment_lock.rs#L6
unused import: `DeployTarget`
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
Cargo and npm build
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/
|
|
StackerDB Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
|
|
CICD Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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 | |
|---|---|---|---|
|
artifact-linux-docker
|
15.5 MB |
sha256:35468e2307ea24276ab8e1a9e1fe370cd1491fce2a615f539e54cf3bc2ea2bc8
|
|
|
trydirect~stacker~2FHBOD.dockerbuild
|
47.9 KB |
sha256:fc3e877ba3bde52cacb95536a2291a50a05cc87e9cb7a8eb3786a8f72e176aeb
|
|
|
trydirect~stacker~79QT9E.dockerbuild
|
95.6 KB |
sha256:97feb56eb9540ba130b8342893931c2440319d5cca1ada41328f3de67a29bc98
|
|