Skip to content

Update CI to use setup-gap@v3#95

Merged
cdwensley merged 2 commits into
masterfrom
codex/update-ci
Jul 13, 2026
Merged

Update CI to use setup-gap@v3#95
cdwensley merged 2 commits into
masterfrom
codex/update-ci

Conversation

@fingolfin

Copy link
Copy Markdown
Member

Update the CI workflow to use current gap-actions releases, migrate legacy inputs, and standardize the GAP version matrix.

@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.91%. Comparing base (75f6635) to head (be2773e).

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #95      +/-   ##
==========================================
+ Coverage   85.21%   85.91%   +0.69%     
==========================================
  Files          32       32              
  Lines        1867     1867              
==========================================
+ Hits         1591     1604      +13     
+ Misses        276      263      -13     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This matches what CI tested before
@cdwensley
cdwensley merged commit 38e913f into master Jul 13, 2026
1 of 4 checks passed
@cdwensley
cdwensley deleted the codex/update-ci branch July 13, 2026 14:59
@fingolfin

Copy link
Copy Markdown
Member Author

@cdwensley CI for this was failing, this should not have been merged

@cdwensley

Copy link
Copy Markdown
Collaborator

@fingolfin Sorry - now reverted. I have received a whole string of CI emails for various packages, and assumed that they all needed to be merged.

@fingolfin

Copy link
Copy Markdown
Member Author

Sure but only if/when they pass. That's the entire point pf CI tests after all. Otherwise you might as well stop using them

@cdwensley

Copy link
Copy Markdown
Collaborator

My guess is that this PR should be reopened, but I cannot see how to do so.

@fingolfin

Copy link
Copy Markdown
Member Author

Can't be reopened, I'll make a fresh one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants