Obtain Rust Toolchain automatically for e2e test config

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, rust
Domain
ci-cd, testing

Research direction

Start by locating the GHA e2e workflow config and reading Cargo.toml to compare the hardcoded Rust toolchain with the declared version. Update the workflow so it obtains the toolchain from Cargo.toml at runtime, and verify the e2e workflow uses that value rather than stable.

Written by the indexing model from the issue text.

Description

soroban-scrum
What problem does your feature solve?

hardocded rust toolchain version on gha e2e workflow config becomes stale

What would you like to see?

gha e2e workflow sources the rust toolchain dynamically from Cargo.toml instead at gha runtime.

What alternatives are there?

continue to hardcoding the value to stable

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.