chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Added a new meeting entry to the meeting schedule for AsyncAPI Spec Triage scheduled for January 22, 2026.

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

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	a4697db
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/69698a4ca2bade0008e7b891
😎 Deploy Preview	https://deploy-preview-4961--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

A new meeting entry titled "AsyncAPI Spec Triage" scheduled for January 22, 2026 at 16:00 UTC was added to the meetings configuration file with associated calendar and URL links.

Changes

Cohort / File(s)	Summary
Meetings Configuration config/meetings.json	Added new meeting object for "AsyncAPI Spec Triage" with calendar link, URL, empty banner field, and ISO 8601 timestamp

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4922: Modifies config/meetings.json to add/update meeting entries in the same file
• chore: update meetings.json and newsrooom_videos.json #4695: Updates config/meetings.json by adding meeting entries alongside other config changes
• chore: update meetings.json and newsrooom_videos.json #4563: Modifies config/meetings.json to add a new meeting entry to the array

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• anshgoyalevil
• sambhavgupta0705
• princerajpoot20
• Mayaleeeee

Poem

🐰 A meeting springs forth on the calendar view,
AsyncAPI Spec Triage, scheduled fresh and new,
January twenty-second, when the rabbits convene,
To hop through the specs—the finest we've seen!
Config updated, the schedule takes flight, 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims changes to both meetings.json and newsroom_videos.json, but the summary shows only meetings.json was modified.	Update the title to accurately reflect the actual changes, such as 'chore: add AsyncAPI Spec Triage meeting to meetings.json' or verify if newsroom_videos.json changes were intended.

✅ 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.}

---

---

📜 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 dad42e3 and a4697db.

📒 Files selected for processing (1)

• config/meetings.json

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: asyncapi-bot
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch

⏰ 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). (4)

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: cypress-run
• GitHub Check: Lighthouse CI

🔇 Additional comments (1)

config/meetings.json (1)

78-85: Confirm the referenced GitHub issue exists.

The new meeting entry for "AsyncAPI Spec Triage" is properly structured and follows the established format in the JSON file. However, verify that the referenced GitHub issue (asyncapi/community#2244) is valid and accessible.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review 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 (dad42e3) to head (a4697db).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

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

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