Update nix requirement from 0.28.0 to 0.29.0 #898
ci.yml
on: pull_request
Run cargo fmt and cargo clippy
24s
Matrix: linux
Matrix: macos
Matrix: windows
Annotations
89 errors and 101 warnings
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
could not compile `open-coroutine-core` (lib) due to 2 previous errors
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on ubuntu-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
could not compile `open-coroutine-core` (lib) due to 2 previous errors
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest
The process '/Users/runner/.cargo/bin/cargo' failed with exit code 101
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-latest
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14
The process '/Users/runner/.cargo/bin/cargo' failed with exit code 101
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/mod.rs#L47
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14:
open-coroutine-core/src/coroutine/suspender.rs#L150
unexpected `cfg` condition value: `boost`
|
Test nightly on macos-14
could not compile `open-coroutine-core` (lib) due to 2 previous errors
|
Test nightly on macos-14
Process completed with exit code 101.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
The process 'C:\Users\runneradmin\.cargo\bin\cargo.exe' failed with exit code 101
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Process completed with exit code 1.
|
Test stable on macos-14
Process completed with exit code 101.
|
Test stable on ubuntu-latest
Process completed with exit code 101.
|
Test stable on macos-latest
The job running on runner GitHub Actions 20 has exceeded the maximum execution time of 360 minutes.
|
Test stable on macos-latest
The operation was canceled.
|
Run cargo fmt and cargo clippy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Run cargo fmt and cargo clippy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Run cargo fmt and cargo clippy
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/
|
Run cargo fmt and cargo clippy
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/
|
Run cargo fmt and cargo clippy
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/
|
Run cargo fmt and cargo clippy
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/
|
Test nightly on ubuntu-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test nightly on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
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/
|
Test nightly on ubuntu-latest
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/
|
Test nightly on ubuntu-latest
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/
|
Test nightly on ubuntu-latest
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/
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test nightly on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
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/
|
Test nightly on macos-latest
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/
|
Test nightly on macos-latest
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/
|
Test nightly on macos-latest
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/
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test nightly on macos-14
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
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/
|
Test nightly on macos-14
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/
|
Test nightly on macos-14
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/
|
Test nightly on macos-14
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/
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
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/
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
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/
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
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/
|
Test nightly-x86_64-pc-windows-gnu on windows-latest
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/
|
Test stable on macos-14
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test stable on macos-14
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
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/
|
Test stable on macos-14
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/
|
Test stable on macos-14
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/
|
Test stable on macos-14
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/
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-14
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
Test stable on ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@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/
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
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/
|
Test stable on ubuntu-latest
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/
|
Test stable on ubuntu-latest
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/
|
Test stable on ubuntu-latest
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/
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on ubuntu-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Test stable on macos-latest
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/
|
Test stable on macos-latest
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/
|
Test stable on macos-latest
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/
|
Test stable on macos-latest
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/
|