npm package diff
Package: @forge/manifest
Versions: 8.3.0 - 8.3.1-next.0
File: package/out/schema/manifest.d.ts
Index: package/out/schema/manifest.d.ts
===================================================================
--- package/out/schema/manifest.d.ts
+++ package/out/schema/manifest.d.ts
@@ -773,9 +773,10 @@
*/
security?: {
egress?: {
/**
- * If set to false, webtriggers will sanitise responses for forms of egress.
+ * If set to false, the developer has opted into no-egress webtriggers. Inherently, webtriggers have the capability of egressing data from Forge apps, making apps using them ineligible for the RoA badge. These no-egress webtriggers give apps a pathway to RoA eligibility by sanitising response bodies, headers, and any other way responses can egress data when called via webtriggers.
+ * More details can be found here: https://hello.atlassian.net/wiki/spaces/ECO/pages/4562786428/WIP+ECORFC-409+-+No+egress+for+Web-Triggers
*/
allowDataEgress: boolean;
/**
* An array of statically defined responses that are not sanitised by no-egress webtriggers.
@@ -1674,9 +1675,10 @@
*/
security?: {
egress?: {
/**
- * If set to false, webtriggers will sanitise responses for forms of egress.
+ * If set to false, the developer has opted into no-egress webtriggers. Inherently, webtriggers have the capability of egressing data from Forge apps, making apps using them ineligible for the RoA badge. These no-egress webtriggers give apps a pathway to RoA eligibility by sanitising response bodies, headers, and any other way responses can egress data when called via webtriggers.
+ * More details can be found here: https://hello.atlassian.net/wiki/spaces/ECO/pages/4562786428/WIP+ECORFC-409+-+No+egress+for+Web-Triggers
*/
allowDataEgress: boolean;
/**
* An array of statically defined responses that are not sanitised by no-egress webtriggers.