BugPin v1.2.2
BugPin v1.2.2 adds local compatibility warnings for npm widget deployments and lets integrations prefill reporter details.
Sites using the @arantic/bugpin-widget npm package must upgrade to version 1.1.3 or later and redeploy. Sites loading the hosted /widget.js script are unaffected.
npm install @arantic/bugpin-widget@latest
What's New
Widget package compatibility warnings
Administrators now see a dismissible warning when a recently active npm widget deployment uses a package version older than the minimum supported by the BugPin server.
The warning identifies affected projects, observed versions, and deployment counts, with a link to the package versions page. Compatibility checks run locally and remain available when remote BugPin update checks are disabled.
Programmatic BugPin.init() integrations report their package version during the existing configuration request. Hosted /widget.js integrations do not send package metadata.
Reporter prefill
Widget integrations can now prefill the editable reporter name and email through BugPin.init() or script-tag data attributes. Reporter-prefilled drafts are scoped by reporter email to avoid restoring another reporter's saved form data.
The Admin Console's Test Widget page also lets administrators edit the test reporter and switch between reporter and logged-out modes.
See Widget Installation for configuration examples.
Privacy and Storage
Widget deployment origins are stored only as SHA-256 hashes. Observations expire after 30 days and are limited to the 100 most recent deployments per project.
The release adds a widget_version_observations database table. The migration runs automatically on first launch; no manual step is required.
How to Upgrade
Docker
docker compose pull && docker compose up -d
Bun
git pull
bun install
bun run build
bun run start
If you use the npm widget package, upgrade and redeploy each application that bundles it.