Skip to content

Commit

Permalink
CI: cargo-update from the right directory
Browse files Browse the repository at this point in the history
Without this change, the patch.crates-io does not take, and we are
building with an old version; this primarily causes issues during
version updates when the version found through patch.crates-io at
runtime is recognized as the new one, but the lock file says to use the
released version, and in the end cargo falls back to not using the local
version.
  • Loading branch information
chrysn committed Mar 20, 2024
1 parent feb03d1 commit ab62128
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,10 @@ jobs:
# and all relevant crates once, and after that, just make some notes in Cargo.lock
run: |
set -x
for MANIF in $(find RIOT -name Cargo.toml)
# It is important to cd in early, for otherwise the patch.crates-io
# will not catch on during the update
cd RIOT
for MANIF in $(find -name Cargo.toml)
do
echo "::group::Updating ${MANIF}"
cargo update -p riot-sys -p riot-wrappers --aggressive --manifest-path $MANIF
Expand Down Expand Up @@ -105,7 +108,10 @@ jobs:
# and all relevant crates once, and after that, just make some notes in Cargo.lock
run: |
set -x
for MANIF in $(find RIOT -name Cargo.toml)
# It is important to cd in early, for otherwise the patch.crates-io
# will not catch on during the update
cd RIOT
for MANIF in $(find -name Cargo.toml)
do
echo "::group::Updating ${MANIF}"
cargo update -p riot-sys -p riot-wrappers --aggressive --manifest-path $MANIF
Expand Down

0 comments on commit ab62128

Please sign in to comment.