Automate release of parser and other packages #52
Description
- automate release as it is done already in generator Start using Conventional Commits spec and automate releases generator#225
- Important to remember:
- no need for docker
- remember to use npm scope
- remember to mark in package.json that package is public
- for browser distributions make sure that during the release bundles are attached to GitHub Release
- I think CDN is not needed for now unless someone from community thinks different. In the age of HTTP/1 I would not use CDN but bundle the library but in HTTP/2 I would personally reconsider it.
- except of parser we need to have automation in:
- https://github.com/asyncapi/raml-dt-schema-parser
- https://github.com/asyncapi/openapi-schema-parser
- https://github.com/asyncapi/asyncapi-node
- https://github.com/asyncapi/asyncapi-react/
- https://github.com/asyncapi/parser-go
- https://github.com/asyncapi/converter-go
Generator templates: - https://github.com/derberg/html-template
- https://github.com/derberg/markdown-template
- https://github.com/derberg/nodejs-template
- https://github.com/derberg/nodejs-ws-template
- https://github.com/derberg/java-spring-template