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 "Marketing WG Meeting" scheduled for May 13, 2025.
  • Added a new video entry for the "AsyncAPI Marketing Working Group Meeting, April 29th 2025".

• Chores

  • Removed the video entry for the "AsyncAPI Community Working Group Meeting, March 25th 2025".

[coderabbitai]

Walkthrough

This update modifies two configuration files. A new entry for the "Marketing WG Meeting" scheduled for May 13, 2025, is added to the meetings configuration file. In the newsroom videos configuration, a new video entry for the "AsyncAPI Marketing Working Group Meeting, April 29th 2025" is added at the top of the list, while the previous entry for the "AsyncAPI Community Working Group Meeting, March 25th 2025" is removed. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
config/meetings.json	Added a new entry for the "Marketing WG Meeting" on May 13, 2025, with associated metadata.
config/newsroom_videos.json	Added a new video entry for "AsyncAPI Marketing Working Group Meeting, April 29th 2025" and removed the entry for "AsyncAPI Community Working Group Meeting, March 25th 2025".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Website
    participant ConfigFiles

    User->>Website: Requests meeting or video list
    Website->>ConfigFiles: Reads meetings.json and newsroom_videos.json
    ConfigFiles-->>Website: Provides updated meeting and video data
    Website-->>User: Displays new meeting and video entries

Loading

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3390: Adds new "Marketing WG Meeting" entries and updates newsroom videos, similar to this PR but for different dates.
• chore: update meetings.json and newsrooom_videos.json #3710: Updates meetings and video entries for "Marketing WG Meeting" events in the same configuration files.
• chore: update meetings.json and newsrooom_videos.json #3992: Adds new entries to meetings.json and newsroom_videos.json for Marketing WG meetings, closely related in update pattern.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

A meeting is set, a video anew,
The Marketing WG hops into view!
With JSON entries crisp and bright,
Events and recordings take their flight.
Rabbits rejoice, the schedule’s clear—
More AsyncAPI moments to cheer!
🐇✨

---

📜 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 8d05db7 and ebb52c2.

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

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

🔇 Additional comments (2)

config/meetings.json (1)

127-133: Validate the new meeting entry for consistency and accuracy.

The newly appended object for the “Marketing WG Meeting” (lines 128–133) adheres to the schema and formatting of existing entries. Please verify:

• The date field is correct and in UTC (2025-05-13T14:00:00.000Z).
• The calLink points to the intended Google Calendar event.
• The url matches the corresponding GitHub issue.
• Leaving "banner": "" is intentional (no image).

Once confirmed, this addition can be approved.

config/newsroom_videos.json (1)

2-7: Confirm the new video entry is correct and properly ordered.

The new video block at the top (lines 2–7) for “AsyncAPI Marketing Working Group Meeting, April 29th 2025” matches the existing structure. Please ensure:

• The image_url and videoId correspond to the actual YouTube thumbnail/video.
• The description URLs (restream.io and GitHub issue) are accurate.
• JSON separators/comma placement remain valid after insertion.

If all checks pass, this update can be merged.

---

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	ebb52c2
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/681170ae7bf3570008fd8d88
😎 Deploy Preview	https://deploy-preview-4079--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 (8d05db7) to head (ebb52c2).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4079   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          733       733           
  Branches       121       121           
=========================================
  Hits           733       733           

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