|
1 | 1 | Pre release |
2 | | -* [ ] npm audit and yarn audit is done |
3 | | -* [ ] change in local package installation |
4 | | -* [ ] update pem.d.ts when there is any change path-expression-matcher package |
5 | | -* [ ] Change log has been updated |
6 | | -* [ ] Added/updated documentation for new properties/features |
7 | | -* [ ] `package-lock.json` reflects the right version : `npm install` |
8 | | -* [ ] Browser bundle are generated `npm run bundle` |
9 | | -* [ ] TS and CJS typings are updated |
| 2 | +- [ ] npm audit and yarn audit is done |
| 3 | +- [ ] change in local package installation |
| 4 | +- [ ] update pem.d.ts when there is any change path-expression-matcher package |
| 5 | +- [ ] Change log has been updated |
| 6 | +- [ ] Added/updated documentation for new properties/features |
| 7 | +- [ ] `package-lock.json` reflects the right version : `npm install` |
| 8 | +- [ ] Browser bundle are generated `npm run bundle` |
| 9 | +- [ ] TS and CJS typings are updated |
10 | 10 | - fxp.d.cts |
11 | 11 | - fxp.d.ts |
12 | 12 |
|
13 | 13 | check here |
14 | 14 | - https://www.typescriptlang.org/play/ |
15 | 15 | - https://github.com/NaturalIntelligence/fxp-type-testing |
16 | | -* [ ] ReadMe file or docs are updated for any change, user list, performance report, links etc. |
17 | | -* [ ] Single test is not running `fit` |
18 | | -* [ ] `npm run checkReadiness` is used to check the files being published |
19 | | -* [ ] tags are assigned to latest commit `git tag -a v5.5.11 -m "ExpressionSet"` |
| 16 | +- [ ] ReadMe file or docs are updated for any change, user list, performance report, links etc. |
| 17 | +- [ ] Single test is not running `fit` |
| 18 | + |
| 19 | +Release: ensure not uncommited changes |
| 20 | +- Version: `npm version patch|minor|major` |
| 21 | + It runs `preversion` -> `version` -> `postversion` scripts if setup |
| 22 | + - It Computes the new version |
| 23 | + - update version in package.json and lock file. Commits the changed files. Default commit message is just the version string itself (e.g. 4.5.2) |
| 24 | + - Creates an annotated git tag on that commit, named v4.5.2 |
| 25 | + - Then will run postversion script. that does nothing |
| 26 | +- run `npm push origin master --tags` |
| 27 | + This'll trigger github publish action when new tag is found. |
| 28 | + github action will release to npm and github |
20 | 29 |
|
21 | 30 | In general |
22 | | -* [ ] tests are added/updated |
| 31 | +- [ ] tests are added/updated |
23 | 32 |
|
24 | 33 | Post release |
25 | | -* [ ] Tagged and Released on github `git push origin --tags` |
26 | | -* [ ] `git push origin master --tags` |
27 | | -* [ ] Notified to the users |
28 | | -* [ ] Sync master and dev branches |
| 34 | +- [ ] Notified to the users |
| 35 | +- [ ] Sync master and dev branches |
29 | 36 |
|
30 | 37 | To remove tag |
31 | 38 | git tag -d <tag_name> |
|
0 commit comments