[BUG] generate failed when make a patch version update

The changelog-reader-action can not read the third level heading, in which case the workflows failed when make a patch version update.

[yi-Xu-0100]

@vivaxy Thanks for your suggestion here, I use the script for some reason.

1. The scripts I used in actions that npm run package is used to make “offline” package for extension and upload to release asset.
2. I can not use the npm run release to publish a new version because I did not have the personal access token for this extension. I upload the .vsix package to market to update the extension, so I need the npm run package to generate the package.
3. Because I can not use the npm run release, so I add a script version to bump the version for the extension, I see the comment in #57, If this name of the script is not suitable, I will adjust it.
4. I think trigger manually can help to make the release, but for me, I also need to package locally to upload the package to market. Maybe we can use the https://github.com/HaaLeo/publish-vscode-extension to help the publishing, but the action needs the PAT to use it.

So the action workflows can trigger manually and run with the following steps:

1. Set up job
2. Checkout code
3. Bump version and write change log with https://github.com/TriPSs/conventional-changelog-action
4. Use the https://github.com/HaaLeo/publish-vscode-extension to publish extension and output the .vsix path
5. Create release
6. Upload release asset

For the possible error in action.

1. If step 3 occurs an error, the release will not be created, we may need to publish locally with scripts(vsce publish for you, and the vsce package for me) which may need to be separated into other scripts.
2. for the existing step 2, the standard-version may be deleted.

For the CHANGELOG.md I also find the content changed with the prettier, maybe we should add it to the .prettierignore.

For the version script, I did not find the named script in pre–post-scripts, Could you point it out for me? Thanks a lot! 😀

[vivaxy]

@yi-Xu-0100 What you did with GitHub Actions is awesome!

I’m not familiar with GitHub Actions. But still, I’ve some questions:

1. Is it possible to reuse npm scripts with GitHub Actions and local publishing? I’d like to think GitHub Actions as a much advanced way of publishing. When it fails, it’s better to fallback to local publishing. So it’s better to have those two publishing ways in the same steps with the same npm scripts.
2. Is https://github.com/TriPSs/conventional-changelog-action applicable in our scenario? So we can tigger GitHub Actions manually with the following steps:
   1. Set up job
   2. Checkout code
   3. Bump version and write change log with https://github.com/TriPSs/conventional-changelog-action
   4. Generate Package
   5. Create release
   6. Upload release asset