Two user-facing changes: a call blocked by a key change now says so
where it failed and can be settled there, and moving between wi-fi and
mobile data no longer costs a needless credential fetch in front of the
ringing.
get.leaf moves in the same commit. It states the version by hand, and
on 0.13 it was left behind: the page advertised the previous build to
anybody deciding whether to install. PublicPagesTests catches that, but
only if the full suite runs, and swift test prints the Swift Testing
summary after the XCTest one, so a green-looking tail can sit under a
real failure.
The self-hosting note is not boilerplate this time. This build reads a
reason the relay only began sending in 0.13; an older relay still works,
just more slowly when a phone changes network.
Two user-facing changes: a call blocked by a key change now says so
where it failed and can be settled there, and moving between wi-fi and
mobile data no longer costs a needless credential fetch in front of the
ringing.
`get.leaf` moves in the same commit. It states the version by hand, and
on 0.13 it was left behind: the page advertised the previous build to
anybody deciding whether to install. PublicPagesTests catches that, but
only if the full suite runs, and `swift test` prints the Swift Testing
summary after the XCTest one, so a green-looking tail can sit under a
real failure.
The self-hosting note is not boilerplate this time. This build reads a
reason the relay only began sending in 0.13; an older relay still works,
just more slowly when a phone changes network.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two user-facing changes: a call blocked by a key change now says so
where it failed and can be settled there, and moving between wi-fi and
mobile data no longer costs a needless credential fetch in front of the
ringing.
get.leafmoves in the same commit. It states the version by hand, andon 0.13 it was left behind: the page advertised the previous build to
anybody deciding whether to install. PublicPagesTests catches that, but
only if the full suite runs, and
swift testprints the Swift Testingsummary after the XCTest one, so a green-looking tail can sit under a
real failure.
The self-hosting note is not boilerplate this time. This build reads a
reason the relay only began sending in 0.13; an older relay still works,
just more slowly when a phone changes network.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
mentioned in commit
47ee6346f4