[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

shipdot@0.2.0

Minor Changes

• #42 1305bae Thanks @pipe1os! - Feed panel improvements: an "Earlier" divider between unread and read entries, an error message (with a retry) when src fails to load instead of a trigger that does nothing, and live re-rendering when a refresh or locale change happens while the panel is open. The built-in bell now has an accessible name before the feed loads. New UI strings: earlier, error.

• #37 e8290e5 Thanks @pipe1os! - The widget fetches src again when a tab comes back to the foreground 10 minutes or more after the last load, so tabs left open for days see new entries. Every fetch revalidates with the server (cache: 'no-cache'), so an unchanged feed costs a 304.

• #35 ddc75e9 Thanks @pipe1os! - Read state syncs across tabs and widgets. Reading entries in one tab clears the badge and hotspots in the others, and widgets on the same page with the same storage-key share read state and draw each hotspot once. Uses a BroadcastChannel named after the storage key, so it also works without localStorage. shipdot:read fires only in the widget where the entries were read.

Patch Changes

• #42 1305bae Thanks @pipe1os! - The badge, the unread dot and hotspot dots stay visible in forced colors mode (Windows High Contrast). Before, they were painted with the page background.

• #34 6e791a1 Thanks @pipe1os! - Hotspots follow targets that move without a scroll or resize, such as content inserted above them or a CSS transition. Reading one entry no longer rebuilds the other hotspots, so their pulse does not restart and an open tooltip stays open.

• #28 8510a37 Thanks @pipe1os! - markRead(ids) marks entries as read by ID, so an app with user accounts can sync read state across devices: store the IDs from shipdot:read on your server and pass them back. It can be called before the feed loads.

• #38 afe02f4 Thanks @pipe1os! - A popover opened above the trigger, and a hotspot tooltip opened above its target, no longer grow down over them when images finish loading. Hotspots pick up --shipdot-* properties and color-scheme the app changes after load, for example when it switches to dark mode with a class on <html>.

• #36 5836781 Thanks @pipe1os! - The popover closes when Tab moves focus out of it, and focus stays where it went. Before, it stayed open and a later Esc anywhere sent focus back to the trigger.

• #33 962cca3 Thanks @pipe1os! - Widget fixes and polish: the popover opens above the trigger when it does not fit below (bells in footers or bottom bars); hotspots hide when their target scrolls out of an inner scroll container; a slotted custom trigger gets aria-expanded and aria-haspopup; when src changes quickly, a slower earlier response no longer replaces the newer feed; the popover, modal and hotspot tooltip fade in (skipped with prefers-reduced-motion).

@shipdot/cli@0.2.0

Patch Changes

• #24 380b0d5 Thanks @pipe1os! - shipdot init prints import 'shipdot' instead of the CDN <script> when your package.json already depends on shipdot, and mentions the npm option otherwise.

• #24 380b0d5 Thanks @pipe1os! - shipdot draft: the ### shipdot section of a pull request now also ends at a horizontal rule (---), so footers that tools append to the description no longer leak into the in-app note.

• Updated dependencies [b3c79e6]:

  • @shipdot/core@0.2.0

@shipdot/core@0.2.0

Patch Changes

• #26 b3c79e6 Thanks @pipe1os! - stripHtmlComments finds comments with a linear-time scanner instead of the Markdown parser, which took quadratic time on deeply nested lists and block quotes: a 65 KB pull request body could stall shipdot draft and the GitHub Action for minutes. Comments are still removed the way GitHub renders them, and <!-- in code spans and code blocks is kept.