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 event to the meetings list: “AsyncAPI Community WG Meeting.”
    • Date/time: 2025-09-09 15:00 UTC
    • Includes direct links to the calendar event and discussion thread
    • Displays a dedicated banner image
  • Users can discover the meeting on the meetings page and quickly access details, RSVP via calendar, and join the conversation through the linked issue.

[coderabbitai]

Walkthrough

Appends a new meeting object to config/meetings.json within the meetings array, including title, calendar link, URL, banner, and ISO date. No other files or logic are changed.

Changes

Cohort / File(s)	Summary
Meetings config config/meetings.json	Appended a new meeting entry: Title "AsyncAPI Community WG Meeting", specified calLink, url, banner, and date "2025-09-09T15:00:00.000Z". Array length increased by 1; schema unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4330 — Also modifies config/meetings.json, adding/removing the same "AsyncAPI Community WG Meeting" entry.
• chore: update meetings.json and newsrooom_videos.json #4202 — Appends an "AsyncAPI Community WG Meeting" entry in the same file with similar fields.
• chore: update meetings.json and newsrooom_videos.json #4100 — Adds the same meeting entry in config/meetings.json with differing scheduled dates.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I twitch my ears at calendars bright,
A meeting hops into our site—delight!
AsyncAPI gathers, links in a row,
Banner unfurled, the dates all aglow.
I thump approval: one more hop to go! 🐇📅

✨ Finishing Touches

🧪 Generate unit tests

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

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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	f858102
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68b8deb7d9eda70008df9e63
😎 Deploy Preview	https://deploy-preview-4380--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.

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4380   +/-   ##
=========================================
  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	37
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/meetings.json (1)

135-140: Sort meetings.json entries chronologically
Multiple dates are out of order (e.g. 2025-05-27 appears after 2025-05-29, and the 2025-09-09 entry follows 2025-09-30). Keep the array sorted by date or apply sorting in the rendering layer.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 80cf3e5 and f858102.

📒 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). (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 (1)

config/meetings.json (1)

134-141: LGTM: valid JSON and schema-consistent entry added.

The new meeting object uses the established fields (title, calLink, url, banner, date) with a correctly formatted ISO 8601 UTC timestamp. Comma placement and array termination are correct.