chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Added upcoming meetings: "AsyncAPI Community WG Meeting" (May 6, 2025) and "Design WG Meeting" (May 1, 2025) to the meetings list.

• Chores

  • Updated newsroom videos by removing the April 22, 2025 Community WG Meeting video and adding the March 18, 2025 Marketing WG Meeting video.

[coderabbitai]

Walkthrough

This update modifies two JSON configuration files. In config/meetings.json, two new meeting entries are added for upcoming events in May 2025, each with details such as title, date, calendar link, and GitHub issue reference. In config/newsroom_videos.json, the first video entry is removed, and a new video entry for a Marketing Working Group Meeting from March 2025 is appended, including its metadata. No changes are made to any exported code or public entities; only data within configuration files is updated.

Changes

Files	Change Summary
config/meetings.json	Added two new meeting entries: "AsyncAPI Community WG Meeting" (May 6, 2025) and "Design WG Meeting" (May 1, 2025).
config/newsroom_videos.json	Removed the first video entry (April 22, 2025) and appended a new video entry for the Marketing WG Meeting (March 18, 2025).

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4046: Automated updates to the same configuration files, adding and modifying meeting and video entries.
• chore: update meetings.json and newsrooom_videos.json #4027: Updates to meetings.json and newsroom_videos.json for meeting and video listings, indicating related event and media changes.
• chore: update meetings.json and newsrooom_videos.json #3485: Adds and removes entries in meetings and video JSON files, directly related to scheduling and video updates.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

Two new meetings on the springtime slate,
Videos shuffled to keep things up to date.
JSON lines in tidy rows,
Where AsyncAPI’s schedule grows.
A hop, a skip, a calendar cheer—
More events and news for all to hear!
🐇✨

---

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.

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.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	b76272c
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/68098788ff218e00084338bc
😎 Deploy Preview	https://deploy-preview-4058--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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (64aaa22) to head (b76272c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4058   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          671       671           
  Branches       115       115           
=========================================
  Hits           671       671           

☔ 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/meetings.json (1)

121-127: Nit: Remove trailing whitespace in the title
The title field on line 122 ends with an extra space ("Design WG Meeting "). Trimming it to "Design WG Meeting" will improve consistency with other entries.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 64aaa22 and b76272c.

📒 Files selected for processing (2)

• config/meetings.json (1 hunks)
• config/newsroom_videos.json (1 hunks)

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

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI
• GitHub Check: Test NodeJS PR - windows-latest

🔇 Additional comments (2)

config/meetings.json (1)

113-120: New AsyncAPI Community WG Meeting entry looks good
The added object at lines 113–120 follows the existing schema and includes all required fields (title, calLink, url, banner, date), and the JSON comma placement is correct.

config/newsroom_videos.json (1)

26-31: New video entry is valid
The newly appended video object includes all required properties (image_url, title, description, videoId) and fits the existing list format. JSON punctuation is correct.