Repository navigation
Conversation
mwolson
force-pushed
the
contrib/background-relay-configuration
branch
from
October 22, 2026 03:11
94e947b to
937df33
Compare
mwolson
force-pushed
the
contrib/background-relay-configuration
branch
2 times, most recently
from
October 24, 2026 00:11
de286ea to
ae629fb
Compare
mwolson
force-pushed
the
contrib/background-relay-configuration
branch
from
October 24, 2026 00:38
ae629fb to
c328361
Compare
mwolson
force-pushed
the
contrib/background-relay-configuration
branch
from
October 24, 2026 16:10
c328361 to
b478f4e
Compare
Carries pingdotgg#16618 background-relay-configuration by jakeleventhal (Jake Leventhal). Mobile background registration, device listing, Live Activities and activity snapshots use an optional separate relay with its own token cache. Servers can override the background publish destination, credential and issuer while retaining the activity sharing switch and existing T3 Connect configuration. Invalid overrides fail without primary-relay fallback. Drop this layer at the refresh after pingdotgg#16618 background-relay-configuration merges upstream.
mwolson
force-pushed
the
contrib/background-relay-configuration
branch
from
October 29, 2026 11:33
b478f4e to
9ccef31
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
Carries pingdotgg#16618 background-relay-configuration by jakeleventhal. Mobile background registration, device listing, Live Activities and activity snapshots can use an optional separate relay with its own token cache. Servers can override the background publish destination, credential and issuer while keeping the activity sharing switch and the existing T3 Connect configuration. Invalid overrides fail instead of falling back to the primary relay.
Why
The personal relay layers above need a background destination separate from T3 Connect. Drop this layer at the refresh after pingdotgg#16618 background-relay-configuration merges upstream.
Checklist