Skip to content

Release

Release #560

Manually triggered September 13, 2023 14:01
Status Success
Total duration 22m 46s
Artifacts 10
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

release.yml

on: workflow_dispatch
Matrix: builds
Release publication
0s
Release publication
Docker build and push
0s
Docker build and push
Fit to window
Zoom out
Zoom in

Annotations

56 warnings
Code checks
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Doc generation
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Doc generation
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
Doc generation
Target filter specified, but no targets matched. This is a no-op
Doc generation: commons/zenoh-protocol/src/core/whatami.rs#L28
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/whatami.rs#L29
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/whatami.rs#L30
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/resolution.rs#L30
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/resolution.rs#L31
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/resolution.rs#L32
`&` without an explicit lifetime name cannot be used here
Doc generation: commons/zenoh-protocol/src/core/resolution.rs#L33
`&` without an explicit lifetime name cannot be used here
Doc generation
`zenoh-protocol` (lib) generated 7 warnings (run `cargo fix --lib -p zenoh-protocol` to apply 7 suggestions)
Build for aarch64-unknown-linux-musl on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for arm-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for x86_64-unknown-linux-musl on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/fraction/fraction-0.13.1.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/form_urlencoded/form_urlencoded-1.2.0.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/fnv/fnv-1.0.7.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/flume/flume-0.10.14.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/fixedbitset/fixedbitset-0.4.2.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/filepath/filepath-0.1.2.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/fastrand/fastrand-1.9.0.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/erased-serde/erased-serde-0.3.28.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/dirs-sys/dirs-sys-0.4.1.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/dirs/dirs-5.0.1.crate` (146.75.30.137), got 502
Build for x86_64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for aarch64-apple-darwin on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for arm-unknown-linux-gnueabi on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for armv7-unknown-linux-gnueabihf on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for x86_64-apple-darwin on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for aarch64-unknown-linux-gnu on ubuntu-20.04
The next version of cargo-deb will add a "-1" suffix to versions.
Build for x86_64-pc-windows-msvc on windows-2019
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/arrayvec/arrayvec-0.5.2.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/home/home-0.5.5.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/hmac/hmac-0.12.1.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/hmac/hmac-0.10.1.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/hkdf/hkdf-0.10.0.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/hex/hex-0.4.3.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/hashbrown/hashbrown-0.13.2.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/arrayref/arrayref-0.3.7.crate` (146.75.30.137), got 502
Build for x86_64-pc-windows-msvc on windows-2019
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/array-init/array-init-2.1.0.crate` (146.75.30.137), got 502

Artifacts

Produced during runtime
Name Size
aarch64-apple-darwin Expired
7.4 MB
aarch64-unknown-linux-gnu Expired
14.9 MB
aarch64-unknown-linux-musl Expired
10.7 MB
arm-unknown-linux-gnueabi Expired
15 MB
arm-unknown-linux-gnueabihf Expired
15.2 MB
armv7-unknown-linux-gnueabihf Expired
14.9 MB
x86_64-apple-darwin Expired
7.93 MB
x86_64-pc-windows-msvc Expired
6.83 MB
x86_64-unknown-linux-gnu Expired
15.7 MB
x86_64-unknown-linux-musl Expired
11.1 MB