chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Added the AsyncAPI Community WG Meeting to the events/meetings list, including date (Oct 21, 2025), banner, and calendar link.
• Chores
  • Removed the deprecated Marketing WG Meeting from the schedule.
  • Updated event ordering to place the new Community WG Meeting after the AsyncAPI Online Conference 2025.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	3de9ca4
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68df1a2f726de60008ad3cc7
😎 Deploy Preview	https://deploy-preview-4449--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

Updated config/meetings.json by removing the “Marketing WG Meeting” entry and adding a new “AsyncAPI Community WG Meeting” entry with specified calLink, URL (issue 2087), banner, and date (2025-10-21T15:00:00.000Z), positioned after the AsyncAPI Online Conference 2025 entry.

Changes

Cohort / File(s)	Summary of Changes
Meetings config update config/meetings.json	Removed "Marketing WG Meeting" block; added "AsyncAPI Community WG Meeting" block (calLink eid …2087, url to issue 2087, banner, date 2025-10-21T15:00:00.000Z); placed after AsyncAPI Online Conference 2025 entry.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4430 — Also edits config/meetings.json, removing a "Marketing WG Meeting" entry.
• chore: update meetings.json and newsrooom_videos.json #4411 — Updates Community WG entries and adjusts/removes Marketing WG entries in config/meetings.json.
• chore: update meetings.json and newsrooom_videos.json #4431 — Modifies AsyncAPI Community WG Meeting data in config/meetings.json.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee
• devilkiller-ag

Poem

Thump-thump goes my rabbit heart—hop hooray!
A meeting hops in; another hops away.
New carrots on the calendar, crisp and bright,
Community gathers by autumn light.
I twitch my whiskers—dates aligned just right. 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title merely lists file names under a generic “chore” prefix and even references “newsrooom_videos.json,” which is not changed, rather than summarizing the actual work of removing the Marketing WG Meeting and adding the AsyncAPI Community WG Meeting entry in meetings.json, so it is both vague and inaccurate.	Revise the title to focus on the primary change—removing the Marketing WG Meeting and adding the AsyncAPI Community WG Meeting in meetings.json—and drop any mention of files not actually modified; for example, “chore: replace Marketing WG Meeting with AsyncAPI Community WG Meeting in meetings.json.”

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit's high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-meetings/bfda00351d82c70b52854eb9fc1d3290e8473e83

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bfda003 and 3de9ca4.

📒 Files selected for processing (1)

• config/meetings.json (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

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

🔇 Additional comments (1)

config/meetings.json (1)

128-133: Data update looks consistent.

The newly added meeting entry follows the existing structure and the details align with the referenced issue/event. Looks good.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (bfda003) to head (3de9ca4).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

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

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	38
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-4449--asyncapi-website.netlify.app/