improve release procedure steps
This commit is contained in:
parent
9c553b7dda
commit
a5605d4d13
17
README.md
17
README.md
|
@ -18,14 +18,15 @@ More details can be found in the [WordPress Plugin Directory](https://wordpress.
|
|||
### Release procedure
|
||||
1. Make sure `changelog.txt` is up-to-date. Use a new version number and copy over the new section into `readme.txt`.
|
||||
2. Update `package.json` with the same version number.
|
||||
3. Build: `npm run build-prod`
|
||||
4. Determine minimum PHP version for code and update package.json if needed: `./vendor/bin/phpcompatinfo analyser:run ./source`
|
||||
5. Make sure screenshots are up-to-date.
|
||||
6. Copy the built plugin into `/trunk` of SVN.
|
||||
7. Create a new tag of the new version: `svn cp trunk tags/<version>`
|
||||
8. Check the version number occurences in both folders.
|
||||
9. Commit everything together: `svn ci -m "release version <version>"`
|
||||
10. Tag the new version in `git` too.
|
||||
3. Update the `package-lock.json`: `npm i --package-lock-only`
|
||||
4. Build: `npm run build-prod`
|
||||
5. Determine minimum PHP version for code and update package.json if needed: `./vendor/bin/phpcompatinfo analyser:run ./source`
|
||||
6. Make sure screenshots are up-to-date.
|
||||
7. Copy the built plugin into `/trunk` of SVN.
|
||||
8. Create a new tag of the new version: `svn cp trunk tags/<version>`
|
||||
9. Check the version number occurences in both folders.
|
||||
10. Commit everything together to the release SVN: `svn ci -m "release version <version>"`
|
||||
11. Commit and tag the new version in `git` too.
|
||||
|
||||
### Other commands
|
||||
- Run ESLint: `npm run eslint`
|
||||
|
|
Loading…
Reference in New Issue