docs: update setup and test docs with missing info #4567
Merged
Conversation
This file contains hidden or 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
cytadela8
approved these changes
Nov 4, 2025
Member
cytadela8
left a comment
cytadela8
left a comment
There was a problem hiding this comment.
cargo install cargo-nextest --version 0.9.109 --locked works, dev contracts is a dependency probably indeed. And older nextest seems needed:
cargo install cargo-nextest
Updating crates.io index
error: cannot install package `cargo-nextest 0.9.110`, it requires rustc 1.88 or newer, while the currently active rustc version is 1.87.0-nightly
`cargo-nextest 0.9.109` supports rustc 1.87
Deniallugo
approved these changes
Nov 14, 2025
Deniallugo
pushed a commit
that referenced
this pull request
Dec 17, 2025
## What ❔ Fixes the development setup docs to accurately reflect some missing information - cargo-nextest must be installed with `--version 0.9.109 --locked` as the latest version does not support rust 1.87 - `zkstack dev contracts` must be run before running unit tests <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ Accurate documentation is helpful for new and external contributors to be able to set up a working developer environment <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- The `Why` has to be clear to non-Matter Labs entities running their own ZK Chain --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Is this a breaking change? - [ ] Yes - [x] No ## Operational changes <!-- Any config changes? Any new flags? Any changes to any scripts? --> <!-- Please add anything that non-Matter Labs entities running their own ZK Chain may need to know --> None ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev lint`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What ❔
Fixes the development setup docs to accurately reflect some missing information
--version 0.9.109 --lockedas the latest version does not support rust 1.87zkstack dev contractsmust be run before running unit testsWhy ❔
Accurate documentation is helpful for new and external contributors to be able to set up a working developer environment
Is this a breaking change?
Operational changes
None
Checklist
zkstack dev fmtandzkstack dev lint.