Skip to content

Conversation

@reubenmiller
Copy link
Contributor

Proposed changes

Recent changes in cargo-nextest (or cargo install) require cargo install to be called with --lock when installing the tool.

Without the --lock flag, the following error is displayed

error: Nextest does not support being installed without --locked. To install nextest from source, run:
       
       cargo install --locked cargo-nextest
       
       For more, see https://nexte.st/docs/installation/from-source/.
  --> /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/locked-tripwire-0.1.1002/src/lib.rs:5:1
   |
 5 | / compile_error!(
 6 | |     "Nextest does not support being installed without --locked. To install nextest from source, run:
 7 | |
 8 | | cargo install --locked cargo-nextest
 9 | |
10 | | For more, see https://nexte.st/docs/installation/from-source/.");
   | |________________________________________________________________^

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Discovered on a failed test run:

Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
  • I ran just format as mentioned in CODING_GUIDELINES
  • I used just check as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@reubenmiller reubenmiller requested review from a team as code owners January 26, 2026 10:44
@reubenmiller reubenmiller added the ci/cd Repository management and pipeline topics label Jan 26, 2026
Copy link
Contributor

@didier-wenzek didier-wenzek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@codecov
Copy link

codecov bot commented Jan 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link
Contributor

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
822 0 3 822 100 2h34m23.823747s

@reubenmiller reubenmiller added this pull request to the merge queue Jan 26, 2026
Merged via the queue into thin-edge:main with commit 4b025b6 Jan 26, 2026
34 checks passed
@reubenmiller reubenmiller deleted the dev-install-tools-cargo-lock branch January 26, 2026 11:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/cd Repository management and pipeline topics

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants