chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Added two upcoming Governance Board Meetings to the public meetings list with dates on September 2 and September 29, 2025, each including calendar links and issue references. No existing meetings were modified.
  • Updated Newsroom videos: added “Governance Board Meeting, Monday September 15th 2025” (now featured at the top) and removed the older “First Meeting of New Governance Board.” All other videos remain unchanged.

[coderabbitai]

Walkthrough

Added two Governance Board Meeting entries to config/meetings.json. Updated config/newsroom_videos.json by inserting a new video at the top and removing one older video. No schema or structural changes; existing entries remain otherwise unchanged.

Changes

Cohort / File(s)	Summary
Meetings updates config/meetings.json	Appended two Governance Board Meeting items with fields: title, calLink, url, banner, date (2025-09-02T16:00:00.000Z and 2025-09-29T16:00:00.000Z). No existing entries modified.
Newsroom videos list config/newsroom_videos.json	Inserted a new video (videoId 7e01rDjnVpY) at the start. Removed an older entry (videoId SaIPQaROWsc). Other entries unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3352 — Touches the same config arrays for meetings and newsroom videos with similar add/remove operations.
• chore: update meetings.json and newsrooom_videos.json #3369 — Also updates meeting entries and video listings in the same JSON configs.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• sambhavgupta0705
• anshgoyalevil
• Mayaleeeee
• asyncapi-bot-eve

Poem

I thump my paws—new dates to keep,
Two meetings hop onto the heap.
A fresh clip shines, an old one goes,
The burrow’s calendar neatly grows.
Carrots aligned, the timeline set—
Onward we scamper—sync’d, no sweat! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title is concise and directly reflects the primary changes (updates to meetings.json and the newsroom videos configuration), so it accurately summarizes the main change in the changeset; however it contains a minor typo ("newsrooom_videos.json") that could cause slight confusion.
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/659cff90e7d2629c2b6752af766e2327d295b5a5

---

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

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	3485c45
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68c8b0aaa41bc60008f329fc
😎 Deploy Preview	https://deploy-preview-4419--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 (659cff9) to head (3485c45).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/newsroom_videos.json (1)

2-7: Minor polish — remove trailing period from top entry description

• Verified: JSON valid; no duplicate videoIds. Top entry (config/newsroom_videos.json, index 0) description ends with a trailing period — remove the final '.' from "asyncapi/community#2069." to avoid autolink issues.
• Optional: normalize spacing before commas in titles across the file for consistency (some entries contain a space before commas).

📜 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 659cff9 and 3485c45.

📒 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. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Redirect rules - 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-148: Approve — entries valid; manual calLink check required

• meetings.json is valid JSON and contains no duplicate Governance Board dates.
• New entries present: 2025-09-02T16:00:00.000Z → issue #2073; 2025-09-29T16:00:00.000Z → issue #2074.
• File order is not strictly chronological (09-15 appears before 09-02); frontend sorts events at runtime in utils/staticHelpers.ts (meetingsWithDates.sort((a:any,b:any)=>a.date - b.date)), so no change needed unless a consumer relies on in-file ordering.
• CalLink eid decode returned binary and remote validation is inconclusive from this environment — open the Google Calendar links to confirm they resolve to the intended events/times (16:00Z) and map to issues #2073/#2074.