[ci] Roll pinned stable toolchain (#2480)

Author: google-pr-creation-bot

Cargo.toml

@@ -59,7 +59,7 @@ zerocopy-panic-in-const-and-vec-try-reserve-1-57-0 = "1.57.0"
 
 [package.metadata.ci]
 # The versions of the stable and nightly compiler toolchains to use in CI.
-pinned-stable = "1.85.1"
+pinned-stable = "1.86.0"
 pinned-nightly = "nightly-2025-03-31"
 
 [package.metadata.docs.rs]

tests/ui-stable/transmute-mut-src-dst-not-references.stderr

@@ -30,11 +30,6 @@ note: in edition 2024, the requirement `!: FromBytes` will fail
    |                                            ^^^^^^^^^^^^^^^^^^^^^^
    = note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
    = note: this warning originates in the macro `transmute_mut` (in Nightly builds, run with -Z macro-backtrace for more info)
-help: use `()` annotations to avoid fallback changes
-  --> src/macros.rs
-   |
-   |         let e: &mut () = $e;
-   |                     ~~
 
 warning: never type fallback affects this call to an `unsafe` function
   --> tests/ui-stable/transmute-mut-src-dst-not-references.rs:17:44

tests/ui-stable/transmute-mut-src-immutable.stderr

@@ -26,11 +26,6 @@ note: in edition 2024, the requirement `!: FromBytes` will fail
    |                      ^^^^^^^^^^^^^^^^^^^^
    = note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
    = note: this warning originates in the macro `transmute_mut` (in Nightly builds, run with -Z macro-backtrace for more info)
-help: use `()` annotations to avoid fallback changes
-  --> src/macros.rs
-   |
-   |         let e: &mut () = $e;
-   |                     ~~
 
 warning: never type fallback affects this call to an `unsafe` function
   --> tests/ui-stable/transmute-mut-src-immutable.rs:17:22

tests/ui-stable/transmute-mut-src-not-a-reference.stderr

@@ -30,11 +30,6 @@ note: in edition 2024, the requirement `!: FromBytes` will fail
    |                                      ^^^^^^^^^^^^^^^^^^^^^^
    = note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
    = note: this warning originates in the macro `transmute_mut` (in Nightly builds, run with -Z macro-backtrace for more info)
-help: use `()` annotations to avoid fallback changes
-  --> src/macros.rs
-   |
-   |         let e: &mut () = $e;
-   |                     ~~
 
 warning: never type fallback affects this call to an `unsafe` function
   --> tests/ui-stable/transmute-mut-src-not-a-reference.rs:17:38

tests/ui-stable/transmute-ref-src-dst-not-references.stderr

@@ -93,11 +93,6 @@ note: in edition 2024, the requirement `!: IntoBytes` will fail
    |                                       ^^^^^^^^^^^^^^^^^^^^^^
    = note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
    = note: this warning originates in the macro `transmute_ref` (in Nightly builds, run with -Z macro-backtrace for more info)
-help: use `()` annotations to avoid fallback changes
-  --> src/macros.rs
-   |
-   |         let e: &() = $e;
-   |                 ~~
 
 warning: never type fallback affects this call to an `unsafe` function
   --> tests/ui-stable/transmute-ref-src-dst-not-references.rs:17:39

tests/ui-stable/transmute-ref-src-not-a-reference.stderr

@@ -30,11 +30,6 @@ note: in edition 2024, the requirement `!: IntoBytes` will fail
    |                                  ^^^^^^^^^^^^^^^^^^^^^^
    = note: `#[warn(dependency_on_unit_never_type_fallback)]` on by default
    = note: this warning originates in the macro `transmute_ref` (in Nightly builds, run with -Z macro-backtrace for more info)
-help: use `()` annotations to avoid fallback changes
-  --> src/macros.rs
-   |
-   |         let e: &() = $e;
-   |                 ~~
 
 warning: never type fallback affects this call to an `unsafe` function
   --> tests/ui-stable/transmute-ref-src-not-a-reference.rs:17:34

zerocopy-derive/tests/ui-stable/union.stderr

@@ -68,7 +68,7 @@ warning: unexpected `cfg` condition name: `zerocopy_derive_union_into_bytes`
 39 | #[derive(IntoBytes)]
    |          ^^^^^^^^^
    |
-   = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
+   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
    = help: try referring to `IntoBytes` crate for guidance on how handle this unexpected cfg
    = help: the derive macro `IntoBytes` may come from an old version of the `zerocopy_derive` crate, try updating your dependency with `cargo update -p zerocopy_derive`

zerocopy-derive/tests/ui-stable/union_into_bytes_cfg/union_into_bytes_cfg.stderr

@@ -13,7 +13,7 @@ warning: unexpected `cfg` condition name: `zerocopy_derive_union_into_bytes`
 20 | #[derive(IntoBytes)]
    |          ^^^^^^^^^
    |
-   = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
+   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
    = help: try referring to `IntoBytes` crate for guidance on how handle this unexpected cfg
    = help: the derive macro `IntoBytes` may come from an old version of the `zerocopy_derive` crate, try updating your dependency with `cargo update -p zerocopy_derive`