chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Chores
  • Removed the “Marketing WG Meeting” (June 10, 2025) from the public meetings list.
  • Deleted the event’s associated calendar link, URL, and banner.
  • The event will no longer appear on the site calendar or meetings page.
  • Existing calendar subscriptions will no longer include this event.
  • No other meetings were changed.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	977ecaf
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/68d1eb5b0165330008f246a5
😎 Deploy Preview	https://deploy-preview-4430--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

Removed a single meeting object titled "Marketing WG Meeting" dated 2025-06-10T14:00:00.000Z from config/meetings.json, including its calLink, url, and banner fields. No other files or public entities were changed.

Changes

Cohort / File(s)	Summary
Meetings config cleanup config/meetings.json	Deleted one meeting entry: title "Marketing WG Meeting" with date 2025-06-10T14:00:00.000Z (including calLink, url, banner).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #4345 — Also removes the same "Marketing WG Meeting" entry from config/meetings.json.
• chore: update meetings.json and newsrooom_videos.json #4386 — Removes a "Marketing WG Meeting" entry (different date) in config/meetings.json.
• chore: update meetings.json and newsrooom_videos.json #4393 — Modifies the "Marketing WG Meeting" entry in config/meetings.json (add/update vs. this removal).

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I nibbled the calendar, hop by hop,
Snipped one carrot-colored stop.
A meeting gone, the burrow’s light—
Less clutter for our moonlit night.
Thump-thump, I tidy, then I cheer,
One less ping in rabbit’s ear. 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The PR title claims updates to "meetings.json" and "newsrooom_videos.json" but the provided raw_summary only documents a removal in config/meetings.json, and the title contains a misspelling ("newsrooom"), creating an inconsistency between the title and the reported changes; this makes it unclear whether the title accurately reflects the changeset. Because of that mismatch and the typo, I cannot conclusively determine that the title correctly summarizes the actual changes.	Please correct the filename typo ("newsrooom" → "newsroom") and update the PR title to precisely match the files changed (for example "chore: update meetings.json" if only meetings.json changed, or "chore: update meetings.json and newsroom_videos.json" if both were actually modified).

✅ 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 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/9791f0d5e25ea757543e8fbaa03e2e4a75664dd9

---

📜 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 9791f0d and 977ecaf.

📒 Files selected for processing (1)

• config/meetings.json (0 hunks)

💤 Files with no reviewable changes (1)

• config/meetings.json

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

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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 (9791f0d) to head (977ecaf).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

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

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