Publish your SDK
Once you have generated your SDK, you can publish it to a package manager so that other developers can use it. You'll need to ensure you have set the correct metadata in your liblab config file, including the SDK version before publishing.
In the liblab config file, you can set the following metadata for any SDK language, and this will be added to the package manifest:
| Option | Description |
|---|---|
sdkVersion | The version number of your SDK. |
authors | The authors of the SDK. Not supported for Java SDKs. |
homepage | The homepage of the SDK. |
For Java, you can also set:
| Option | Description |
|---|---|
groupId | The group ID of the SDK. |
For Python you can also set:
| Option | Description |
|---|---|
pypiPackageName | The name of the Python package for PyPI. |
classifiers | The PyPI Trove classifiers. |
projectUrls | The PyPI project URLs. |
For TypeScript you can also set:
| Option | Description |
|---|---|
npmOrg | The scope for the npm package name. |
npmName | The npm package name. |
Publishing to a package manager
Depending on the language you have generated your SDK for, you can publish to the following package managers:
Publish your TypeScript SDK
You can find instructions to publish your TypeScript SDK to the npm repository in the npm documentation.
Publish your Java SDK
You can find instructions to publish your Java SDK to the Maven Central Repository in the Sonatype central repository documentation.
Publish your Python SDK
You can find instructions to publish your Python SDK to the PyPI repository in the PyPI documentation.