chore: remove cameron rushton from the tsc members list

[CameronRushton]

Description
Remove self from the TSC members list since I'm inactive.

Related issue(s)
None

Summary by CodeRabbit

• Chores
  • Updated the Technical Steering Committee roster by adjusting the membership status for a team member.

[coderabbitai]

Walkthrough

This change updates the MAINTAINERS.yaml file by modifying the isTscMember status for Cameron Rushton from true to false. All other details for Cameron, such as Slack ID, hire availability, company affiliation, and repository contributions, remain unchanged. There are no changes to the declarations of exported or public entities.

Changes

File	Change Summary
MAINTAINERS.yaml	Updated isTscMember for Cameron Rushton from true to false.

Poem

I hopped along the YAML trail,
Tweaking status with a happy tail.
Cameron's flag now set to false,
No disruptions in the code's pulse.
Celebrating changes in a rabbit's rhyme,
Hopping forward one commit at a time!
🐇✨

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

MAINTAINERS.yaml (1)

1-789: Pipeline Validation Failure – Verify YAML Schema Compliance
The pipeline failure indicates that the maintainers file does not pass the YAML schema validation. Please review the file format and ensure that all entries (including unchanged ones) adhere to the required schema. It may be helpful to run a local YAML linter or validation tool and check the maintainers file guidelines for any missing or misconfigured keys.

🧰 Tools

🪛 Gitleaks (8.21.2)

143-143: Found a LinkedIn Client ID, risking unauthorized access to LinkedIn integrations and professional data exposure.

(linkedin-client-id)

---

172-172: Found a LinkedIn Client ID, risking unauthorized access to LinkedIn integrations and professional data exposure.

(linkedin-client-id)

---

744-744: Found a LinkedIn Client ID, risking unauthorized access to LinkedIn integrations and professional data exposure.

(linkedin-client-id)

---

585-585: Discovered a LinkedIn Client secret, potentially compromising LinkedIn application integrations and user data.

(linkedin-client-secret)

🪛 GitHub Actions: Validating the list of maintainers

[error] Validation of maintainers file failed with the following errors: [validator.errors]

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1a1c24 and 4d77701.

📒 Files selected for processing (1)

• MAINTAINERS.yaml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Validating the list of maintainers

MAINTAINERS.yaml

[error] Validation of maintainers file failed with the following errors: [validator.errors]

🔇 Additional comments (1)

MAINTAINERS.yaml (1)

88-88: Update of TSC Membership Status for Cameron Rushton
The change correctly updates isTscMember to false, which properly removes Cameron Rushton from the Technical Steering Committee as per the PR objectives.

🧰 Tools

🪛 GitHub Actions: Validating the list of maintainers

[error] Validation of maintainers file failed with the following errors: [validator.errors]

[derberg]

Thanks for all your current support, and see you in future whenever ready

[derberg]

/rtm

[asyncapi-bot]

@CameronRushton We would like to express our gratitude for your contributions as a member of the Technical Steering Committee at the AsyncAPI Initiative. Your efforts have been immensely valuable to us, and we truly appreciate your dedication. Thank you once again, and we wish you all the best in your future endeavors!