[FEAT] Option to target specific tag/branch/commit of the QRMI - #186
Merged
Conversation
MatthieuMoreau0
requested review from
OkuyanBoga,
awennersteen and
ohtanim
as code owners
April 20, 2026 09:31
…en building spank plugin
MatthieuMoreau0
force-pushed
the
mm/option-target-qrmi-tag
branch
from
April 20, 2026 09:34
38a3093 to
8865cc3
Compare
ohtanim
approved these changes
Apr 20, 2026
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
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.
Description of Change
In this MR I add a new optional flag to target a specific tag/branch/commit of the QRMI when building the spank plugin instead of the main branch (left as default).
Pinning the QRMI version used during the build makes the resulting plugin binary reproducible and prevents unexpected breakage from upstream changes on
main.Checklist ✅
Ticket