Regenerate CI workflows with xmsconan 2.15.5 - #128
Merged
Conversation
Brings xmscore in line with the rest of the suite: actions/checkout@v2 -> @v4 (v2 is deprecated) and the xmsconan pin moves 2.15.3 -> 2.15.5. Coverage.yaml deliberately stays on >= as the canary.
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.
Regenerates CI files with xmsconan 2.15.5 (was 2.15.3), bringing xmscore in line with the rest of the suite.
Changes
actions/checkout@v2→@v4(5 occurrences: 4 inXmsCore-CI.yaml, 1 inCoverage.yaml). v2 is deprecated — GitHub already force-runs its Node 20 actions on Node 24 and warns on v2.xmsconan==2.15.3→==2.15.5in every build/deploy/lint step.Coverage.yamlmovesxmsconan>=2.15.3→>=2.15.5, deliberately keeping>=as the canary..flake8is unchanged — nothing in it moved between 2.15.3 and 2.15.5.Why now
xmscore shipped 7.0.9 before two template bugs were found and fixed upstream:
checkout@v2, so regeneration reverted repos that had moved to v4.undefined needthat produced job-less pipelines (GitHub-only repos like this one were unaffected).This picks up both, so xmscore is no longer the one repo on the pre-fix template.
Verification
AQU codes are excluded because the GitHub flake job does not install flake8-aquaveo — that plugin is published only to the internal index (
aquapi.aquaveo.com, which resolves to 192.168.99.1 and is unreachable from GitHub-hosted runners), so this matches what CI actually runs.To be released as 7.0.10.