TheBoredTeam/boring.notch

Move project to Swift 6

Open

#1054 opened on Feb 25, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Swift (9,103 stars) (704 forks)batch import
help wanted

Description

Summary

Track the migration of the codebase to Swift 6, including language mode adoption, concurrency updates, dependency compatibility, and CI adjustments.

Swift 6 introduces stricter concurrency checking, enhanced Sendable enforcement, and changes that may surface previously ignored warnings as errors. This issue covers the required work to ensure full compatibility and a clean build under Swift 6 language mode.

Motivation

  • Align with the latest Swift language evolution
  • Maintain compatibility with the current Apple toolchain
  • Improve concurrency safety with stricter compile-time checks
  • Reduce technical debt by addressing warnings that will become errors

Contributor guide

Tech stack
swift
Domain
desktop
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Swift 5.9+Concurrency conceptsBuild system knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Explore the Swift 6 language mode adoption by reviewing the Swift Evolution proposals and migration guide. Check the current project's Swift version in Xcode project settings and Package.swift. Identify all compiler warnings that will become errors in Swift 6, especially related to concurrency and Sendable. Assess third party dependencies for Swift 6 compatibility. Plan incremental migration steps and consider creating sub issues for each module.