liblab versions
liblab supports multiple versions of its SDK generation for different SDK languages. As we update to newer versions of our SDK generation with enhanced features, there may be breaking changes in the generated SDK.
By managing the liblab version used for SDK generation you can ensure that your SDK will not receive an update that causes breaking changes without your knowledge. When you are ready to update to a newer version of our SDK generation, you can increment the version in your liblab config file, and determine the impact on your generated SDKs before you release them to your users or customers.
Configure liblab versions
You can configure the liblab version on a per-language basis by setting the liblabVersion option in the languageOptions section of your config file.
Supported versions
| SDK language | liblabVersion | Default1 | Notes |
|---|---|---|---|
| TypeScript | 1 | ❌ | Initial release |
| TypeScript | 2 | ✅ | v2 of our TypeScript SDK generation with features such as model and service validation using zod, custom retries per endpoint, and improved name generation. |
| Java | 1 | ❌ | Initial release |
| Java | 2 | ✅ | v2 of our Java SDK generation with features such as improved models, simplified hooks, improved code snippets, and improved name generation |
| Python | 1 | ❌ | Initial release |
| Python | 2 | ✅ | v2 of our Python SDK generation with features such as SDK side validation, reST docstrings, and improved name generation |
| C# | 2 | ✅ | Initial release (Beta) |
| Go | 2 | ✅ | Initial release (Beta) |
| PHP | 2 | ✅ | Initial release (Beta) |
| Terraform | 2 | ✅ | Initial release (Beta) |
11 The default value is the version that will be used if the liblabVersion is not specified in the config file.