fix(ci): Do not use --exact-match when setting Noir versions for aztec-up bootstrap #19945
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.
If I want to test a patch in the Noir submodule against CI by altering
noir/noir-repodirectly rather than needing a new temporary tag it is currently not possible.When aztec-up fetchs the versions the
noir_versionexpects an exact match for the tag.This prevents being able to directly modify the submodule as no tag exists. I ran into this issue in #19871 where CI would fail with
fatal: no tag exactly matches '515b2702975fd85069fae48ddd0d90a56cd65628'ataztec-up/bootstrap.sh. This does not affect release builds as those are also protected in the Noir build.