chore: bump signage-kit to 2026.8.6 - #19
Merged
Merged
Conversation
Uses the Screenly asset-metadata headers as a player signal. No app code changes: the Worker apps mount the profile route as (c) => playerProfileResponse(c.req.raw) and that helper is async now, which Hono accepts. - Presence of the X-Screenly-* headers names the vendor at high confidence. - X-Screenly-hardware fills player_model, which a Screenly UA never carries. - X-Screenly-version reports the player generation as player_sw_version, and is deliberately not wired into below_floor. - X-Screenly-hostname gives a stable per-device key as player_device, hashed to 128 bits inside the Worker so no raw device id reaches GA4. Premises-identifying metadata (screen name, location, coordinates, tags) is not parsed or reported. player_device exists because GA4's client_id lives in the _ga cookie and these players largely boot with fresh storage, so ids churn and totalUsers is not a device count. The three new dimensions are already registered in every property. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Bumps
@screenly-labs/signage-kitto 2026.8.6: the Screenly asset-metadata headers are now used as a player signal.No app code changes. The Worker apps mount the profile route as
(c) => playerProfileResponse(c.req.raw)and that helper is async now, which Hono accepts, so the version bump is the whole change.What lands
X-Screenly-*headers names the vendor at high confidence: the device states what it is, rather than the profiler inferring it from a UA string an integrator can strip.X-Screenly-hardwarefillsplayer_model, which a Screenly UA never carries.X-Screenly-versionreports the player generation asplayer_sw_version. Deliberately not wired intobelow_floor: a player generation says nothing about which Chromium it ships.X-Screenly-hostnamegives a stable per-device key asplayer_device, hashed to 128 bits inside the Worker so no raw device id reaches GA4. Premises-identifying metadata (screen name, location, coordinates, tags) is not parsed or reported.player_devicematters because GA4'sclient_idlives in the_gacookie and these players largely boot with fresh storage, so ids churn andtotalUsersis not a device count. The three new dimensions are already registered in every property.Only the 5 Worker apps can read request headers, and
send_metadatadefaults to off on the asset, soplayer_metadatameasures the covered share.Kit release: https://github.com/Screenly-Labs/signage-kit/releases/tag/2026.8.6
🤖 Generated with Claude Code