Skip to content

v1.13.0 documentation, changelog, blog post, and homepage updates#10

Merged
bensie merged 34 commits into
mainfrom
bensie/doc-latest-hotsock
May 20, 2026
Merged

v1.13.0 documentation, changelog, blog post, and homepage updates#10
bensie merged 34 commits into
mainfrom
bensie/doc-latest-hotsock

Conversation

@bensie
Copy link
Copy Markdown
Member

@bensie bensie commented May 18, 2026

Summary

  • Add v1.13.0 changelog entry covering message reactions, presence member pub/sub events, heartbeatTimeout claim, subscription cleanup improvements, and dependency bumps.
  • Add react directive documentation to claims (boolean or array-of-strings form), expandReactions on listMessages, and connection/listReactions endpoint to the Client HTTP API docs.
  • Add hotsock.messageReactionAdded, hotsock.messageReactionRemoved, hotsock.memberAdded, hotsock.memberRemoved, and hotsock.memberUpdated pub/sub event documentation.
  • Add heartbeatTimeout claim and uncomment the hotsock.heartbeat section in keep-alive docs.
  • Add release blog post and update homepage banner, hero pill, capabilities grid, and release cadence.
  • Normalize pub/sub event examples with consistent uid/umd sample data and hotsockVersion across the page.

Test plan

  • npm run build passes
  • Spot-check rendered pages for claims, events, client HTTP API, changelog, and blog post

bensie added 30 commits May 18, 2026 12:48
reactions don't emit hotsock.messageReactionAdded/Removed events to
SNS/EventBridge. they go through the standard hotsock.messagePublished
path with event=hotsock.messageReaction in the metadata, and are gated
by emitPubSubEvent like any other message (always true on the
websocket path, customer-controlled on the http path).
reactions are still in the v1.13.2 binary but need more time to bake
before they're publicly documented. all docs, changelog entries, blog
post, and homepage references removed for now.
Reactions are ready. Key differences from the previous iteration:
- react directive accepts true, false, or an array of allowed values
- pub/sub events (hotsock.messageReactionAdded/Removed) are emitted
  from the DynamoDB stream processor post-commit, gated by emitPubSubEvent
- TTL-driven reaction deletes don't emit messageReactionRemoved
- pub/sub data shape: {channel, messageId, id, reaction, uid, umd, createdAt, expiresAt}
  with dataType "messageReaction"
- metadata: {channel, reaction, trigger, connectionId?, sourceIp?, userAgent?}
@bensie bensie changed the title release v1.13.1 changelog, documentation, and blog post v1.13.0 documentation, changelog, blog post, and homepage updates May 20, 2026
@bensie bensie merged commit ecd4053 into main May 20, 2026
2 checks passed
@bensie bensie deleted the bensie/doc-latest-hotsock branch May 20, 2026 05:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant