@@ -38,7 +38,7 @@ and any other relevant channels
38
38
Reset the build state to 'latest'; this is displayed on the demo site:
39
39
40
40
1 . revert ` buildState ` in ` td.vue/package.json ` back to ` -latest `
41
- 2 . revert version, for example ` "version": "2.3 .0", ` , in ` td.vue/package.json ` ,
41
+ 2 . revert version, for example ` "version": "2.5 .0", ` , in ` td.vue/package.json ` ,
42
42
in ` package.json ` and ` td.server/package.json `
43
43
3 . ensure that the package-lock files are up to date using ` npm install `
44
44
4 . ` git add --all; git status `
@@ -54,17 +54,18 @@ After the releases candidate has been agreed by the Threat Dragon community, a r
54
54
1 . ` git clone [email protected] :OWASP/threat-dragon.git `
55
55
2 . ` cd threat-dragon `
56
56
3 . update version eg ` "version": "2.5.0", ` , in ` package.json ` , ` td.vue/package.json ` and ` td.server/package.json `
57
- 4 . update ` buildState ` in ` td.vue/package.json ` away from ` -latest ` to "" (empty)
57
+ 4 . update ` buildState ` in ` td.vue/package.json ` away from ` " -latest" ` to ` "" ` (empty)
58
58
5 . update package lock files: ` npm install `
59
59
6 . ` npm run build `
60
60
7 . ` npm test `
61
61
8 . ` npm run test:vue `
62
- 9 . ensure that the package-lock files are up to date using ` npm install `
63
- 10 . ` git add --all; git status `
64
- 11 . ` git commit -m"release version 2.5.0" `
65
- 12 . ` git push `
66
- 13 . tag the release ` git tag v2.5.0 `
67
- 14 . ` git push origin v2.5.0 `
62
+ 9 . ensure documentation is clean: ` pyspelling --config .spellcheck.yaml ` and ` markdownlint-cli2 docs/**/*.md `
63
+ 10 . ensure that the package-lock files are up to date using ` npm install `
64
+ 11 . ` git add --all; git status `
65
+ 12 . ` git commit -m"release version 2.5.0" `
66
+ 13 . ` git push `
67
+ 14 . tag the release ` git tag v2.5.0 `
68
+ 15 . ` git push origin v2.5.0 `
68
69
69
70
The github release workflow then creates the draft release and the install images
70
71
0 commit comments