Skip to content

Realign the quic branch CI workflows with upstream - #23

Merged
ydnar merged 2 commits into
quicfrom
claude/quic-open-source-prep-f1ds5i
Aug 8, 2026
Merged

Realign the quic branch CI workflows with upstream#23
ydnar merged 2 commits into
quicfrom
claude/quic-open-source-prep-f1ds5i

Conversation

@ydnar

@ydnar ydnar commented Aug 7, 2026

Copy link
Copy Markdown

Motivation:

The quic branch carries CI edits that diverge from apple/swift-nio-ssl main for reasons that no longer hold or are already handled upstream. Each divergence shows up as a workflow hunk in the upstream proposal (apple#592), unrelated to the QUIC-TLS API under review there.

Modifications:

  • Restore the schedule: cron on the Main workflow, matching upstream. Scheduled workflows run from the repository's default branch, which on this fork is main and already carries the trigger, so this is parity rather than new scheduled activity on quic.
  • Re-enable the Linux nightly toolchains in the Unit tests workflow. The disable cited the nightly -warnings-as-errors / -suppress-warnings conflict, which upstream already avoids by dropping -warnings-as-errors from the nightly-main argument override. Restoring the upstream overrides runs nightly the same way upstream does.

The macos-test-fork job and the api_breakage_check_enabled: false line stay, as fork CI plumbing the fork still needs: a fork has no access to Apple's self-hosted macOS runner pool, and there is no stable baseline for the API-breakage check yet.

Result:

The Main and Unit tests workflow blocks on quic match upstream again, so the schedule and nightly hunks drop out of the upstream proposal (apple#592), leaving only the QUIC-TLS API plus the two intentional fork-CI differences. Nightly stays informational: an upstream compiler bug can still turn it red, which is accepted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Lo6DQFYJZY9HYuS6QTUpEr

The quic branch commented out the schedule cron on the Main workflow
under a CI-budget note, while apple/swift-nio-ssl main keeps it.
Restoring it realigns the `on:` block with upstream, so the trigger no
longer shows as a difference in the upstream proposal (apple#592).

Scheduled workflows run from the repository's default branch. On this
fork that is main, which already carries the trigger, so this is parity
with upstream rather than new scheduled activity on quic.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Lo6DQFYJZY9HYuS6QTUpEr
The quic branch disabled the Linux nightly toolchains in the Unit tests
workflow, while apple/swift-nio-ssl main runs them. The stated reason,
that nightly rejects combining -warnings-as-errors/-Wwarning with
-suppress-warnings, is already handled upstream: the nightly-main
argument override drops -warnings-as-errors for exactly that reason, so
nightly builds without the conflict.

Restore the upstream nightly argument overrides so the Unit tests `with:`
block matches upstream, removing the hunk from the upstream proposal
(apple#592). Nightly stays informational: an upstream compiler bug can still
turn it red, which is accepted.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Lo6DQFYJZY9HYuS6QTUpEr
@ydnar ydnar changed the title Restore the scheduled trigger on the Main workflow Realign the quic branch CI workflows with upstream Aug 7, 2026

@ydnar ydnar left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ydnar

ydnar commented Aug 8, 2026

Copy link
Copy Markdown
Author

Merge

@ydnar
ydnar marked this pull request as ready for review August 8, 2026 20:46
@ydnar
ydnar merged commit 7f3f847 into quic Aug 8, 2026
45 of 46 checks passed
@ydnar
ydnar deleted the claude/quic-open-source-prep-f1ds5i branch August 8, 2026 20:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants