@veryfront/ext-observability-sentry-node 0.1.1186 → 0.1.1190

package/README.md

@@ -2,6 +2,11 @@
 
 First-party Sentry application error reporter for Veryfront runtimes.
 
+This package is service-conditional rather than an auto-activated application
+extension. The server or agent service imports the matching reporter only after
+its enablement policy passes; adding the package to `node_modules` alone does
+not initialize Sentry or enable network egress.
+
 Enable the adapter explicitly and provide its credential:
 
 ```sh
@@ -10,10 +15,10 @@ VERYFRONT_ERROR_REPORTER=sentry
 SENTRY_DSN=https://public@example.ingest.sentry.io/1
 ```
 
-`SENTRY_ENABLED=false` always disables reporting, even when the adapter and a
-valid DSN are present. During the compatibility rollout, an unset flag keeps
-the existing adapter-selection behavior. `SENTRY_DSN` selects the event
-destination and may use a public HTTPS custom Sentry hostname; `SENTRY_URL` is
+Only `SENTRY_ENABLED=true` or `SENTRY_ENABLED=1` enables reporting. An unset,
+blank, `false`, `0`, or unrecognized value disables reporting even when the
+adapter and a valid DSN are present. `SENTRY_DSN` selects the event destination
+and may use a public HTTPS custom Sentry hostname; `SENTRY_URL` is
 release-tooling configuration and is not read by the runtime adapter.
 
 `SENTRY_DSN` alone does not activate the framework adapter. Official compiled Veryfront

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@veryfront/ext-observability-sentry-node",
-  "version": "0.1.1186",
+  "version": "0.1.1190",
   "description": "Veryfront first-party extension package for ext-observability-sentry-node",
   "keywords": [
     "veryfront",
@@ -27,7 +27,7 @@
   },
   "scripts": {},
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=22.3.0"
   },
   "publishConfig": {
     "access": "public"