Skip to content

fortemi-react v2026.5.3

Choose a tag to compare

@jmagly jmagly released this 24 May 21:36
· 398 commits to main since this release
ccdf0fc

fortemi-react v2026.5.3

fortemi-react v2026.5.3 is a package presentation and host-neutral API cleanup release for the published browser packages. It improves the npm README experience for both packages, removes legacy downstream host branding from repo docs and code comments, and fixes repository release creation so Gitea and GitHub receive a real versioned release title while retaining the signed v2026.5.3 tag.

Highlights

  • Expanded the @fortemi/core npm README with a clearer product value proposition, architecture overview, use cases, search/knowledge model, tool surface explanation, and storage/privacy positioning.
  • Expanded the @fortemi/react npm README so React consumers can understand Fortemi's local-first archive, retrieval, Knowledge Shard, capability, and tool value without jumping to the core package first.
  • Removed legacy host-specific references from public docs, internal ADRs, React comments, and tool metadata.
  • Standardized bridge-facing tool IDs on the fortemi.* namespace.
  • Standardized bridge projection naming on BridgeCapability and toBridgeCapabilities().
  • Fixed Gitea release creation by sending the release name field, in addition to GitHub's release name and Gitea-compatible title data, so release lists and sidebars show a versioned release title instead of an empty title with only the Latest badge.

Published Packages

  • @fortemi/core@2026.5.3
  • @fortemi/react@2026.5.3

Compatibility

Most application consumers can upgrade directly from 2026.5.2. Consumers that register or look up manifest tools by fully qualified ID should use the fortemi.<tool> namespace. Consumers using the bridge projection helper should use toBridgeCapabilities() and BridgeCapability.

Verification

This release is intended to be cut from a signed v2026.5.3 tag after branch checks pass. The publish workflow verifies the signed tag before publishing npm packages or repository releases.