chore: update next-spec branch with master changes

[char0n]

This is PR is part of asyncapi/spec#830 and updates next-spec branch with changes from master.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[char0n]

@fmvilas @derberg @jonaslagoni @magicmatatjahu can you please look into this PR. It's part of 2.5.0 release effort and updates the release branch (next-spec) with master branch.

[derberg]

strange to see changes only in package-lock.json

GH is not able to load diff for me, what is in there?

[char0n]

@derberg there was conflict in package-lock.json file between master and next-spec. I did try to resolve using git diff tool but I've always ended up with corrupted package-lock.json. So I've decided to regenerate it using node v16.15.1 (npm v8.11.0) and following command:

  $ npm i --verbose --legacy-peer-deps

[derberg]

@char0n weird, there should not be any conflicts, we should just take 1:1 what is in the master as I don't think there should be any changes in the next-spec related to dependencies

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[char0n]

@char0n weird, there should not be any conflicts, we should just take 1:1 what is in the master as I don't think there should be any changes in the next-spec related to dependencies

@derberg you can try for yourself by checking into next-spec branch and running git merge master. Just make sure both branches are up-todate.

Anyway, I've tried to eliminate the package-lock.json diff by copying it's content from master during conflict resolution and running npm i to regenerate only actual changes from package.json instead of regenerating it all. You are now able to inspect the diff in package-lock.json file.

[char0n]

And the windows memory test is now passing as well.

[derberg]

LGTM 👍🏼

[derberg]

/rtm

[asyncapi-bot]

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

The release is available on:

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

Your semantic-release bot 📦🚀

[asyncapi-bot]

🎉 This PR is included in version 1.17.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[asyncapi-bot]

🎉 This PR is included in version 2.0.0-next-major.18 🎉

The release is available on:

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

Your semantic-release bot 📦🚀