feat: re-trigger message payload validation

[jonaslagoni]

Description
This PR re-triggers the release workflow as it failed the last time #334

[smoya]

Adding more context: The action keeps failing since the merged commit didn't have the fix for increasing the timeout on the test (the actual error). This PR is up-to-date and contains such a change.

[smoya]

@jonaslagoni can you just do git commit --alow-empty instead of adding that empty line?

[derberg]

I don't think we need it, I'm rerunning the initial release. MacOS just went through, waiting for Windows

[smoya]

I don't think we need it, I'm rerunning the initial release. MacOS just went through, waiting for Windows

LOL! The previous re-run I made was also failing. Now it seems it doesn't.

[derberg]

yeah, call me re-run ninja

[derberg]

ok, it worked, but no release, and no changes were detected 🤔

https://github.com/asyncapi/spec-json-schemas/actions/runs/4404537995/jobs/7715620229

[derberg]

oh yeah, after all you need to merge this as release was not triggered as in the meantime you merged PR with timeout increase 🤷🏼

[jonaslagoni]

Yea 😄

[jonaslagoni]

@smoya done 🙂

[jonaslagoni]

/rtm

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[asyncapi-bot]

🎉 This PR is included in version 5.0.0-next-major-spec.14 🎉

The release is available on:

• npm package (@next-major-spec dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[asyncapi-bot]

🎉 This PR is included in version 6.0.0-next-major-spec.1 🎉

The release is available on:

• npm package (@next-major-spec dist-tag)
• GitHub release

Your semantic-release bot 📦🚀