Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update next-spec with latest master #691

Merged
merged 18 commits into from
Jan 25, 2023

Conversation

AceTheCreator
Copy link
Member

This PR updates next-spec branch with changes from master.

cc @fmvilas @derberg

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

derberg
derberg previously approved these changes Jan 20, 2023
fmvilas
fmvilas previously approved these changes Jan 23, 2023
@fmvilas
Copy link
Member

fmvilas commented Jan 23, 2023

🤔 We got a failing test. Any idea why this is happening? @magicmatatjahu

@fmvilas
Copy link
Member

fmvilas commented Jan 23, 2023

Anyway, this is not a concern of this PR so feel free to merge. Remember to merge using the "Merge commit" strategy instead of the "Squash and merge" one.

@magicmatatjahu
Copy link
Member

@fmvilas

We got a failing test. Any idea why this is happening?

I don't know 🤷🏼 I don't think so that in the failing test the ajv try to create the new reference for each validation function. I have to check that, so yeah, please merge it and I will apply fix (probably on release branch).

@AceTheCreator
Copy link
Member Author

I think I need your approvals @magicmatatjahu, @jonaslagoni

magicmatatjahu
magicmatatjahu previously approved these changes Jan 23, 2023
@AceTheCreator
Copy link
Member Author

/rtm

@fmvilas
Copy link
Member

fmvilas commented Jan 24, 2023

Yeah, we can't merge if this test is not passing. We should be fixing it on another PR pointing to next-spec.

@magicmatatjahu
Copy link
Member

@AceTheCreator Please add new commits from master and try to merge it :)

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@AceTheCreator
Copy link
Member Author

All tests passed, thanks to @magicmatatjahu

Kindly review this PR @fmvilas @derberg

@AceTheCreator
Copy link
Member Author

/rtm

@asyncapi-bot asyncapi-bot merged commit f52bc17 into asyncapi:next-spec Jan 25, 2023
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 1.17.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@asyncapi-bot
Copy link
Contributor

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

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants