fix: update @asyncapi/specs to 4.2.0 version

[asyncapi-bot]

No description provided.

[jonaslagoni]

We do explicit validation of payloads, but now they are starting to be validated by our JSON Schema files, so we can start to phase them out. Thats why the tests fails because it expects our own validators to throw the error, now the core validation step.

[derberg]

@jonaslagoni but if we change the error type that we throw, it is a breaking change

[jonaslagoni]

Yea was going to ask that next 😆

Now sure which approach to take to update the dependency.

[derberg]

well, parser needs new major, of course we can just resign from bumping to latest specs package in master, and do bump only in 2.0 release candidate

IMHO 2.0-only is best approach. Especially that it is already integrated in some tools I think.

@fmvilas @magicmatatjahu @smoya share your thoughts please

[derberg]

@fmvilas @magicmatatjahu @smoya share your thoughts please

[smoya]

@fmvilas @magicmatatjahu @smoya share your thoughts please

Merging this in master should be considered a breaking change: some valid payloads will become invalid.
I suggest we skip this update for Parser-JS v1.x in favour of targeting v2 (next-major branch). Basically, +1 to @derberg suggestion.

Additionally, to create a new PR freezing@asyncapi/specs package for 1.x so no more @asyncapi-bot updates happen.

EDIT: Issue created #736

[smoya]

target next-major branch

[fmvilas]

Yeah, I think it’s a breaking change too.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[derberg]

@smoya we're closing this one, right? you freezed the version?

[smoya]

@smoya we're closing this one, right? you freezed the version?

Yup, can be closed now. For the reference #737