Update README.md

[kpj2006]

Addressed Issues:

Fixes #(issue number)

Screenshots/Recordings:

Additional Notes:

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

• Documentation
  • Updated the copyright year in the contributor acknowledgment section from 2025 to 2026.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1e60198a-3487-4801-9bad-4c5dd4d76d0a

📥 Commits

Reviewing files that changed from the base of the PR and between e962c18 and 938905d.

📒 Files selected for processing (1)

• README.md

---

Walkthrough

The README copyright notice in the “Thanks To All Contributors” section is updated from © 2025 AOSSIE to © 2026 AOSSIE.

Changes

README Documentation

Layer / File(s)	Summary
Update copyright year README.md	The footer copyright year changes from 2025 to 2026.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: Documentation

Suggested reviewers: zahnentferner

Poem

A rabbit hops through README light,
Updating years to keep them right.
From twenty-five to twenty-six,
A tidy change—no magic tricks.
The footer shines, neat as a carrot’s glow.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is related to the change, but it is too generic and does not describe the actual README edit.	Rename it to mention the specific README change, such as updating the copyright year in the contributors section.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.}

[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 My code follows the project's code style My changes generate no new warnings or errors

Generated by 🚫 dangerJS against 938905d