chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Updated the Marketing WG Meeting schedule: the previous December 2024 meeting has been removed and replaced with a new entry for April 2025, ensuring that users have access to the most current meeting information.

[coderabbitai]

Walkthrough

The update modifies the meetings schedule in the configuration file by removing a "Marketing WG Meeting" entry scheduled for December 17, 2024, and adding a new entry for April 1, 2025. Both entries share similar fields (title, calendar link, URL, banner, and date) and the new entry is inserted before the last existing entry in the JSON array.

Changes

File	Summary
config/meetings.json	Removed the "Marketing WG Meeting" entry dated 2024-12-17 and added a new entry scheduled for 2025-04-01 with similar structure and fields.

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3399: Involves modifying the "Marketing WG Meeting" entry in meetings.json by both removing and adding meeting entries.
• chore: update meetings.json and newsrooom_videos.json #3754: Contains code-level changes targeting similar modifications to the "Marketing WG Meeting" entries in meetings.json.
• chore: update meetings.json and newsrooom_videos.json #3582: Focuses on the removal of an existing "Marketing WG Meeting" entry, aligning closely with the changes in this PR.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I'm a hopping rabbit in the JSON field,
Nibbling on entries with a code-built shield.
Old dates are removed, new ones take flight,
April's meeting blooms in the soft morning light.
With each joyful hop in our data's domain,
I celebrate code changes with a cheerful refrain! 🐰💻

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	161f062
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67e66354e16a0000085ce406
😎 Deploy Preview	https://deploy-preview-3984--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 site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (29b2fa1) to head (161f062).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3984   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/meetings.json (1)

85-92: New Marketing WG Meeting Entry Validated

The new "Marketing WG Meeting" entry has been added with the required fields (title, calLink, url, banner, and date). The values appear consistent with the schema used by the other meeting entries. Please verify the following:

• Insertion Position & Order: Confirm that inserting this entry at this position (just before the closing bracket) matches the intended order. If you expect the meetings to be arranged chronologically, you might want to consider sorting them or double-checking the order.
• Removal Consistency: The PR objectives mention removing a "Marketing WG Meeting" scheduled for December 17, 2024. Although that entry isn’t shown here, ensure that its removal is complete and that no stale data remains elsewhere.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c51a00c and 3548ce5.

📒 Files selected for processing (1)

• config/meetings.json (1 hunks)

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

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

[thulieblack]

/rtm