Bump cookie and express in /example-projects/reqwest-wasm-example #474
dependabot[bot]Annotations
153 warnings
|
stable / wasm32-unknown-unknown
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
stable / wasm32-unknown-unknown
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
stable / wasm32-unknown-unknown
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/
|
|
stable / wasm32-unknown-unknown
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/
|
|
stable / wasm32-unknown-unknown
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/
|
|
stable / wasm32-unknown-unknown
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/
|
|
nightly / wasm32-wasi
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
nightly / wasm32-wasi
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
nightly / wasm32-wasi
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/
|
|
nightly / wasm32-wasi
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/
|
|
nightly / wasm32-wasi
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/
|
|
nightly / wasm32-wasi
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/
|
|
nightly / wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
nightly / wasm32-wasi
`wasi` (lib) generated 1 warning
|
|
nightly / wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`equivalent` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`unicode-ident` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`hashbrown` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`serde_spanned` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`proc-macro2` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`aho-corasick` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
nightly / wasm32-wasi
`cfg-if` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`wasi` (lib) generated 1 warning
|
|
nightly / wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`byteorder` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`pin-project-lite` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`memchr` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`bytes` (lib) generated 1 warning (1 duplicate)
|
|
nightly / wasm32-wasi
`futures-sink` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
stable / wasm32-wasi
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
stable / wasm32-wasi
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/
|
|
stable / wasm32-wasi
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/
|
|
stable / wasm32-wasi
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/
|
|
stable / wasm32-wasi
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/
|
|
stable / wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
stable / wasm32-wasi
`wasi` (lib) generated 1 warning
|
|
stable / wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`equivalent` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`unicode-ident` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`hashbrown` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`indexmap` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`aho-corasick` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`serde_spanned` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
stable / wasm32-wasi
`byteorder` (lib) generated 1 warning
|
|
stable / wasm32-wasi
`cfg-if` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`wasi` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`pin-project-lite` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`memchr` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`bytes` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`futures-sink` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
stable / wasm32-wasi
`byteorder` (lib) generated 1 warning
|
|
stable / wasm32-wasi
`cfg-if` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`wasi` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`pin-project-lite` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`memchr` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`bytes` (lib) generated 1 warning (1 duplicate)
|
|
stable / wasm32-wasi
`quick-error` (lib) generated 1 warning (1 duplicate)
|
|
nightly / x86_64-unknown-linux-gnu
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
nightly / x86_64-unknown-linux-gnu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
nightly / x86_64-unknown-linux-gnu
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/
|
|
nightly / x86_64-unknown-linux-gnu
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/
|
|
nightly / x86_64-unknown-linux-gnu
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/
|
|
nightly / x86_64-unknown-linux-gnu
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/
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L246
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L247
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L247
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L248
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
|
|
nightly / x86_64-unknown-linux-gnu:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
|
|
nightly / wasm32-unknown-unknown
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
nightly / wasm32-unknown-unknown
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
nightly / wasm32-unknown-unknown
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/
|
|
nightly / wasm32-unknown-unknown
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/
|
|
nightly / wasm32-unknown-unknown
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/
|
|
nightly / wasm32-unknown-unknown
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/
|
|
nightly / x86_64-unknown-linux-musl
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
nightly / x86_64-unknown-linux-musl
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
nightly / x86_64-unknown-linux-musl
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/
|
|
nightly / x86_64-unknown-linux-musl
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/
|
|
nightly / x86_64-unknown-linux-musl
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/
|
|
nightly / x86_64-unknown-linux-musl
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/
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L246
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L247
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L247
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L248
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
nightly / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
nightly / x86_64-unknown-linux-musl:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
|
|
nightly / x86_64-unknown-linux-musl:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
|
|
stable / x86_64-unknown-linux-musl
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
stable / x86_64-unknown-linux-musl
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
stable / x86_64-unknown-linux-musl
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/
|
|
stable / x86_64-unknown-linux-musl
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/
|
|
stable / x86_64-unknown-linux-musl
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/
|
|
stable / x86_64-unknown-linux-musl
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/
|
|
stable / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L246
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L247
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L247
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L248
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-musl:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-musl:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
|
|
stable / x86_64-unknown-linux-musl:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
|
|
stable / x86_64-unknown-linux-gnu
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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/
|
|
stable / x86_64-unknown-linux-gnu
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L54
static `CLOUDEVENTS_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L56
static `CONTENT_TYPE` is never used
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L58
function `header_prefix` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 4 warnings
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 1 warning
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 1 warning
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 1 warning
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L246
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L247
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v03/attributes.rs#L252
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L247
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L248
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::DateTime::<Tz>::from_utc`: Use TimeZone::from_utc_datetime() or DateTime::from_naive_utc_and_offset instead
|
|
stable / x86_64-unknown-linux-gnu:
src/event/v10/attributes.rs#L253
use of deprecated associated function `chrono::NaiveDateTime::from_timestamp`: use `DateTime::from_timestamp` instead
|
|
stable / x86_64-unknown-linux-gnu:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
|
|
stable / x86_64-unknown-linux-gnu:
src/test/fixtures/mod.rs#L48
use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 1 warning
|
|
stable / x86_64-unknown-linux-gnu:
src/binding/mod.rs#L55
static `CLOUDEVENTS_BATCH_JSON_HEADER` is never used
|
|
stable / x86_64-unknown-linux-gnu
`cloudevents-sdk` (lib) generated 1 warning
|
|
stable / x86_64-unknown-linux-gnu
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/
|
|
stable / x86_64-unknown-linux-gnu
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/
|
|
stable / x86_64-unknown-linux-gnu
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/
|
|
stable / x86_64-unknown-linux-gnu
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/
|