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 video entry for the "AsyncAPI Design WG Meeting, Tuesday June 17th 2025".
  • Removed the oldest video entry from the list.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	ed115d2
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/685b4557da019600084da5d9
😎 Deploy Preview	https://deploy-preview-4209--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

A new entry for the "AsyncAPI Design WG Meeting, Tuesday June 17th 2025" video was added to the start of the newsroom videos JSON configuration file, while the last video entry was removed. No other changes were made to the file or exported entities.

Changes

File(s)	Change Summary
config/newsroom_videos.json	Added new video entry at the beginning; removed last entry

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4098: Modifies the same JSON file by adding a new video at the beginning and removing the last entry.
• chore: update meetings.json and newsrooom_videos.json #4139: Updates config/newsroom_videos.json by adding and removing video entries, directly relating to video list management.
• chore: update meetings.json and newsrooom_videos.json #4167: Also adds a new video entry at the beginning and removes the last entry in the same JSON file for a different meeting date.

Suggested reviewers

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

Poem

Hopping through the JSON field,
A new video carrot is freshly revealed!
The oldest sprout, now gently gone,
While June's meeting hops right on.
With every nibble, the list is neat—
AsyncAPI’s garden, tidy and sweet!
🥕

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a7d46a and ed115d2.

📒 Files selected for processing (1)

• config/newsroom_videos.json (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (8)

• 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 - ubuntu-latest
• GitHub Check: Test NodeJS PR - macos-13
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI

🔇 Additional comments (1)

config/newsroom_videos.json (1)

2-7: Potential duplicate entry for the same meeting

The newly-added Design WG entry has an identical title/date to the item that already exists at lines 9-13 but carries a different videoId. Unless the meeting was intentionally split into multiple recordings, this will surface twice on the site and may confuse users or break deduplication logic downstream.

Recommend verifying which videoId is correct and removing the unintended duplicate.

To quickly spot any other duplicates across the file you can run:

#!/bin/bash
# List titles that occur more than once
jq -r '.[].title' config/newsroom_videos.json | sort | uniq -d
# List videoIds that occur more than once
jq -r '.[].videoId' config/newsroom_videos.json | sort | uniq -d

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

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

Documentation and Community

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ca4eb7f) to head (ed115d2).
Report is 2 commits behind head on master.

Additional details and impacted files

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