Use --locked when building in CI (#31720)

Thus the build will immediately fail if a PR modifies Cargo.toml but
forgets to include the changes in Cargo.lock

This was previously checked by lockfile_changed.sh after building
normally, wasting resources.
This commit is contained in:
Oriol Brufau 2024-03-21 12:54:02 +01:00 committed by GitHub
parent ecabdc2583
commit ea62a5e24f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 4 additions and 19 deletions

View file

@ -85,7 +85,7 @@ jobs:
"$env:WIX\bin" >> $env:GITHUB_PATH
- name: Build (${{ inputs.profile }})
run: |
python mach build --${{ inputs.profile }}
python mach build --locked --${{ inputs.profile }}
cp C:\a\servo\servo\target\cargo-timings C:\a\servo\servo\target\cargo-timings-windows -Recurse
- name: Copy resources
run: cp D:\a\servo\servo\resources C:\a\servo\servo -Recurse