You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we merged: #37
We are using "latest" release and not master.
We expect that when rust release a new version and updates master, that won't break other tests (because we only test releases known by libp2p/test-plans).
BUT we do use a master definition in the Cargo file, this is how we deal with multiple versions:
the worfklow started to fail in go-libp2p, here is an example of a run:
https://github.com/libp2p/go-libp2p/actions/runs/3047048099/jobs/4910594908
Raised by @marten-seemann
We need to investigate, my first intuition:
Now that we merged: #37
We are using "latest" release and not master.
We expect that when rust release a new version and updates
master
, that won't break other tests (because we only test releases known bylibp2p/test-plans
).BUT we do use a
master
definition in the Cargo file, this is how we deal with multiple versions:test-plans/ping/rust/Cargo.toml
Line 27 in 520162a
That line will break if the package is bumped to version 0.49 because it will try to load the repo and won't find the 0.48 version.
We might need to drop this line and use a rewrite in the
master
group.The text was updated successfully, but these errors were encountered: