TypeScript WSDL Client - 0.8.14 Release (Breaking Changes!!!)

[sergeliatko]

TypeScript WSDL Client - 0.8.14 Release (Breaking Changes!!!)

The 0.8.14 release focuses on stabilizing the release pipeline and polishing the developer experience around the gateway, catalog handling, and CLI.

Highlights

Gateway URN format & flags (breaking in 0.8.0)

Gateway-generated JSON Schemas now use a service-first URN structure:

• urn:services:{service}:{version}:schemas:{models|operations}:{slug}

This replaces the older urn:schema:{version}:services:{service}:{models|operations}:{slug} format to make service-scoped filtering and navigation easier.

Gateway and pipeline commands now always require:

• --gateway-service-name
• --gateway-version-prefix

This makes URNs explicit and predictable across environments.

Catalog co-location and CLI defaults

Catalog handling has been standardized and documented in the updated README.md:

• Catalogs now default to the output directory instead of a hardcoded tmp/ path.
• client writes catalog.json to {client-dir}/catalog.json by default.
• openapi writes catalog.json to {dir-of-openapi-file}/catalog.json by default.
• pipeline uses a cascade: {client-dir} > {openapi-dir} > {gateway-dir} > tmp/.

This makes catalog discovery more intuitive and keeps artifacts co-located with the code that uses them.

CLI flags and logging clean-up (breaking flag rename)

All CLI options are now standardized to lowercase, hyphenated names. Notable breaking renames include:

• --versionTag → --version-tag
• --basePath → --base-path
• --pathStyle → --path-style
• --closedSchemas → --closed-schemas
• --pruneUnusedSchemas → --prune-unused-schemas

Logging and console output have been simplified and normalized:

• Removed redundant messages (schema counts, per-file writes, OpenAPI validation success spam).
• Standardized prefixes: [ERROR], [WARNING], [SUCCESS].
• Removed emojis and inconsistent [wsdl] prefixes for better compatibility with various terminals and CI logs.

Gateway and OpenAPI improvements

• Gateway now supports both JSON and YAML OpenAPI input based on file extension (.json, .yaml, .yml).
• Gateway success messages always print absolute paths, matching other commands.
• OpenAPI generation now reports the exact output path and uses more consistent console output.
• Pipeline output clearly shows which steps ran (client, OpenAPI, gateway) and includes discovery information (schemas, types, operations).

Docs and programmatic API

The README.md has been substantially updated:

• Clarified that the gateway command generates scaffolding (routes + schemas + handler stubs), not a fully implemented gateway.
• Added a clear description of catalog co-location behavior per command.
• Documented all five CLI commands (compile, client, openapi, gateway, pipeline) with updated examples and flag names.
• Added detailed sections for Fastify integration patterns and the current gateway status.
• Documented the programmatic API for all exported functions:
  • compileWsdlToProject
  • generateOpenAPI
  • generateGateway
  • runGenerationPipeline
• Simplified prose, removed emojis and decorative symbols, and made the docs easier to scan and copy-paste.

Release and CI workflow

• The release workflow has been tightened up and versioning logic has been improved (0.8.1, 0.8.11, 0.8.14).
• CI now focuses on a single smoke:pipeline flow to cover client, OpenAPI, and gateway generation end to end.
• Smoke scripts were cleaned up to use consistent, documented flags (--wsdl-source, --catalog-file, --client-dir, --openapi-file, --gateway-dir, --gateway-service-name, --gateway-version-prefix, --openapi-format, --openapi-servers).

Impact and upgrade notes

If you are using the gateway or pipeline commands:

• Update your scripts to pass --gateway-service-name and --gateway-version-prefix.
• If you depend on the old URN format, plan for the new service-first structure.
• Update any CLI invocations to use the new lowercase, hyphenated flag names.

If you are consuming catalogs or relying on their location:

• Expect catalogs to be co-located with generated artifacts by default.
• Review the new README.md sections on catalog organization and the pipeline workflow.

The 0.8.14 release is primarily about making the toolchain more predictable, documented, and CI-friendly, while keeping the surface of breaking changes limited and well-described.