You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: scripts/release/README.md
+3-32Lines changed: 3 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,27 +1,6 @@
1
-
##How to release widgets & modules to the appstore (`./marketplaceRelease.js`)
1
+
# How to release widgets & modules to the appstore (`./marketplaceRelease.js`)
2
2
3
-
#### Web Widgets
4
-
5
-
1. Trigger the "Create Web Release" action manually in GitHub with the argument containing the widget name. Eg: "accordion-web".
6
-
2. That's it!
7
-
- The content should now be released in GitHub.
8
-
- The content should now be released in the MX Marketplace. Double check to verify.
9
-
10
-
#### Web Modules
11
-
12
-
1. Trigger the "Create Web Release" action manually in GitHub with the argument containing the module name. Eg "data-widgets".
13
-
2. That's it!
14
-
- The content should now be released in GitHub.
15
-
- The content should now be released in the MX Marketplace. Double check to verify.
16
-
17
-
#### Atlas Core
18
-
19
-
1. Trigger the "Create Web Release" action manually in GitHub with the argument "atlas-core".
20
-
2. That's it!
21
-
- The content should now be released in GitHub as a draft. Approve and publish it.
22
-
- Then another GitHub action `MarketplaceRelease` will take care of releasing the module to the MX Marketplace. Double check to verify.
23
-
24
-
#### Native Modules
3
+
## Native Modules
25
4
26
5
- Native _modules_ published to Marketplace include Native Mobile Resources (named `mobile-resources-native` in code) and Nanoflow Commons (named `nanoflow-actions-native` in code). `nanoflow-actions-hybrid` is deprecated since MX9.
27
6
@@ -44,15 +23,7 @@ The automation script uses the version part to bump the module's `package.json`
44
23
45
24
Note: regarding JS actions and widgets, the automation will delete existing JS action and widgets from the test project before copying over that which comes from the widget resources repository. This is useful to avoid retaining stale files/dependencies, for example, as the codebase changes and thus sourcecode files/dependencies change.
46
25
47
-
#### Hybrid Modules
48
-
49
-
1. Add a tag to the commit you want to create a release from. The tag should be formatted like ${PackageName}-v${Major}.${Minor}.${Patch}
50
-
- Example: `mobile-resources-hybrid-v1.0.0`
51
-
1. That's it!
52
-
- The content should now be released in GitHub.
53
-
- The content should now be released in the MX Marketplace. Double check to verify.
54
-
55
-
#### Atlas Native Content Module
26
+
## Atlas Native Content Module
56
27
57
28
1. Add a tag to the commit you want to create a release from. The tag should be formatted like ${PackageName}-v${Major}.${Minor}.${Patch}
0 commit comments