fix: update copyright year to 2025 in documentation

[SouparnaChatterjee]

fix: update copyright year to 2025 in documentation

Fixes #

Changes done:

• Updated copyright year from 2024 → 2025 in:
  • about.md
  • README.md

Screenshots

No UI changes — only documentation updates.

Preview Link(s):

Not applicable (Markdown-only changes).

✅️ By submitting this PR, I have verified the following

• Checked to see if a similar PR has already been opened 🤔️
• Reviewed the contributing guidelines 🔍️
• Sample preview link added (Not applicable — docs only)
• Tried Squashing the commits into one

Summary by CodeRabbit

• Documentation
  • Updated copyright year in project documentation to reflect the current year.

[coderabbitai]

Walkthrough

Copyright year updated from 2024 to 2025 across documentation files. No functional changes, logic modifications, or alterations to control flow; purely cosmetic year updates in metadata.

Changes

Cohort / File(s)	Summary
Copyright year updates README.md, about.md	Updated copyright year from 2024 to 2025; minor formatting adjustments (trailing blank line added)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple, repetitive cosmetic changes across documentation files
• No functional, logic, or behavioral modifications

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating copyright year to 2025 in documentation files (README.md and about.md).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f8cb565 and e5265ae.

📒 Files selected for processing (2)

• README.md (1 hunks)
• about.md (1 hunks)

🔇 Additional comments (2)

about.md (1)

10-10: Copyright year update looks good.

The copyright year has been correctly updated from 2024 to 2025, consistent with the README update.

README.md (1)

197-198: Copyright year and trailing newline updated correctly.

The copyright year has been updated from 2024 to 2025, and a trailing newline has been added at the end of the file—both consistent with standard documentation practices and the corresponding update in about.md.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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