All notable changes to fortemi-react are documented here.
- Added virtual embedding-set selectors and durable virtual embedding-set definitions for default, criteria, set-operation, fallback, latest-compatible, and snapshot workflows.
- Added persisted graph/community artifact tables and Knowledge Shard import/export support for graph sources, graph edges, community sets, communities, and community assignments.
- Added cached similarity graph APIs with freshness tracking, cache-only/live-only modes, stale marking, and threshold alias validation.
- Added dynamic and user-authored community APIs plus React hooks for embedding sets, similarity graphs, communities, and graph-source controller state.
- Split public npmjs.org distribution to the GitHub mirror workflow using
NPMJS_TOKENand npm provenance while keeping Gitea package publication for the internal registry. - Added the release-tag helper that forces the project release-signing key before publishing workflows run.
- Fixed migration-count tests so future schema migrations do not require hard-coded test rewrites.
@fortemi/core@2026.5.4@fortemi/react@2026.5.4
Consumers upgrading from 2026.5.3 get two new migrations: 0007_virtual_embedding_sets and 0008_graph_community_artifacts. Existing archives migrate on open. React consumers can keep existing hooks unchanged; the new graph/community hooks are additive.
- Expanded the
@fortemi/coreREADME with the project value proposition, architecture overview, use cases, search/knowledge model, tool surface details, and storage/privacy positioning for npm readers. - Expanded the
@fortemi/reactREADME so React consumers can understand the local-first archive, retrieval, Knowledge Shard, capability, and bridge-tool value without needing to read the core README first. - Updated getting-started and integration documentation to use host-neutral Fortemi language.
- Removed legacy downstream host references from docs, ADRs, code comments, and tests.
- Standardized bridge-visible tool IDs on the
fortemi.*namespace. - Standardized bridge projection naming on
BridgeCapabilityandtoBridgeCapabilities().
- Fixed Gitea release publishing by sending a versioned release
namefield so repository release lists show a proper release title instead of an empty title with only the Latest badge. - Kept repository release
tag_nametied to the signedv*tag for both Gitea and GitHub.
@fortemi/core@2026.5.3@fortemi/react@2026.5.3
Most consumers can upgrade directly from 2026.5.2. Integrations that inspect bridge tool IDs should use the fortemi.<tool> namespace. Integrations using the bridge projection helper should use toBridgeCapabilities() and BridgeCapability.
- Split repository release credentials so Gitea release publishing uses
GT_PUBLISH_TOKENand GitHub release publishing usesGH_PUBLISH_TOKEN. - Fixed manual publish reruns by passing the selected release tag into signed-tag verification.
- Added release-note driven repository release bodies so GitHub and Gitea releases can publish the prepared announcement instead of generic generated copy.
@fortemi/core@2026.5.2@fortemi/react@2026.5.2
No runtime API changes are included in this release. Existing @fortemi/core and @fortemi/react consumers can upgrade from 2026.5.1 without code changes.
- Verified the full npm, Gitea release, and GitHub release path for signed Fortemi releases.
- Published
@fortemi/core@2026.5.1and@fortemi/react@2026.5.1to npm. - Created matching Gitea and GitHub repository releases for the signed
v2026.5.1tag.
- Added the npm publish workflow for
@fortemi/coreand@fortemi/react. - Added signed release-tag verification using the project release key.
- Published the first coordinated package release for the Fortemi browser packages.