ci/rework-include-ts

[Charles-Schleich]

The CI/CD pipeline should include releasing 3 things

• Zenoh-ts packaged and released on npm (github)
• zenoh-plugin-remote-api released on github
• Documentation publishing
  All of these things should happen on a push to a version tag
  This requires all Cargo.toml's and package.json's to be bumped to the same version number.

The respective workflows for plugin, docs and plugin will handle publishing.

Debate: Should we allow releasing the library or the plugin manually as well ?

[github-actions]

PR missing one of the required labels: {'bug', 'internal', 'breaking-change', 'dependencies', 'documentation', 'enhancement', 'new feature'}

[gabrik]

Comment here, the JS package should be on npm not github, otherwise access it still requires a token.

[diogomatsubara]

without the v

[Charles-Schleich]

updated.

[diogomatsubara]

without the v and quoted

[Charles-Schleich]

updated

[diogomatsubara]

I think this whole workflow can be deleted. We have in the release.yml a job to publish the artifacts created during the build to github and release it as a Github release.

[Charles-Schleich]

Removed the workflow, i was under the impression the workflow was doing the releasing.

[Charles-Schleich]

@gabrik ive opened an issue in gitlab for the Eclipse Foundation to create a bot on NPM,
once they create that bot i will integrate publishing to npm in the CI/CD (Should just require an update to the .npmrc)
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5279