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 "GSoC Welcome Contributors Call" meeting to the upcoming events, including relevant links and scheduled date.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	583cd98
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/683267e0b123e30008ae563c
😎 Deploy Preview	https://deploy-preview-4125--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 project configuration.

[coderabbitai]

Walkthrough

A new meeting entry titled "GSoC Welcome Contributors Call" was added to the meetings configuration file. The entry includes details such as the meeting name, a Google Calendar link, a GitHub issue URL, an empty banner field, and a scheduled date and time. No existing entries were changed.

Changes

File(s)	Change Summary
config/meetings.json	Added a new entry for "GSoC Welcome Contributors Call" with date, links, and metadata.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Website
    participant meetings.json

    User->>Website: Requests meetings data
    Website->>meetings.json: Reads meeting entries
    meetings.json-->>Website: Returns all meeting entries (including new GSoC call)
    Website-->>User: Displays updated meetings list

Loading

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3415: Adds a new meeting entry to the same meetings.json file.
• chore: update meetings.json and newsrooom_videos.json #4079: Adds another meeting entry to meetings.json for a different event.
• chore: update meetings.json and newsrooom_videos.json #4121: Adds a new meeting entry to meetings.json without modifying existing entries.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

A meeting appears, so bright and new,
For GSoC friends, both old and true.
On May twenty-ninth, mark the call,
Contributors welcome, one and all!
In JSON fields, the invite lies—
🐇 Hopping to greet with open eyes!

---

📜 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 38fa620 and 583cd98.

📒 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)

155-161: Approve new meeting entry "GSoC Welcome Contributors Call"
The JSON snippet is syntactically correct and follows the existing formatting (indentation, comma placement, ISO8601 date with milliseconds). All required fields (title, calLink, url, banner, date) are present and consistent with the other entries.

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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 (38fa620) to head (583cd98).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4125   +/-   ##
=========================================
  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.