@sentry/api 0.238.0 → 0.240.0

package/dist/types.gen.d.ts

@@ -4552,14 +4552,14 @@ export type ListTraceItemAttributesResponse = Array<{
     /**
      * Additional, mostly-static metadata about an attribute.
      *
-     * When ``expand=context`` is requested (and the
-     * ``data-browsing-attribute-context`` feature is enabled), context is attached
-     * to every attribute. Today the metadata is sourced from the sentry
-     * conventions (``sentry_conventions.attributes.ATTRIBUTE_METADATA``), so
-     * attributes that map to a known convention carry that metadata (only the
-     * fields actually present are included) while custom attributes get an empty
-     * context. Serving context for custom attributes is planned, at which point
-     * the empty contexts will start to be populated.
+     * When ``expand=context`` is requested, context is attached to every
+     * attribute. Today the metadata is sourced from the sentry conventions
+     * (``sentry_conventions.attributes.ATTRIBUTE_METADATA``), so attributes that
+     * map to a known convention carry that metadata (only the fields actually
+     * present are included) while custom attributes get an empty context. Serving
+     * context for custom attributes is planned (gated behind the
+     * ``data-browsing-attribute-context`` feature), at which point the empty
+     * contexts will start to be populated.
      */
     context?: {
         brief?: string;
@@ -21545,14 +21545,14 @@ export type ListOrganizationTraceItemAttributesResponses = {
         /**
          * Additional, mostly-static metadata about an attribute.
          *
-         * When ``expand=context`` is requested (and the
-         * ``data-browsing-attribute-context`` feature is enabled), context is attached
-         * to every attribute. Today the metadata is sourced from the sentry
-         * conventions (``sentry_conventions.attributes.ATTRIBUTE_METADATA``), so
-         * attributes that map to a known convention carry that metadata (only the
-         * fields actually present are included) while custom attributes get an empty
-         * context. Serving context for custom attributes is planned, at which point
-         * the empty contexts will start to be populated.
+         * When ``expand=context`` is requested, context is attached to every
+         * attribute. Today the metadata is sourced from the sentry conventions
+         * (``sentry_conventions.attributes.ATTRIBUTE_METADATA``), so attributes that
+         * map to a known convention carry that metadata (only the fields actually
+         * present are included) while custom attributes get an empty context. Serving
+         * context for custom attributes is planned (gated behind the
+         * ``data-browsing-attribute-context`` feature), at which point the empty
+         * contexts will start to be populated.
          */
         context?: {
             brief?: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/api",
-  "version": "0.238.0",
+  "version": "0.240.0",
   "description": "Official auto-generated TypeScript client for the Sentry public REST API",
   "keywords": [
     "sentry",