chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Added a new "AsyncAPI Community WG Meeting" scheduled for May 20, 2025, to the meetings list, including relevant links and a banner image.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	b46b082
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/681bfd64097695000878be17
😎 Deploy Preview	https://deploy-preview-4100--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Walkthrough

A new entry for the "AsyncAPI Community WG Meeting" scheduled on May 20, 2025, at 15:00 UTC was appended to the config/meetings.json file. The entry includes details such as the meeting title, date, time, calendar link, GitHub issue URL, and a banner image.

Changes

File(s)	Change Summary
config/meetings.json	Appended a new JSON object for the "AsyncAPI Community WG Meeting" on May 20, 2025, with relevant links.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Website
    participant MeetingsConfig

    User->>Website: Requests meeting schedule
    Website->>MeetingsConfig: Reads meetings.json
    MeetingsConfig-->>Website: Returns list including new AsyncAPI Community WG Meeting
    Website-->>User: Displays updated meetings list

Loading

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4066: Updates meetings.json by adding or modifying meeting entries, similar to the current change.
• chore: update meetings.json and newsrooom_videos.json #3992: Adds new meeting entries to config/meetings.json without altering existing ones, directly related in structure and purpose.
• chore: update meetings.json and newsrooom_videos.json #4079: Adds new meeting entries to config/meetings.json, related by extending the meetings schedule.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee
• devilkiller-ag
• vishvamsinh28
• asyncapi-bot-eve

Poem

A meeting is set, the calendar grows,
May 20th at three, the community knows.
JSON lines added, so neat and so bright,
Rabbits in code, hopping with delight.
The schedule expands, the future is clear—
More AsyncAPI moments for all to appear!
🐇✨

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between decfab1 and b46b082.

📒 Files selected for processing (1)

• config/meetings.json (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (2)

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

🔇 Additional comments (1)

config/meetings.json (1)

134-141: New meeting entry appended correctly.
The "AsyncAPI Community WG Meeting" on 2025-05-20 is inserted in proper chronological order, follows the established key ordering (title, calLink, url, banner, date), and maintains consistent formatting.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (decfab1) to head (b46b082).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4100   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.