chore(CI): validate Cargo lock file #2309
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
borngraced
previously approved these changes
Dec 27, 2024
onur-ozkan
requested changes
Dec 27, 2024
.github/workflows/fmt-and-lint.yml
Outdated
There was a problem hiding this comment.
I would create separate pipeline for checking Cargo.lock
.github/workflows/fmt-and-lint.yml
Outdated
Comment on lines
32
to
33
| - name: Backup Cargo.lock | ||
| run: cp Cargo.lock Cargo.lock.bak |
There was a problem hiding this comment.
We could simply run cargo update -w --locked which will fail if Cargo.lock isn't up-to-date.
There was a problem hiding this comment.
Cool, does the job!
https://github.com/KomodoPlatform/komodo-defi-framework/actions/runs/12526268691/job/34938647572
Adding web-time v1.1.0
error: the lock file /home/runner/work/komodo-defi-framework/komodo-defi-framework/Cargo.lock needs to be updated but --locked was passed to prevent this
commit 4d83f94
laruh
force-pushed
the
ci-check-cargo-lock
branch
from
3fb42e3 to
4d83f94
Compare
onur-ozkan
reviewed
Dec 30, 2024
Comment on lines
10
to
24
| name: Validate Cargo.lock Consistency | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v3 | ||
|
|
||
| - name: Install Rust toolchain | ||
| run: | | ||
| rustup toolchain install nightly-2023-06-01 --no-self-update --profile=minimal | ||
| rustup default nightly-2023-06-01 | ||
|
|
||
| - name: Validate Cargo.lock | ||
| run: | | ||
| echo "Checking if Cargo.lock is up-to-date..." | ||
| cargo update -w --locked |
There was a problem hiding this comment.
to simplify:
Suggested change
| name: Validate Cargo.lock Consistency | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Checkout repository | |
| uses: actions/checkout@v3 | |
| - name: Install Rust toolchain | |
| run: | | |
| rustup toolchain install nightly-2023-06-01 --no-self-update --profile=minimal | |
| rustup default nightly-2023-06-01 | |
| - name: Validate Cargo.lock | |
| run: | | |
| echo "Checking if Cargo.lock is up-to-date..." | |
| cargo update -w --locked | |
| name: Checking Cargo.lock file | |
| runs-on: ubuntu-latest | |
| steps: | |
| uses: actions/checkout@v3 | |
| - name: Validate Cargo.lock | |
| run: cargo update -w --locked |
There was a problem hiding this comment.
Do we really need to skip rustup toolchain install step?
There was a problem hiding this comment.
We could as cargo update will trigger that already.
onur-ozkan
approved these changes
Jan 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.