@forge/manifest 8.3.0 → 8.3.1-next.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/out/schema/manifest-schema.json +1 -1
  3. package/out/schema/manifest.d.ts +4 -2
  4. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @forge/manifest
2
2
 
3
+ ## 8.3.1-next.0
4
+
5
+ ### Patch Changes
6
+
7
+ - 2ccf3f4: Update manifest definitions
8
+
3
9
  ## 8.3.0
4
10
 
5
11
  ### Minor Changes
package/out/schema/manifest-schema.json CHANGED
@@ -407,7 +407,7 @@
407
407
  "additionalProperties": false,
408
408
  "properties": {
409
409
  "allowDataEgress": {
410
- "description": "If set to false, webtriggers will sanitise responses for forms of egress.",
410
+ "description": "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. \nMore details can be found here: https://hello.atlassian.net/wiki/spaces/ECO/pages/4562786428/WIP+ECORFC-409+-+No+egress+for+Web-Triggers",
411
411
  "type": "boolean"
412
412
  },
413
413
  "allowedResponses": {
package/out/schema/manifest.d.ts CHANGED
@@ -774,7 +774,8 @@ export interface Modules {
774
774
  security?: {
775
775
  egress?: {
776
776
  /**
777
- * If set to false, webtriggers will sanitise responses for forms of egress.
777
+ * 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.
778
+ * More details can be found here: https://hello.atlassian.net/wiki/spaces/ECO/pages/4562786428/WIP+ECORFC-409+-+No+egress+for+Web-Triggers
778
779
  */
779
780
  allowDataEgress: boolean;
780
781
  /**
@@ -1675,7 +1676,8 @@ export interface Modules {
1675
1676
  security?: {
1676
1677
  egress?: {
1677
1678
  /**
1678
- * If set to false, webtriggers will sanitise responses for forms of egress.
1679
+ * 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.
1680
+ * More details can be found here: https://hello.atlassian.net/wiki/spaces/ECO/pages/4562786428/WIP+ECORFC-409+-+No+egress+for+Web-Triggers
1679
1681
  */
1680
1682
  allowDataEgress: boolean;
1681
1683
  /**
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@forge/manifest",
3
- "version": "8.3.0",
3
+ "version": "8.3.1-next.0",
4
4
  "description": "Definitions and validations of the Forge manifest",
5
5
  "main": "out/index.js",
6
6
  "scripts": {