supabase / supabase-swift / 37469822501
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 149
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 90.132% (-0.008%) from 90.14%
37469822501

push

github

web-flow 
ci: test against Xcode 27.0 alongside 26.4 (#1433)

* ci: test against Xcode 27.0 alongside 26.4

Blacksmith's macos-latest runner now ships Xcode 27.0 (/Applications/Xcode_27.0.app)
alongside 26.4, so add it to the macOS test matrix for early coverage.

* fix(ci): unblock the Xcode 27.0 matrix leg and dedupe Coveralls uploads

Supabase.xcworkspace's lock file still pinned swift-custom-dump 1.3.3,
swift-case-paths 1.9.2, and xctest-dynamic-overlay 1.5.1 - versions that
predate those packages' own split onto swift-issue-reporting for
Swift 6.4+. Under Xcode 27's Swift 6.4 toolchain, our root manifest pulls
in swift-issue-reporting directly while swiftui-navigation (an Examples-only
dependency) still required the old xctest-dynamic-overlay target literally
named IssueReporting, so SwiftPM saw two packages declaring the same target
name and xcodebuild's package resolution failed outright. Bumping those three
pins (and letting swift-issue-reporting join the lock) resolves cleanly under
both Xcode 26.4 and 27.0 - verified locally with both toolchains installed.

Also gate the coverage-export/Coveralls step to the 26.4 leg only, since the
Coveralls action isn't configured for parallel/matrix uploads (no
`parallel: true` or unique `flag-name`) and would otherwise upload coverage
twice per run now that the xcode matrix has two entries.

* fix(ci): keep swift-case-paths at 1.9.2 to unbreak the Examples build

Bumping swift-case-paths to 1.10.0 (as a side effect of clearing the stale
pin that caused the Xcode 27 IssueReporting clash) broke the Examples
scheme: swiftui-navigation 1.5.5 is written against case-paths' concrete
AnyCasePath<Enum, Case> type, which 1.10.0 replaced with an existential
`any CasePath<Enum, Case>`.

swift-case-paths was never part of the IssueReporting collision (its
manifest only depends on swift-syntax, no xctest-dynamic-overlay/
swift-issue-reporting involvement), so pinning it back to 1.9.2 is safe.
Verified locally: the Examples sch... (continued)

10805 of 11988 relevant lines covered (90.13%)

895743.07 hits per line

Coverage Regressions

Lines Coverage ∆ File
4
79.28
-1.02% Sources/Realtime/WebSocket/URLSessionWebSocket.swift
Jobs
ID Job ID Ran Files Coverage
1 37469822501.1 149
90.13
GitHub Action Run
Source Files on build 37469822501