@eventcatalog/generator-openapi@7.12.9

Patch Changes

• f684245: fix: stop demoting newer cataloged messages when the generator is re-run against an older spec. The EventBridge, AsyncAPI and OpenAPI generators previously used a plain !== version check before calling versionEvent / versionMessage, which meant any version difference would move the cataloged entry into versioned/ and write the incoming one at the root — even when the incoming version was older. The generators now use a semver-aware comparison (with semver.coerce so non-semver versions like EventBridge's integer counters still sort numerically) and only demote the cataloged entry when the incoming version is strictly newer. When the incoming version is older or cannot be confidently compared, the generator logs a warning, leaves the cataloged entry untouched, and points the service's sends/receives at the existing cataloged version.

@eventcatalog/generator-eventbridge@3.4.3

Patch Changes

• f684245: fix: stop demoting newer cataloged messages when the generator is re-run against an older spec. The EventBridge, AsyncAPI and OpenAPI generators previously used a plain !== version check before calling versionEvent / versionMessage, which meant any version difference would move the cataloged entry into versioned/ and write the incoming one at the root — even when the incoming version was older. The generators now use a semver-aware comparison (with semver.coerce so non-semver versions like EventBridge's integer counters still sort numerically) and only demote the cataloged entry when the incoming version is strictly newer. When the incoming version is older or cannot be confidently compared, the generator logs a warning, leaves the cataloged entry untouched, and points the service's sends/receives at the existing cataloged version.

@eventcatalog/generator-asyncapi@6.4.2

Patch Changes

• f684245: fix: stop demoting newer cataloged messages when the generator is re-run against an older spec. The EventBridge, AsyncAPI and OpenAPI generators previously used a plain !== version check before calling versionEvent / versionMessage, which meant any version difference would move the cataloged entry into versioned/ and write the incoming one at the root — even when the incoming version was older. The generators now use a semver-aware comparison (with semver.coerce so non-semver versions like EventBridge's integer counters still sort numerically) and only demote the cataloged entry when the incoming version is strictly newer. When the incoming version is older or cannot be confidently compared, the generator logs a warning, leaves the cataloged entry untouched, and points the service's sends/receives at the existing cataloged version.

@eventcatalog/generator-openapi@7.12.8

Patch Changes

• 79f3c3d: fix: preserve existing service location when re-running the generator without a domain configured. Previously, if a service already existed inside a domain (e.g. domains/orders/services/my-service) and the generator was re-run without the domain option set, the generator would write a duplicate copy of the service to the catalog root at services/my-service. The generators now resolve the existing service's on-disk location via getResourcePath and write back in-place, matching the behaviour already used for consumer services.

@eventcatalog/generator-asyncapi@6.4.1

Patch Changes

• 79f3c3d: fix: preserve existing service location when re-running the generator without a domain configured. Previously, if a service already existed inside a domain (e.g. domains/orders/services/my-service) and the generator was re-run without the domain option set, the generator would write a duplicate copy of the service to the catalog root at services/my-service. The generators now resolve the existing service's on-disk location via getResourcePath and write back in-place, matching the behaviour already used for consumer services.

@eventcatalog/generator-openapi@7.12.7

Patch Changes

• c545a2e: fix: preserve group fields on sends/receives when regenerating against an existing service. Previously, running the generator a second time against a service already in the catalog would drop group values derived from groupMessagesBy (e.g. path-prefix, single-group). Freshly-generated pointers now win over stale catalog pointers on id+version collisions, while catalog-only pointers (e.g. hand-added) are preserved.

@eventcatalog/generator-openapi@7.12.6

Patch Changes

• 9a2f4f5: feat(generator-openapi): warn when a spec has 50+ operations without groupMessagesBy set

@eventcatalog/generator-openapi@7.12.5

Patch Changes

• c0c209f: feat(generator-openapi): add single-group option to groupMessagesBy for large APIs

@eventcatalog/generator-openapi@7.12.4

Patch Changes

• 3f5ff74: fix(generator-openapi): group path-prefix when multiple verbs share a single path

@eventcatalog/generator-openapi@7.12.3

Patch Changes

• 6ad035f: Fix consumer route wildcard matching so patterns with a leading * (e.g. */adopted) correctly match OpenAPI paths that start with /.