Lukasz Gornicki
Lukasz Gornicki
thanks @Relequestual There is no native support for org level actions yet and [don't know when it will arrive](https://github.community/t/plans-to-support-global-workflows-in-github-repository/17899). I crafted [this](https://github.com/derberg/global-workflows-support) action to support "global" actions. It is actively...
what about pulling `server-api` inside CLI repo? every new CLI release also provides the server. We do not need separate versioning for server-api, why even calling it `server-api`. Just can...
Imho TSC voting is not needed, we do not remove project, we just move the code and functionality to another place. We move https://github.com/asyncapi/generator-hooks under generator and I'm also not...
@smoya yeah that was long time before. as current CLI codeowner I'm completely fine if you sunset `server-api` and slowly move it under `cli` repo. For sure with some MVP...
sounds good, just remember that once we will deploy server api from context of `cli` repo, we will have to add `DIGITALOCEAN_ACCESS_TOKEN` that is already here
@NektariosFifes if you have no custom workflows, and only these from `.githb` then the only thing you should do is `Upgrade Release pipeline - in case of nodejs projects`
I see below  don't you see setting button? 
**Scope of this issue** Cleanup `package.json` from the following: - remove script `"release": "semantic-release"` - remove the following `devDependencies` and then run `npm install` ``` @semantic-release/commit-analyzer @semantic-release/github @semantic-release/npm @semantic-release/release-notes-generator conventional-changelog-conventionalcommits...