CI repair

[jpgrayson]

• update testing certs (test certificates are expired #156)
• update to actions/checkout@v4 (resolves GitHub deprecation warning)
• add Swift 6.0 to test matrix

N.B. there remains a GitHub deprecation warning related to codecov/codecov-action@v2, which uses an out of date version of node. But to migrate to codecov/codecov-action@v4 requires setting up a codecov token as described here, which requires a repo admin permissions.

[adam-fowler]

I'm wondering if a better solution is to generate new certs in the GitHub action so they never expire for CI.

[adam-fowler]

Also codecov wasn't even enabled on this repo, when it got moved to swift-server-community. You might as well up the version number on the action and I'll see if I can fix it

[jpgrayson]

Added the change for codecov. You'll need to define a CODECOV_TOKEN secret as shown here:

https://docs.codecov.com/docs/adding-the-codecov-token

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.12%. Comparing base (e02e237) to head (441baeb).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #157      +/-   ##
==========================================
- Coverage   79.07%   78.12%   -0.96%     
==========================================
  Files          22       22              
  Lines        2518     1979     -539     
==========================================
- Hits         1991     1546     -445     
+ Misses        527      433      -94     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jpgrayson]

I'm wondering if a better solution is to generate new certs in the GitHub action so they never expire for CI.

That's an idea. Given the trouble I had with needing to use MacOS' libreSSL versus homebrew's OpenSSL, it might be that the generate-certs.sh script needs some tweaks to be more compatible with the different openssl implementations out there.

[jpgrayson]

bump @adam-fowler

I think this PR is ready to go. The updated codecov seems to be working. The CI failure is due to codecov detecting -0.96% less coverage, but the process itself seems to be working.

I was not planning on trying to do the CI-time cert generation in this PR.

[adam-fowler]

Done. Thanks for this @jpgrayson