fix(contract build): use `--locked` when building contracts to ensure deps remain the same with the same `Cargo.lock`

Open Beginner friendly
#2,384 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
build-system, cli

Research direction

Start at the contract build entry point in stellar-cli and trace the Cargo command used to build contracts. Verify that the build uses --locked, then confirm that rebuilding with the same Cargo.lock keeps dependency resolution pinned.

Written by the indexing model from the issue text.

Description

What problem does your feature solve?

Improving contract build determinism so that deps are the same as long as the Cargo.lock remains the same.

This way anyone who wants to rebuild the contract in the future will use the pinned versions instead of potentially pulling in updated deps.

What would you like to see?
What alternatives are there?
Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.