Honor exact CLI releases in prospect benchmarks - #15
Open
gauravtiwari wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prospect CLI installation wrote its mise configuration in the workspace but installed from a different directory. An exact canary override could therefore install the stable release and fail executable resolution before the workload.
Use the same directory for configuration, installation, and executable resolution, pass the exact selected release to mise, and retain the selected tag with the CLI version evidence.
Validation: workflow lint; 57 benchmark tests, 367 assertions (3 existing integration skips); actual local canary installation with executable resolution and checksum matching the candidate manifest. Normal Ferrum fresh and rolling canaries are running on this branch.