Skip to main content
Glean Feed publishes the framework-agnostic widget as @gleanfeed/widget and the React provider as @gleanfeed/react.

​
Runtime support

The React package depends on a compatible widget package and installs it as a runtime dependency. Installing both explicitly keeps the relationship visible in your application manifest:

​
Version policy

  • During 0.x, a minor release may contain a breaking change. Pin exact versions when upgrades require controlled testing.
  • Starting with 1.0.0, packages follow semantic versioning: breaking changes use a major release, features a minor release, and fixes a patch release.
  • The stable CDN URL receives the current production widget build. Use npm and an exact version when a deployment needs a deliberate upgrade boundary.
  • Releases are authorized through the reviewed repository workflow and npm trusted publishing after the initial registry bootstrap. Verify the publisher, repository, version, and release notes before updating a lockfile.

​
Upgrade safely

  1. Review both package release notes when using React.
  2. Upgrade the widget and wrapper together when their compatibility ranges move.
  3. Test launcher and inline mounting, feedback/roadmap/changelog navigation, signed identity, notification badges, teardown, and React Strict Mode.
  4. Keep the previous lockfile available for a fast rollback.
See Install the widget, React, and troubleshooting for implementation details.