Repository navigation
chore: pin ote-events v0.8.2 instead of v0.6.0 - #14
Merged
Merged
Conversation
Two feature releases behind. Every attribute and property the reader uses — layout, group-events, fields-preview, fields-detail, show-past, sort, event-actions, theme, plus events/eventActions/eventClassName/eventBadges — is unchanged in 0.8.2, checked against the widget's source rather than its changelog. What the bump is actually for: dompurify 3.4.14 → 3.4.17 on the path every feed-supplied string takes to the DOM; non-ASCII ids and URLs surviving the render path unencoded, which matters for a reader whose feeds are Spanish; and an http:// image on this https page falling back to the placeholder instead of leaving a broken frame. It does not bring the 0.5/0.6 spec fields: the widget targets OTE 0.4.0 (oteSpecVersion in its package.json), so speakers, recordings, contributing and D032 pricing are still unrendered whatever version is pinned. Tracked in #13. Verified in a browser against the four registered feeds in cards, list and calendar views: 200 upcoming events render, no console errors. Refs #13 Co-Authored-By: Claude Opus 5 <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
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.
First item off #13.
The reader pinned
<ote-events>v0.6.0 while the widget is at v0.8.2.Checked the widget's source, not its changelog: every attribute and
property the reader uses (
layout,group-events,fields-preview,fields-detail,show-past,sort,event-actions,theme, andevents/eventActions/eventClassName/eventBadges) is unchangedin 0.8.2.
What the bump is for:
dompurify3.4.14 → 3.4.17 — the sanitizer every feed-supplied stringpasses through before reaching the DOM.
ids and URLs survive the render path unencoded. Relevant here:the registered feeds are Spanish.
http://image on thishttpspage falls back to the placeholderinstead of leaving a broken frame.
What it does not bring: the 0.5/0.6 spec fields. The widget targets OTE
0.4.0 (
oteSpecVersionin itspackage.json), sospeakers,recordings,contributingand D032 pricing stay unrendered whateverversion is pinned here. That is upstream work, tracked in #13.
Verified in a browser against the four registered feeds in cards, list and
calendar views: 200 upcoming events render, no console errors.
🤖 Generated with Claude Code