Update all gtk crates to 18.x #5751
Annotations
24 warnings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, jetli/[email protected], actions-rs/toolchain@v1, Swatinem/rust-cache@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
wasm-pack build examples
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
wasm-pack build examples:
druid/examples/web/src/examples/multiwin.rs#L18
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/disabled.rs#L21
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/switches.rs#L18
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/timer.rs#L18
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/layout.rs#L19
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/invalidation.rs#L19
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/scroll.rs#L19
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/list.rs#L18
crate-level attribute should be in the root module
|
wasm-pack build examples:
druid/examples/web/src/examples/anim.rs#L25
crate-level attribute should be in the root module
|
cargo test compile book examples
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
install stable toolchain
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/
|
install stable toolchain
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/
|
install stable toolchain
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/
|
install stable toolchain
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 test compile druid-shell
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
restore cache
The `save-state` 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/
|
restore cache
The `save-state` 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/
|
restore cache
The `save-state` 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/
|
restore cache
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 test compile druid
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
cargo clippy druid-shell (wasm)
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
wasm-pack build hello_web example
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
The logs for this run have expired and are no longer available.
Loading