@forge/cli-shared 5.0.0-next.2-experimental-9e36838 → 5.0.0-next.3

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.
package/CHANGELOG.md CHANGED
@@ -1,43 +1,11 @@
1
1
  # @forge/cli-shared
2
2
 
3
- ## 5.0.0-next.2-experimental-9e36838
4
-
5
- ### Major Changes
6
-
7
- - 5c2c20f: Fixed the issue where the CLI was unable to bundle modules with multiple entrypoints using different resource types.
8
-
9
- Specifically the following configuration that supports both UI Kit and Custom UI resources are now supported properly.
10
-
11
- ```yaml
12
- modules:
13
- jira:customFieldType:
14
- - key: my_custom_field_app
15
- resource: ui-kit-resource
16
- render: native
17
- contextConfig:
18
- resource: custom-ui-resource
19
- ```
20
-
21
- In the previous CLI version, the above configuration would assume that the `custom-ui-resource` is a UI Kit resource
22
- and would expected a UI Kit based resource is linked. To support using same resource type for multiple entrypoints,
23
- in above example, please add `render: native` to the `contextConfig` to correct the resource type:
24
-
25
- ```yaml
26
- modules:
27
- jira:customFieldType:
28
- - key: my_custom_field_app
29
- resource: ui-kit-resource
30
- render: native
31
- contextConfig:
32
- resource: ui-kit-resource
33
- render: native
34
- ```
3
+ ## 5.0.0-next.3
35
4
 
36
5
  ### Patch Changes
37
6
 
38
- - Updated dependencies [77d16a9]
39
- - Updated dependencies [f04a310]
40
- - @forge/manifest@7.2.3-next.1-experimental-9e36838
7
+ - Updated dependencies [6099d41]
8
+ - @forge/manifest@7.2.3-next.2
41
9
 
42
10
  ## 5.0.0-next.2
43
11