chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

Updates

• Chores
  • Added three new upcoming meetings to the system with complete scheduling details including titles, calendar links, and associated resources.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	20ac76b
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/697172ba637edf0008381151
😎 Deploy Preview	https://deploy-preview-4995--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

Walkthrough

The pull request adds three new meeting entries to the config/meetings.json configuration file. Each entry contains meeting metadata including title, calendar link, URL, banner image, and date. No existing entries were modified.

Changes

Cohort / File(s)	Summary
Meeting Configuration Updates config/meetings.json	Appends three new meeting objects to the array with complete metadata (title, calLink, url, banner, date)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4630: Also modifies config/meetings.json by appending new meeting entries to the array
• chore: update meetings.json and newsrooom_videos.json #4918: Similarly updates config/meetings.json by adding new meeting objects
• chore: update meetings.json and newsrooom_videos.json #4554: Modifies the same config/meetings.json file with meeting entry changes

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

🐰 Three more meetings hop into place,
Config files filled with time and space,
No edits old, just calendars new,
AsyncAPI events—there's quite a few! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The pull request title mentions updating both meetings.json and newsrooom_videos.json, but the raw summary shows only changes to config/meetings.json with no modifications to newsrooom_videos.json.	Update the PR title to accurately reflect only the changes made. Consider: 'chore: update meetings.json' or verify if newsrooom_videos.json changes are also included.

✅ 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 changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 (7813fdb) to head (20ac76b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4995   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

☔ 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	39
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@config/meetings.json`:
- Around line 86-92: The "title" field currently contains a long agenda-like
sentence; change the "title" value to a concise meeting name (e.g., "Builders
Program Update" or "Builders Progress Meeting") to match other entries' naming
style—edit the JSON object containing the "title" key in this diff and replace
the verbose sentence with a short, consistent meeting title while leaving other
fields (calLink, url, banner, date) unchanged.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Meeting title appears to be a description rather than a name.

The title "Provide updates on the progress the builders are making on the different programs they're leading." reads like a meeting agenda item or description rather than a meeting title. Other entries in this file use concise names like "AsyncAPI Community WG Meeting" or "Governance Board Meeting".

Consider updating this to a proper meeting name for consistency with other entries.

🤖 Prompt for AI Agents

In `@config/meetings.json` around lines 86 - 92, The "title" field currently
contains a long agenda-like sentence; change the "title" value to a concise
meeting name (e.g., "Builders Program Update" or "Builders Progress Meeting") to
match other entries' naming style—edit the JSON object containing the "title"
key in this diff and replace the verbose sentence with a short, consistent
meeting title while leaving other fields (calLink, url, banner, date) unchanged.