ci: fix security check by verifying repository permissions instead of…

[Atharva0506]

Addressed Issues:

Fixes #(issue number)

Screenshots/Recordings:

Additional Notes:

This PR replaces the organization membership check in version-release.yml with a repository-level collaborator permission check.
Why this was needed:
The previous script used getMembershipForUser to check if the actor was a member of the AOSSIE-Org organization. However, on GitHub, organization memberships are set to "Private" by default. The standard GITHUB_TOKEN provided to actions does not have permission to view private organization memberships, so it was resulting in a 404 Not Found and blocking legitimate maintainers from triggering the release workflow.
The Fix:
I have updated the script to use getCollaboratorPermissionLevel to verify if the actor has write or admin access to the repository itself. Since the token is inherently scoped to the repository, it has full access to verify collaborator permissions regardless of organization privacy settings. This securely prevents unauthorized users from running the workflow while correctly authorizing actual maintainers.

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

[coderabbitai]

Warning

Review limit reached

@Atharva0506, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 minutes and 42 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: ce262fb0-a7c5-4dbe-b516-4099f2be15c5

📥 Commits

Reviewing files that changed from the base of the PR and between f426acf and c45616c.

📒 Files selected for processing (1)

• .github/workflows/version-release.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[github-actions]

	Messages
📖	⚠️ PR Template Check These are non-blocking, but please fix: Please replace the placeholder Fixes #(issue number) with the actual issue number (e.g. Fixes #42). Some required checklist items are not completed: My PR addresses a single issue

Generated by 🚫 dangerJS against c45616c