Fix/optional sponsors tier

[rahul-vyas-dev]

Screenshots/Recordings:

Before: -

After: -

Additional Notes:

Fix the case when sponsors tier is not passed.

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.

Summary by CodeRabbit

• Bug Fixes

  • Sponsorship tier labels are now displayed only when tier information is available, preventing empty labels from appearing.

• Chores

  • Updated application and package version numbers.

[coderabbitai]

Warning

Review limit reached

@rahul-vyas-dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: df4a8ec4-0870-4b54-88b2-cf19a759fc89

📥 Commits

Reviewing files that changed from the base of the PR and between 9144c69 and f460463.

📒 Files selected for processing (1)

• VERSION

Walkthrough

SupportUsButton now omits empty sponsorship tier labels. The VERSION file and package.json also receive version updates.

Changes

Sponsor rendering and release metadata

Layer / File(s)	Summary
Conditional sponsor tier rendering src/components/SupportUsButton.tsx	The sponsorship tier <span> is rendered only when sponsor.sponsorshipTier is present.
Release version metadata VERSION, package.json	Project version values are updated in both release metadata files.

Estimated code review effort: 2 (Simple) | ~5 minutes

Possibly related PRs

• AOSSIE-Org/SupportUsButton#32: Also changes sponsor tier rendering in SupportUsButton.

Suggested labels: Typescript Lang

Poem

A bunny saw a tier tag fade,
When empty fields were gently laid.
Versions hopped from one to two,
Then two-point-one joined the queue.
“Clean sponsor cards!” the rabbit said.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly reflects the main change: making the sponsors tier optional.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@VERSION`:
- Line 1: Synchronize the release metadata to the authoritative version 2.1.0:
update VERSION at line 1 and package.json at line 3 so both declare 2.1.0 before
publishing.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4ddfdad2-1023-4cad-a1c9-069e7265dbe7

📥 Commits

Reviewing files that changed from the base of the PR and between 228b368 and 9144c69.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• VERSION
• package.json
• src/components/SupportUsButton.tsx