Thomas Eizinger 0c85839dab
.github/workflows: Refactor CI jobs (#3090)
We refactor our continuous integration workflow with the following goals in mind:

- Run as few jobs as possible
- Have the jobs finish as fast as possible
- Have the jobs redo as little work as possible

There are only so many jobs that GitHub Actions will run in parallel.
Thus, it makes sense to not create massive matrices but instead group
things together meaningfully.

The new `test` job will:

- Run once for each crate
- Ensure that the crate compiles on its specified MSRV
- Ensure that the tests pass
- Ensure that there are no semver violations

This is an improvement to before because we are running all of these
in parallel which speeds up execution and highlights more errors at
once. Previously, tests run later in the pipeline would not get run
at all until you make sure the "first" one passes.

We also previously did not verify the MSRV of each crate, making the
setting in the `Cargo.toml` rather pointless.

The new `cross` job supersedes the existing `wasm` job.

This is an improvement because we now also compile the crate for
windows and MacOS. Something that wasn't checked before.
We assume that checking MSRV and the tests under Linux is good enough.
Hence, this job only checks for compile-errors.

The new `feature_matrix` ensures we compile correctly with certain feature combinations.

`libp2p` exposes a fair few feature-flags. Some of the combinations
are worth checking independently. For the moment, this concerns only
the executor related transports together with the executor flags but
this list can easily be extended.

The new `clippy` job runs for `stable` and `beta` rust.

Clippy gets continuously extended with new lints. Up until now, we would only
learn about those as soon as a new version of Rust is released and CI would
run the new lints. This leads to unrelated failures in CI. Running clippy on with `beta`
Rust gives us a heads-up of 6 weeks before these lints land on stable.

Fixes #2951.
2022-11-18 11:04:16 +00:00

2.8 KiB

0.12.1 [Unreleased]

  • Update rust-version to reflect the actual MSRV: 1.60.0. See PR 3090.

0.12.0

  • Remove parallel dialing optimization, to avoid requiring the use of the ls command. See PR 2934.

0.11.0 [2022-01-27]

  • Migrate to Rust edition 2021 (see PR 2339).

0.10.4 [2021-11-01]

  • Implement From<io::Error> for ProtocolError instead of Into. PR 2169

0.10.3 [2021-03-17]

  • Update dependencies.

0.10.2 [2021-03-01]

  • Re-enable "parallel negotiation" if the dialer has 3 or more alternative protocols. PR 1934

0.10.1 [2021-02-15]

  • Update dependencies.

0.10.0 [2021-01-12]

  • Update dependencies.

0.9.1 [2020-12-02]

  • Ensure uniform outcomes for failed negotiations with both V1 and V1Lazy. PR 1871

0.9.0 [2020-11-25]

  • Make the V1Lazy upgrade strategy more interoperable with V1. Specifically, the listener now behaves identically with V1 and V1Lazy. Furthermore, the multistream-select protocol header is now also identical, making V1 and V1Lazy indistinguishable on the wire. The remaining central effect of V1Lazy is that the dialer, if it only supports a single protocol in a negotiation, optimistically settles on that protocol without immediately flushing the negotiation data (i.e. protocol proposal) and without waiting for the corresponding confirmation before it is able to start sending application data, expecting the used protocol to be confirmed with the response.

  • Fix the encoding and decoding of ls responses to be spec-compliant and interoperable with other implementations. For a clean upgrade, 0.8.4 must already be deployed.

0.8.5 [2020-11-09]

0.8.4 [2020-10-20]

0.8.3 [2020-10-16]

  • Fix a regression resulting in a panic with the V1Lazy protocol. PR 1783.

  • Fix a potential deadlock during protocol negotiation due to a missing flush, potentially resulting in sporadic protocol upgrade timeouts. PR 1781.

  • Update dependencies.

0.8.2 [2020-06-22]

  • Updated dependencies.