File tree Expand file tree Collapse file tree 1 file changed +1
-20
lines changed
Expand file tree Collapse file tree 1 file changed +1
-20
lines changed Original file line number Diff line number Diff line change @@ -12,7 +12,6 @@ following information:
12123 . Example code snippet that causes the issue.
13134 . Screenshots of the broken UI.
1414
15-
1615## Development
1716
1817Clone this repo and install [ Node v16] ( https://nodejs.org/en/download/ ) . Below
@@ -25,24 +24,6 @@ are commands we use to perform various tasks:
2524- ` npm run lint ` , run linter.
2625- ` npm run format ` , run code formatter.
2726
28-
2927## Publishing a new version
3028
31- 1 . Update ` CHANGELOG.md ` with any changes that need to be communicated to a
32- user of the SDK. See https://keepachangelog.com/en/1.1.0/ for details on
33- what and how content should be included.
34- 2 . Run ` npm version <new version> ` to set the new SDK version and create the git
35- tag.
36- 3 . [ Publish new version to npm.] ( #publishing-to-npm )
37-
38-
39- ### Publishing to npm
40-
41- You will need permission to publish to the [ mxenabled] [ mxenabled_npm_org ]
42- organization in npm before you can publish this package. Once you are able to
43- publish, log into npm with ` npm login ` then run ` npm publish ` to publish. Note
44- that running ` npm publish ` will automatically execute ` npm run build:dist ` for
45- you, so there is no need to do that manually.
46-
47-
48- [ mxenabled_npm_org ] : https://www.npmjs.com/org/mxenabled " mxenabled npm organization "
29+ Publishing of the npm package is handled by github actions. The ` CHANGELOG.md ` and ` package.json ` version need to be manually updated.
You can’t perform that action at this time.
0 commit comments