docs(community): update latest maintainers list

[asyncapi-bot]

Updated Maintainers list is available and this PR introduces changes with latest information about Maintainers

Summary by CodeRabbit

• Chores
  • Updated the list of repositories assigned to certain maintainers. No user-facing features or functionality were changed.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	48dda6a
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/684560d0e4f9ff000898a93c
😎 Deploy Preview	https://deploy-preview-4154--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

The repository assignments for two maintainers in config/MAINTAINERS.json were updated. The "spec-json-schemas" repository was removed from Sergio Moya's list, and the "saunter" repository was removed from Alexander Wichmann's list. No other maintainers or fields were changed.

Changes

File	Change Summary
config/MAINTAINERS.json	Updated maintainers' repository lists: removed "spec-json-schemas" from Sergio Moya; removed "saunter" from Alexander Wichmann.

Possibly related PRs

• docs(community): update latest maintainers list #3273: Also updates config/MAINTAINERS.json by removing repositories from maintainers' lists.
• docs(community): update latest maintainers list #4119: Changes repository assignments for "Sergio Moya" in config/MAINTAINERS.json, directly related to this update.
• docs(community): update latest maintainers list #3361: Updates repository assignments in config/MAINTAINERS.json, indicating changes in maintainer responsibilities.

Suggested labels

autoapproved, ready-to-merge, autoupdate

Suggested reviewers

• derberg
• anshgoyalevil
• sambhavgupta0705
• Mayaleeeee
• devilkiller-ag
• vishvamsinh28
• akshatnema

Poem

In the warren of maintainers, names hop and shift,
Repos are traded, in a gentle spring lift.
Sergio and Alexander, your gardens rearranged,
The JSON fields tidy, responsibilities changed.
With every small update, the project grows bright—
🐇 Onward we hop, through the code and the night!

---

📜 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 521b729 and 48dda6a.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

config/MAINTAINERS.json (2)

439-449: Confirm removal of spec-json-schemas from Sergio Moya's assignments

The "spec-json-schemas" repository was removed from Sergio Moya's repos list. Please verify that this reflects the current ownership and that no pending issues or responsibilities remain under his purview.

---

636-638: Confirm removal of saunter from Alexander Wichmann's assignments

The saunter repository has been dropped from Alexander Wichmann's repos list, leaving only spec-json-schemas and bindings. Ensure this change matches the latest maintainership roster and that saunter is reassigned or marked as unmaintained appropriately.

---

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 (521b729) to head (48dda6a).
Report is 1 commits behind head on master.

Additional details and impacted files

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