[CI] Do not hard-code OCK version number#1002
Merged
Merged
Conversation
coldav
force-pushed
the
colin/fix_remote_hal
branch
10 times, most recently
from
65f0f5a to
926323e
Compare
As we are preparing for a 5.0 release, tests should not assume 4.0.
hvdijk
force-pushed
the
colin/fix_remote_hal
branch
from
926323e to
a663c59
Compare
hvdijk
changed the title
hvdijk
approved these changes
Sep 23, 2025
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
2 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.
Overview
[CI] Do not hard-code OCK version number.
Reason for change
As we are preparing for a 5.0 release, tests should not assume 4.0.
Description of change
Describe the intended behaviour your changes are meant to introduce to the
project and explain how they resolve the problem stated above. Detail any
relevant changes that may affect other users of the project, such as
compilation options, runtime flags, expected inputs and outputs, API entry
points, etc.
If you have added new testing, provide details on what tests you have added
and what the purpose of them is.
Anything else we should know?
If there's any other relevant information we should know that may help us in
understanding and verifying your patch, please include it here.
Checklist