27 Commits
Author SHA1 Message Date
Si Beaumont 97fd57437f Run CMake CI job in a matrix by supported Swift version (#141)
### Motivation:

The CMake CI job in this repo is running using `swift:6.0-jammy`, and
installs CMake from the distro package manager. It doesn't get a very
new CMake and is blocking #140.

We are also missing coverage of our actual supported Swift versions
(currently 6.2 through 6.4).

### Modifications:

Run CMake CI job in a matrix by supported Swift version

### Result:

Replace the CMake CI job running on 6.0 image, with a matrix running on
6.2, 6.3, and 6.4 images.
2026-11-20 10:17:25 +00:00
Rick Newton-Rogers e3be192d35 Migrate macOS build argument overrides to Swift version inputs (#123)
Motivation

* The shared `macos_tests.yml` workflow no longer accepts
  `xcode_16_2_build_arguments_override` and the `xcode_16_3` input is a
  no-op. Passing the removed input causes CI to fail.
* Older Xcodes are being removed from the runners; Swift version inputs
  are the replacement.

Modifications

* Replace `xcode_16_2/16_3_build_arguments_override` with
  `swift_6_1/6_2/6_3_build_arguments_override` carrying the same
  `-Xswiftc -Xfrontend -Xswiftc -require-explicit-sendable` value.

Result

* macOS CI passes again using the Swift version inputs.
2026-05-15 11:30:42 +02:00
Rick Newton-RogersandGeorge Barnett eb50cbd146 Drop Swift 6.0 (#119)
Motivation:

Swift 6.0 is no longer supported, we should bump the tools version and
remove it from our CI.

Modifications:

* Bump the Swift tools version to Swift 6.1
* Remove Swift 6.0 jobs where appropriate in main.yml, pull_request.yml

Result:

Code reflects our support window.

---------

Co-authored-by: George Barnett <gbarnett@apple.com>
2026-04-08 13:43:17 +01:00
Rick Newton-Rogers 317065bbda Enable Swift 6.3 jobs in CI (#118)
Motivation:

Swift 6.3 has been released, we should add it to our CI coverage.

Modifications:

Add additional Swift 6.3 jobs where appropriate in main.yml,
pull_request.yml

Result:

Improved test coverage.
2026-04-01 13:55:33 +01:00
Rick Newton-Rogers d1c97a8641 update actions/checkout from v4 to v6 (#116)
Motivation

* Following [GitHub's
announcement](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/),
Node 20 is being deprecated and runners will begin using Node 24 by
default starting March 4th, 2026. Node 20 will reach end-of-life in
April 2026.

Modifications

* Upgrade GitHub Actions to their latest versions to ensure
compatibility with Node 24.
* Replace `actions/checkout@v4` with `actions/checkout@v6` in all
workflow files.

Result

* Workflow files reference `actions/checkout@v6`.
2026-03-02 13:33:16 +00:00
Rick Newton-Rogers a0b1a7253f switch from main to 0.0.7 for swiftlang workflows (#114)
Motivation

* `@main` references to `swiftlang/github-workflows` are deprecated.

Modifications

* Replace `@main` with `@0.0.7` in all workflow files.

Result

* Workflow files reference a pinned version of
`swiftlang/github-workflows`.
2026-02-23 13:51:54 +00:00
Melissa Kilby 823291a67d chore: restrict GitHub workflow permissions - future-proof (#109)
See https://github.com/swiftlang/github-workflows/issues/167 for
additional context

This approach aligns with security best practices, as detailed in the
following documentation:

-
https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
-
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#defining-access-for-the-github_token-scopes
-
https://openssf.org/blog/2024/08/12/mitigating-attack-vectors-in-github-workflows/


The default GITHUB_TOKEN permissions are defined at the repository
level. This PR modifies the workflow-level overrides to conform to
OpenSSF best practices -> defense in depth.

Allow me to quote OpenSSF:

https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

> The highest score is awarded when the permissions definitions in each
workflow's yaml file are set as read-only at the top level and the
required write permissions are declared at the run-level.”

> Remediation steps
> - Set top-level permissions as read-all or contents: read as described
in GitHub's documentation.
> - Set any required write permissions at the job-level. Only set the
permissions required for that job; do not set permissions: write-all at
the job level.


Compare to the LLVM project:

Top-level: contents read, e.g.
https://github.com/swiftlang/llvm-project/blob/next/.github/workflows/build-ci-container-windows.yml#L3-L4
-> this makes it future-proof

Job-level: Allow write permissions as needed, e.g.
https://github.com/swiftlang/llvm-project/blob/next/.github/workflows/build-ci-container-windows.yml#L53-L58

Signed-off-by: Melissa Kilby <mkilby@apple.com>
2025-10-20 08:51:15 +01:00
Rick Newton-Rogers 348b60eb35 Enable Swift 6.2 jobs in CI (#107)
Motivation:

Swift 6.2 has been released, we should add it to our CI coverage.

Modifications:

Add additional Swift 6.2 jobs where appropriate in main.yml,
pull_request.yml

Result:

Improved test coverage.
2025-09-22 14:28:23 +01:00
Raphael 6bbdf5fb8b Enable release mode builds (#105)
### Motivation:

Some errors do not show up in debug builds. Enabling release mode builds
improves the CI coverage.

### Modifications:

Enable release mode builds for pull requests and scheduled builds on
main.

### Result:

Improved CI coverage.
2025-07-30 08:59:50 +01:00
Rafael CepedaandGeorge Barnett f702259812 Introduced -Xswiftc -Xfrontend flag to GA workflow. (#104)
Introduced -Xswiftc -Xfrontend flag to GA workflow. There were no
Sendability warnings to fix after this change.

---------

Co-authored-by: George Barnett <gbarnett@apple.com>
2025-06-20 12:57:05 +01:00
Rick Newton-Rogers bb75fd81b3 Drop Swift 5.9 (#102)
Motivation:

Swift 5.9 is no longer supported, we should bump the tools version and
remove it from our CI.

Modifications:

* Bump the Swift tools version to Swift 5.10
* Remove Swift 5.9 jobs where appropriate in main.yml, pull_request.yml

Result:

Code reflects our support window.
2025-04-29 15:32:34 +01:00
Rick Newton-Rogers 15fb892c05 Enable Swift 6.1 jobs in CI (#99)
Motivation:

Swift 6.1 has been released, we should add it to our CI coverage.

Modifications:

Add additional Swift 6.1 jobs where appropriate in main.yml,
pull_request.yml

Result:

Improved test coverage.
2025-04-14 10:47:03 +01:00
Rick Newton-Rogers d1b6295fef Enable macOS CI on pull requests (#98)
Motivation:

* Improve test coverage

Modifications:

Enable macOS CI to be run on pull request commits and make the use of
the nightly runner pool for main.yml jobs explicit.

Result:

Improved test coverage.
2025-04-01 17:41:09 +01:00
Rick Newton-Rogers 945d24b4c6 Enable macOS CI on merge to main and daily timer (#97)
Motivation:

* Improve test coverage
* Check test pass/fail status
* Monitor CI throughput

Modifications:

Enable macOS CI to be run on all merges to main and on a daily timer.

Result:

Improved test coverage run out-of-band at the moment so we can get a
feeling for if any changes need to be made in the repo or in the CI
pipelines to ensure timely and stable checks.
2025-03-28 15:12:04 +00:00
Rick Newton-Rogers 6578d7acfc Use centralized CMake checks (#96)
### Motivation:

We now have centrally-hosted CMake checks in the NIO repository which we
should use to reduce maintenance. The new checks also increase coverage
by performing a build with CMake as part of the checks.

### Modifications:

* Use the new workflow
* Commit formatting changes in the CMakeLists files from the new script
* Document how to update the CMakeLists files
* Remove the obsolete scripts

### Result:

Better CI coverage.
2025-03-17 11:15:52 +00:00
Rick Newton-Rogers 6cac4d424c Add static SDK CI workflow (#95)
Add static SDK CI workflow which runs on commits to PRs, merges to main
and daily on main.
2025-03-13 11:02:10 +00:00
Rick Newton-Rogers 9fb1b88a90 Rename nightly_6_1 params to nightly_next (#91)
Rename nightly_6_1 params to nightly_next; see
https://github.com/apple/swift-nio/pull/3122
2025-03-03 14:50:35 +00:00
Rick Newton-Rogers 82d28dbe21 CI use 6.1 nightlies (#87)
CI use 6.1 nightlies now that Swift development is happening in the 6.1
branch
2025-01-30 09:44:09 +00:00
Franz Busch c27bcbd7ec Update release.yml (#84)
Update the release.yml file with the latest label changes
2024-12-18 14:14:56 +01:00
Franz Busch 15a8a271b4 Aligning semantic version label check name (#82) 2024-11-28 12:47:15 +01:00
Rick Newton-RogersandCory Benfield e647aabfb8 unify scheduled and main yamls (#79)
Co-authored-by: Cory Benfield <lukasa@apple.com>
2024-11-15 11:17:47 +00:00
Franz Busch 892b611455 [CI] Enable Windows CI (#77)
# Motivation

We want to make sure our packages build on all supported platforms.

# Modification

This PR enabled the Windows CI.

# Result

Better test coverage in our package.
2024-10-23 10:43:11 +01:00
Rick Newton-Rogers 81ee7dc715 CI: concurrency=complete require-explicit-sendable (#76)
CI: concurrency=complete require-explicit-sendable

Motivation:

Adopt `-Xswiftc -strict-concurrency=complete -Xswiftc
-require-explicit-sendable` in CI to lock-in concurrency-safety wins.

Modifications:

Added strict flags to pull request and scheduled GHA CI on Swift 6.0.

Result:

CI should ensure we don't regress data-race safety on Swift 6.0.
2024-10-17 09:36:37 +01:00
Rick Newton-Rogers d016643222 Migrate to GitHub Actions reusable workflows (2) (#74)
* Prepare repo for new GHA checks

Motivation:

Migrate to GitHub Actions reusable workflows (2)

Modifications:

* Add GHA PR label checks
* Add GHA benchmarks checks
* Satisfy soundness checks

Result:

New soundness checks should be green and ready for adoption

* review comments
2024-10-15 13:04:58 +01:00
Peter Adams 9969712080 yamllint fixes (#73) 2024-10-14 11:43:24 +01:00
Rick Newton-RogersandFranz Busch 381bf08f8f Migrate to GitHub Actions reusable workflows (1) (#70)
* Migrate to GitHub Actions reusable workflows (1)

Motivation:

Migrate to GitHub Actions reusable workflows whilst keeping CI green.

Modifications:

As the first step in migrating to use GitHub actions this PR provides
the workflows which will be used in the future, at first in disabled
state so that we can keep CI green during the changeover.

Result:

Once this PR is merged we can:
* Enable the new CI
* In a future PR neutralize the old CI scripts
* Disable the old CI via GitHub
* In a future PR Delete the old CI scripts

* add scheduled GHA CI

* Update .github/workflows/pull_request.yml

Co-authored-by: Franz Busch <privat@franz-busch.de>

* review comments

---------

Co-authored-by: Franz Busch <privat@franz-busch.de>
2024-10-10 10:46:42 +01:00
Franz Busch 7b4b3c7a81 Add release.yml (#61) 2024-09-06 13:10:28 +01:00